2018-03-13 17:19 GMT+01:00 Ivan Kelly :
> > @Ivan
> > I wonder if some tests on Jepsen with bookie restarts may find this kind
> of
> > issues, given that it is not a network/SO problem
> If jepsen can catch then normal integration test can. The readers in
> question, are they tailing with long po
> @Ivan
> I wonder if some tests on Jepsen with bookie restarts may find this kind of
> issues, given that it is not a network/SO problem
If jepsen can catch then normal integration test can. The readers in
question, are they tailing with long poll, or just calling
readLastAddConfirmed in a loop? W
Findings of today:
A - the system fails even with BK 4.6.0
B - we have moved all the clients and the bookies to different machines
(keeping the same ZK cluster), same problem
C - I have copies of the application which are running on other similar
machines (on the same Blade/VMWare system)
D - I hav
On Tue, Mar 13, 2018 at 12:42 AM, Enrico Olivelli
wrote:
> Good idea
> I have already responded on the PR
>
> Summary of my response:
>
>1. okay to make it the default
>2. may this change break existing tests, or at least change the meaning
>of what is tested ?
>3. we should add a
Good idea
I have already responded on the PR
Summary of my response:
1. okay to make it the default
2. may this change break existing tests, or at least change the meaning
of what is tested ?
3. we should add a test about this change, at least on the new API
Enrico
2018-03-13 8:4
Hi all,
I am raising a discussion to set `ENABLE_DIGEST_TYPE_AUTODETECTION' to true
to turn on this feature by default. because `digest type` has been
recorded in ledger metadata since 4.5, it is better for client to use the
digest type recorded in ledger metadata.
Here is a proposal of the chan
