We've seen twice now a circumstance where a small number of jobs get "stuck" in a delayed state. We are still tracking down the cause of the delay to make sure it's not an application bug actually telling beanstalkd to delay these jobs for a large amount of time. But in the meantime we notice binlogs begin backing up.
We are running version: 1.6+4+g236c669 and this most recent incident had binlogs from 6 days ago forward (about 50GB worth). The only way we can work around this issue is to remove the server from production, let any ready-state jobs get consumed, stop the service, manually delete the binlog files, and start the service back up. Is it by design that delayed jobs make binlogs hang around? -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/W-jFPHj1W24J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
