[ https://issues.apache.org/jira/browse/KUDU-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15891347#comment-15891347 ]
David Alves commented on KUDU-1837: ----------------------------------- Well I found something very wrong with our client that could certainly cause it (we're using one client instance per thread vs using the same one across all threads), but not 100% sure that is the only cause. As soon as I have some spare cycles will work on that. > kudu-jepsen reports non-linearizable history for the tserver-majorities-ring > scenario > ------------------------------------------------------------------------------------- > > Key: KUDU-1837 > URL: https://issues.apache.org/jira/browse/KUDU-1837 > Project: Kudu > Issue Type: Bug > Affects Versions: 1.2.0 > Reporter: Alexey Serbin > Labels: kudu-jepsen > Attachments: 20170115T142504.000-0800.tar.bz2 > > > The kudu-jepsen test has found an instance of non-linearizable history for > the tserver-majorities-ring scenario. The artifacts from the failed scenario > are attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)