Hi! I'm not sure how is this possible, but I am getting this situation. My worker is constantly doing "reserve-with-timeout", and then, after it successfully processed a job, it does "delete" operation. After some time worker starts acting bad: when it does "delete" it gets response "TIMED_OUT", and after that upon "reserve-job-with-timeout" it gets "DELETED" response.
Beanstalk's -VVV log shows a proper log (delete->DELETED, reserve-with-timeout->TIMED_OUT), but tcpflow and tcpdump confirm wrong ordering: ``` 010.054.080.157.46153-010.122.036.080.11300: reserve-with-timeout 3 010.122.036.080.11300-010.054.080.157.46153: TIMED_OUT 010.054.080.157.46153-010.122.036.080.11300: delete 1211 010.122.036.080.11300-010.054.080.157.46153: TIMED_OUT 010.122.036.080.11300-010.054.080.157.46153: DELETED 010.054.080.157.46153-010.122.036.080.11300: reserve-with-timeout 3 010.054.080.157.46153-010.122.036.080.11300: reserve-with-timeout 3 010.122.036.080.11300-010.054.080.157.46153: TIMED_OUT ``` Any advice what could go wrong? Thanks! -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/d/optout.
