Reusing taskIds may work if you're guaranteed to never be running two
instances of the same taskId simultaneously, but I could imagine a
particularly dangerous scenario where a master and slave experience a
network partition, so the master declares the slave lost and therefore its
tasks lost, and
I'd be most curious to see a working example of this idea, prefixes
and all for sleeping (long term sleeping) nodes (slave and masters).
Anybody, do post what you have/are doing on this taskid resuse and
reservations experimentations. Probably many are interested for a
variety of reasons
2 matches
Mail list logo
