delayed jobs (and binlogs)

[chadkouse]

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?

[Keith Rarick]

On Tue, Sep 25, 2012 at 9:31 PM, chadkouse <chad....@gmail.com> wrote:
> Is it by design that delayed jobs make binlogs hang around?

No. Compaction should ensure that the binlog only
takes space proportional to the amount of live data
in it.

Can you share your stats output from one of the
servers with a large binlog? (Feel free to send it to
me directly if you're not comfortable posting it
publicly.) I'm particularly interested in the
binlog-records-written and binlog-records-migrated
stats.

[Chad Kouse]

Ok I will get those stats if/when this happens again.  Thanks.

-- 

Chad Kouse

--

You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.

To post to this group, send email to beansta...@googlegroups.com.

To unsubscribe from this group, send email to beanstalk-tal...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.