UriDeploymentSpi Possible Bug

[Ibrahim Altun <ib...@segmentify.com>]

Hi,

I've spotted a strange behaviour on UriDeploymenySpi module, I am not sure
if this behaviour is expected or not, can anybody clarify it please;

We are getting following log on clusters as expected

[2021-12-09T09:49:06,363][INFO ][grid-uri-scanner-#2-#23][UriDeploymentSpi]
Found new or updated deployment unit
[uri=file:///usr/share/apache-ignite/libs/segmentify/cacheentryprocessor-09122021.jar,
file=/data/ignite/temp_ignite_libs/gg.uri.deployment.tmp/bb34f617-91d1-4b5e-ba3c-b3e23129d6dd/cacheentryprocessor-091220212552686432429770561.jar,
tstamp=1639043345000]

[2021-12-09T09:49:06,368][WARN ][grid-uri-scanner-#2-#23][UriDeploymentSpi]
Processing deployment without descriptor file (it will cause full classpath
scan) [path=META-INF/ignite.xml,
package=/data/ignite/temp_ignite_libs/gg.uri.deployment.tmp/bb34f617-91d1-4b5e-ba3c-b3e23129d6dd/dirzip_cacheentryprocessor-091220212552686432429770561.jar]

What we expect with this deployment is that all
cache-entry-proccessor classes be updated/redeployed on cluster nodes, but
they are not.

If we add a new class we can use it without any problem, but when an
already defined class is updated (only additional lines) the cluster keeps
using the old one. Additionally when a node is restarted in the cluster
after then an updated class can be used.

Is this expected or am I missing something?

Thanks.

-- 
<https://www.segmentify.com/>İbrahim Halil AltunSenior Software Engineer+90
536 3327510 • segmentify.com → <https://www.segmentify.com/>UK • Germany •
Turkey <https://www.segmentify.com/ecommerce-growth-show>
<https://www.g2.com/products/segmentify/reviews>