Thanks, Tim! That was exactly what it was. Apparently things didn't come completely back up, and it was falling back to the secondary. (obviously, I haven't written any puppet manifests for dns...:) )<br><br>--b<br>
<br><div class="gmail_quote">On Mon, Nov 21, 2011 at 3:45 PM, Tim Nelson <span dir="ltr"><<a href="mailto:tnelson@rockbochs.com">tnelson@rockbochs.com</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">----- Original Message -----<br>
> I had a power failure in my home a couple of weeks ago, and ever<br>
> since, VMs on my OpenVZ machine. I noticed that it would take several<br>
> seconds to log into VMs. However, I have just deployed Puppet and<br>
> really noticed large amounts of lag that for the few recipes I have<br>
> written so far. The puppetmaster What would normally take 1-2 seconds<br>
> or less in other environs takes anywhere from 30-40 seconds to up to<br>
> 250 seconds to run a catalog. I suspect that it is making multiple<br>
> connections, each suffering the lag.<br>
><br>
<br>
</div>It sounds like you're having DNS resolution failures and the delay you experience is how long it takes for the queries to timeout.<br>
<br>
--Tim<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://openvz.org/mailman/listinfo/users" target="_blank">https://openvz.org/mailman/listinfo/users</a><br>
</blockquote></div><br>