[Bucardo-general] long wait time and many rows in bucardo_delta

[Brady S Edwards]

Thank you for your response

I had the cron job disabled, and enabling it helped with the wait time for
the bucardo_ctl status.
I still have a large delta table that continues to grow.

As far as upgrading bucardo, would I be better off upgrading to 5 or 4.4.6?


On Sun, Nov 6, 2011 at 8:59 AM, Itamar Reis Peixoto <itamar at ispbrasil.com.br
> wrote:

> On Sun, Nov 6, 2011 at 1:51 PM, Brady S Edwards
> <brady.s.edwards at seagate.com> wrote:
> > Hello,
> > I'm currently running bucardo 4.4.2 on Postgresql 9.0.2 in a two db's
> > multi-master environment. Rtt is between the two db's is about 200ms.
> > Last week I stopped bucardo "bucardo_ctl stop", added three columns to
> one
> > of the tables in the sync, and then restarted bucardo.
> > I then performed a few hundred thousand updates on this table of which
> about
> > 3/4's of the updates did not make it to the remote db.
> > There are currently about 440000 entries in the bucardo_delta table.
> > bucardo_ctl status looks like:
> > Days back: 3  User: bucardo  Database: bucardo  PID of Bucardo MCP: 22765
> > Name          Type  State         PID   Last_good Time  I/U/D Last_bad
>  Time
> >
> =============+=====+=============+=====+=========+=====+=====+=========+=========
> > sync_xxxxx| S   |WAIT:42h49m6s|25009|unknown  |     |
> > |42h49m16s|27h20m36s
> > CO-Root@/var/log> bucardo_ctl status sync_xxxxx
> > Days back: 3  User: bucardo  Database: bucardo
> > ======================================================================
> > Sync name:            sync_xxxxx
> > Current state:        WAIT:42h 49m 16s (PID = 25009)
> > Type:                 swap
> > Source herd/database: xxxx2 / xxxx1
> > Target database:      xxxx2
> > Tables in sync:       24
> > Last good:            unknown
> > Ins/Upd/Del:
> > Last bad:             42h 49m 25s (time to run: 27h 20m 36s)
> > Last bad time:        Nov 04, 2011 15:36:10  Target: xxx2
> > Latest bad reason: Controller cleaning out unended q entry
> > PID file:             /var/run/bucardo/bucardo.ctl.sync.sync_xxxxx.pid
> > PID file created:     Fri Nov  4 15:36:09 2011
> > Status:               active
> > Limitdbs:             0
> > Priority:             0
> > Checktime:            none
> > Overdue time:         00:00:00
> > Expired time:         00:00:00
> > Stayalive:            yes      Kidsalive: yes
> > Rebuild index:        0        Do_listen: no
> > Ping:                 yes      Makedelta: no
> > Onetimecopy:          0
> > I'm wondering how I can resolve this.
> > I was thinking of stopping the client apps, stopping bucardo, disabling
> the
> > triggers on the table in question, perform the updates on both tables,
> > removing the entries for the table in question from the bucardo_delta
> table
> > and restarting everything.
> > Does this sound like a reasonable approach.
> > Thanks
> > --
> > Brady Edwards
> >
> >
>
> you need to upgrade to bucardo 4.4.6 and setup cron job
>
> http://bucardo.org/wiki/Bucardo/Cron
>
>
>
>
>
>
>
> --
> ------------
>
> Itamar Reis Peixoto
> msn, google talk: itamar at ispbrasil.com.br
> +55 11 4063 5033 (FIXO SP)
> +55 34 9158 9329 (TIM)
> +55 34 8806 3989 (OI)
> +55 34 3221 8599 (FIXO MG)
>



-- 
Brady Edwards
(720) 684-2984
Seagate Technology
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20111106/2e7c4663/attachment.html