Affects Version/s: 4.16.0
Fix Version/s: None
For non-primary HA nodes, a message is being sent to the primary node when a .deb is uploaded to calculate metadata. When a .deb is deployed directly to the primary node, there is an aggregation of storage events (afterCreate, afterPropertyCreate) per-artifact - the same logic should also also be enforced on non-HA nodes, but it is missing. The result is multiple calculation cycles on the primary triggered for every .deb deployment (due to the three afterPropertyCreate events)
1.Setup ha with two nodes
2.Deploy some .deb to the slave node:
curl -XPUT -uadmin:password -T ~/some.deb "http://localhost:8082/artifactory/debian-local/pool/s/some.deb;deb.distribution=trusty;deb.component=main;deb.architecture=amd64"
3.Watch the artifactory.log of the primary node, it should state " Starting calculation of Debian metadata.." 3 times