[GitHub] eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads.

eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads. URL: https://github.com/apache/bookkeeper/pull/1804#issuecomment-438162643 Okay, we don't need this. This is an

[GitHub] eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads.

eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads. URL: https://github.com/apache/bookkeeper/pull/1804#issuecomment-438010582 maybe the errors on recovery are due to the fact that reads should strictly respect the order

[GitHub] eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads.

eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads. URL: https://github.com/apache/bookkeeper/pull/1804#issuecomment-437918755 there are still a lot of errors This is

[GitHub] eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads.

eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads. URL: https://github.com/apache/bookkeeper/pull/1804#issuecomment-437870131 retest this please This is an automated

[GitHub] eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads.

eolivelli commented on issue #1804: [client] read submission for readonly handle should bypass OSE threads. URL: https://github.com/apache/bookkeeper/pull/1804#issuecomment-437576491 In client tests there are a lot of failure around fencing. This is quite scary