No swap, we keep swap turned off following the "better to OOM than
slow down" theory. I'm gonna try to get GC's plotted for all of these
JVMs. I'm also finding instances where watches are fired but an
exception thrown inside the watch evaporates the thread without
exception handling and logging; I'm wrapping these.
But beyond all of that, I'm still on the hunt for guidelines for ZK
capacity sizing to get a sense of the performance and stability we
should expect with different heap sizes, ensemble sizes, number of
clients, unique watches, unique paths and update rates.
On Thu, Dec 6, 2012 at 5:34 PM, Ted Dunning <[EMAIL PROTECTED]> wrote:
> Is there any swap activity on the client or server boxes?
> On Thu, Dec 6, 2012 at 8:25 PM, Ian Kallen <[EMAIL PROTECTED]> wrote:
>> > d) ZK swapping out due to inactivity during memory pressure?
>> Can you cite an explanation or explain this here? I'm not sure what to
>> look for. It wouldn't be clients not detecting that they've lost their
>> session and creating a new one w/o the watches, "retrying" a znode
>> update does trigger the watch on the lapsed clients.