[RTFACT-20086] Slow response from with Move API when conan user/channel changes Created: 09/Sep/19 Updated: 10/Sep/19
|Project:||Artifactory Binary Repository|
For example, performing a move without changing the user/channel works fine, with the HTTP call returning a response in less than half a second:
Afterwords, the new artifact is in the expected location, and the old artifact is gone (although the "/user/package/1.0.0" directory remains, even if empty).
However, attempting a move where the user/channel changes, the API never responds. Eventually the nginx reverse proxy we have in front of artifactory times out after 90 seconds, and returns a 504.
Afterwords, it appears that artifactory did successfully move the package to the new location, however, it leaves behind two "index.json" files and a ".timestamp" files (along with the directory structure containing them).
|Comment by Daniel Peacock [ 09/Sep/19 ]|
As an aside, when combined with a few other quirks of the move command, promoting conan artifacts is robustly rather tricky. This is the best I've gotten.
|Comment by Daniel Peacock [ 10/Sep/19 ]|
Okay, I got permissions needed to test behind the reverse proxy. The move API command does respond, it just takes 2 minutes, and then fails with a locking error:
It looks like this is a duplicate of