Foreign node in queue path causes infinite loop

[netflix]

Foreign node in queue path causes infinite loop

[Randgalt]

I don't see the infinite loop. Do you have an example?

[trevorbernard]

Yes, initially empty queue and you enqueue a message that doesn't start with "queue-" and it will try and process that message forever.

Sent from my iPhone

On 2012-02-22, at 2:14 PM, Jordan [email protected] wrote:

I don't see the infinite loop. Do you have an example?

---

Reply to this email directly or view it on GitHub:
#30 (comment)

[Randgalt]

I see. I'm not sure what to do about this. I think it would be wrong for Curator to delete the node. When I wrote the code my intention was that having foreign nodes is an error. Do you have a suggestion for how to handle this? Otherwise, I'd say make sure the path's children are clean before passing the path to Curator.

[Randgalt]

I haven't heard back from you on this so I'll close this issue.

[trevorbernard]

The email must have got lost in the shuffle. I don't know what's the correct behaviour or not. I suppose you can implement the appropriate access controls to make sure only queue znodes get created and make this a non-issue. However, if I was doing something like this in production, I would favour dropping since the SLA between producer and consumer would be well defined.

[Randgalt]

How did the foreign node get in there? Did you re-use the path?

[trevorbernard]

zkCli :)

[Randgalt]

OK. I view this as a user error. Under normal use it should never happen.