Problem description: Uploading a RubyGem package, either through the /api/gems endpoint or via manually uploading the *.gem package, does not trigger indexing. This is when the upload is sent to the Secondary node in an HA cluster.
Oddly enough uploads to the primary HA node triggers the expected behavior.
This is a problem for users who have an HA setup with the Primary outside of the load balancer. Their only option is to manually recalculate the index every few seconds to keep the metadata up to date.
What is the expected behavior? Uploads to any node in the HA cluster trigger indexing.
Steps to reproduce:
1] Install an Artifactory 7.10.2 HA cluster (Docker installation), set it up with a MySQL database
2] Set up the basic RubyGem repositories, a gems-local repo is needed
3] Bypass any load balancer and directly upload a Gem package onto the Secondary node under the "gems-local/gems" folder
4] Note that indexing does not trigger on the Primary nor the Secondary, even after several minutes have passed
5] Upload the same Gem file to the Primary, and note that the indexing triggers as expected
Enable node affinity by adding this Artifactory System Property:
[ $JFROG_HOME/var/etc/artifactory/artifactory.system.properties ]