On Tue, Mar 4, 2014 at 12:34 PM, Charlie Mason wrote:
> I have single node cluster I use for development on my local machine.
> After apt package upgrades and hard reboots the node takes a very long time
> to restart.
>
Regarding "after apt package upgrades", this is yet another case for :
https
On Tue, Mar 4, 2014 at 2:28 PM, Nate McCall wrote:
> The commit log replay is single threaded, so if you have a ton of
> overwrites in a whole lot of commit log (like you would with a queue
> pattern) it might be backing up.
>
> The only real work around to this right now would be to turn off dur
The commit log replay is single threaded, so if you have a ton of
overwrites in a whole lot of commit log (like you would with a queue
pattern) it might be backing up.
The only real work around to this right now would be to turn off durable
writes to the queue schema.
The following has some detai
Hi All,
I have single node cluster I use for development on my local machine. After
apt package upgrades and hard reboots the node takes a very long time to
restart.
The node will always eventually come back up however it takes ages
sometimes. It seems to be CPU bound as all 4 cores are maxed out
