[
https://issues.apache.org/jira/browse/KUDU-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1825:
------------------------------
Attachment: history.txt
linear.svg
Attaching the SVG and history file for this run.
>From my understanding of these, it looks like somehow we are reading a value
>'2' even though we never wrote that value. The '2' must be leftover from an
>earlier test run or somesuch, and perhaps shows up as readable just after the
>servers restart. Merits further investigation.
> kudu-jepsen reports non-linearizable history for 'kill-all-tservers' scenario
> -----------------------------------------------------------------------------
>
> Key: KUDU-1825
> URL: https://issues.apache.org/jira/browse/KUDU-1825
> Project: Kudu
> Issue Type: Bug
> Reporter: Alexey Serbin
> Attachments: history.txt, linear.svg
>
>
> One of the iterations of the kudu-jepsen test hit non-linearizable history of
> opertions: http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/82/
> It's necessary to create a reproducible scenario for that and fix the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
