curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cameron McKenzie <mckenzie....@gmail.com>
Subject Re: CURATOR-3.0 tests
Date Tue, 14 Jun 2016 03:54:20 GMT
Done, have created a PR.

On Mon, Jun 13, 2016 at 1:22 PM, Cameron McKenzie <mckenzie.cam@gmail.com>
wrote:

> Yep, I will try and do it tomorrow
> On 13 Jun 2016 1:19 PM, "Jordan Zimmerman" <jordan@jordanzimmerman.com>
> wrote:
>
>> Sure - you OK doing it?
>>
>> > On Jun 12, 2016, at 10:09 PM, Cameron McKenzie <mckenzie.cam@gmail.com>
>> wrote:
>> >
>> > It could probably just be the remaining amount of time until session
>> > timeout couldn't it? We should know at what time the last event was as
>> we
>> > use this to calculate when the list event occurs
>> > On 13 Jun 2016 12:54 PM, "Jordan Zimmerman" <jordan@jordanzimmerman.com
>> >
>> > wrote:
>> >
>> >> Yeah - that was my thinking but, really, it could be done more often.
>> >> Maybe 1/3 instead of 2/3? It wouldn’t do any harm really. Just as long
>> as
>> >> it doesn’t turn into a spin loop.
>> >>
>> >> -Jordan
>> >>
>> >>> On Jun 7, 2016, at 2:13 AM, Cameron McKenzie <mckenzie.cam@gmail.com>
>> >> wrote:
>> >>>
>> >>> Jordan, do you remember what the rationale behind only waiting for
>> 2/3 of
>> >>> the session timeout is? It's something to do with the way that ZK
>> itself
>> >>> handles session timeouts isn't it? Does ZK timeout the session if it
>> >> hasn't
>> >>> received a heartbeat for 2/3 of the session timeout? I can't remember.
>> >>> cheers
>> >>
>> >>
>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message