[
https://issues.apache.org/jira/browse/KUDU-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898055#comment-15898055
]
Alexey Serbin commented on KUDU-1838:
-------------------------------------
Yes, it's still relevant. We haven't done any fixes since this issue reported.
The main fix would be to use multiple sessions instead of multiple clients.
That fix has not landed yet.
> kudu-jepsen reports non-linearizable history for the hammer-3-tservers
> scenario
> -------------------------------------------------------------------------------
>
> Key: KUDU-1838
> URL: https://issues.apache.org/jira/browse/KUDU-1838
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Alexey Serbin
> Labels: kudu-jepsen
> Attachments: 20170115T165415.000-0800.tar.bz2
>
>
> The kudu-jepsen test has found an instance of non-linearizable history for
> the hammer-3-tservers scenario. The artifacts from the failed scenario are
> attached.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
