PUT /targerts/{target_id} update of metadata causing failure

October 30, 2012 - 4:09pm #1

Starting about an hour ago, we started seeing targets got into a permanent "processing" state when updating the target's metadata.

Basically, we're doing a PUT /targets/{target_id} with just the new metadata in the request's JSON.  The target goes into a "processing" state and does not seem to come out of it.  Unfortunately, it also means we cannot the target using DELETE /targets/{target_id}, since apparently you can't do that while the target is in this state.

The targets in our dataset that are in this state are 1dedbef29e6149c4b247388ffd59cb5e, 4de2e4b9cf154d78bfe3baa6722ab952 and d907cdd0f90f4569aa90b41fbce00762.


PUT /targerts/{target_id} update of metadata causing failure

November 1, 2012 - 3:31pm #5

It looks like they eventually reverted to success after some hours, with the exception of the one in the "failed" state.

Unfortunately, I disabled metadata updates to your server and added an API to my service to work around this issue. I'll try reenabling metadata updates and see what happens.

PUT /targerts/{target_id} update of metadata causing failure

November 1, 2012 - 3:25pm #4

Are the 'success' targets still stuck in processing, or reverted to failed? - are they listed below?

Please see your PM.

PUT /targets/{target_id} update of metadata causing failure

October 31, 2012 - 3:24pm #3

Both.  I've seen it with new targets, which I suspected was due to the fact it was still in the "processing" state, but I was then able to reproduce with "success" targets as well.

PUT /targerts/{target_id} update of metadata causing failure

October 31, 2012 - 2:22pm #2

We'll look into this - had you attempted to update the targets shortly after creating them, or were these targets established in the DB prior to the update?

Log in or register to post comments