<div class="gmail_quote">On Wed, Apr 13, 2011 at 10:33 AM, Vick Khera <span dir="ltr"><<a href="mailto:vivek@khera.org">vivek@khera.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><div class="gmail_quote">On Wed, Apr 13, 2011 at 12:55 PM, Richard Yen <span dir="ltr"><<a href="mailto:dba@richyen.com" target="_blank">dba@richyen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was wondering if there'd be any way to make that logswitch go faster (or perhaps more frequently)? Would anyone know how to minimize the size of sl_log_*? I was thinking about doing things like raising sync_interval to create less entries in </blockquote>
</div><br></div><div>Why? Was there some observable "bad" that was resulting from it taking so long? In particular, was your replication falling behind?</div><div></div></blockquote></div><div><br></div><div>
Well, I noticed that when the log gets large and it's in the middle of a logswitch, load on the origin node will increase and subsequent to that, all subscriber nodes will lag up to 900sec. This seems troublesome, considering that nodes in my cluster typically don't lag for more than 10sec--it's only during these logswitch events that they lag by so much.</div>
<div><br></div><div>--Richard</div>