Unusual HA behaviour in vertx

[webgeek webgeek]

I am relatively new to vertx but loving the learning curve!

I am trying to do a POC to simulate how HA works.

Both modules are running from the same 'repo' - a local repo

1. Deploy runmod com.x.y.z~mod1~1.0 -ha

    This starts a vertx instance - a class specified in "main": of the module

2. Deploy runmod com.x.y.z~mod2~1.0 -ha

    This starts, another vertx module instance

Below is what happens:

Hazzle cluster recognises the presence of both vertx modules

When I kill mod2, mod1 realises that mod2 has failed BUT it does not redeploy the failed module. Instead, it redeploys itself (mod1).

Would appreciate if someone can comment on what I might be doing wrong. Spent a day on this already 

[Tim Fox]

Please push a reproducer to GitHub, then someone can take a look :)

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.