Re: [Proposal] Change default gemfire.memoryEventTolerance from 1 to 0

2019-01-24 Thread Alexander Murmann
lk to Alexander directly? > >> > >> Ryan > >> > >> -- Forwarded message - > >> From: Alexander Murmann > >> Date: Wed, Jan 23, 2019 at 4:13 PM > >> Subject: Re: [Proposal] Change default gemfire.memoryEventTolerance from &

Re: [Proposal] Change default gemfire.memoryEventTolerance from 1 to 0

2019-01-24 Thread Ryan McMahon
;> Ryan >> >> ------ Forwarded message ----- >> From: Alexander Murmann >> Date: Wed, Jan 23, 2019 at 4:13 PM >> Subject: Re: [Proposal] Change default gemfire.memoryEventTolerance from >> 1 to 0 >> To: >> Cc: Ryan McMahon >> >> &

Re: [Proposal] Change default gemfire.memoryEventTolerance from 1 to 0

2019-01-23 Thread Alexander Murmann
Ryan, thank you so much for the great explanation of your proposal! This seems very sound and you and David got me convinced that it's the right thing to change the default. To me the question now is one of timing. Is this something we can change in a minor release or do we have to wait for Geode

Re: [Proposal] Change default gemfire.memoryEventTolerance from 1 to 0

2019-01-22 Thread David Wisler
I would add that, by changing the default to 0, we can then skip all of the "special" logic that almost no customers use.With a default of 1, we go into this logic every time unnecessarily, even when customers have not explicitly told us to "tolerate" an eviction or critical state change.I