You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2017/01/17 16:02:26 UTC
[jira] [Updated] (KUDU-1825) kudu-jepsen reports non-linearizable
history for some scenarios
[ https://issues.apache.org/jira/browse/KUDU-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated KUDU-1825:
--------------------------------
Assignee: Alexey Serbin
Description:
The kudu-jepsen test found non-linearizable history of operations:
* http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/82/
* http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/139/
* http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/140/
It's necessary to create reproducible scenarios for that and fix, if possible.
Logs and other artifacts for job_id 82 are attached; for 139 and 140 can be downloaded from Jenkins.
was:
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.
Summary: kudu-jepsen reports non-linearizable history for some scenarios (was: kudu-jepsen reports non-linearizable history for 'kill-all-tservers' scenario)
> kudu-jepsen reports non-linearizable history for some scenarios
> ---------------------------------------------------------------
>
> Key: KUDU-1825
> URL: https://issues.apache.org/jira/browse/KUDU-1825
> Project: Kudu
> Issue Type: Bug
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Attachments: history.txt, linear.svg, master.log, ts-1.log, ts-2.log, ts-3.log, ts-4.log, ts-5.log
>
>
> The kudu-jepsen test found non-linearizable history of operations:
> * http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/82/
> * http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/139/
> * http://sandbox.jenkins.cloudera.com/view/Kudu/job/kudu-jepsen/140/
> It's necessary to create reproducible scenarios for that and fix, if possible.
> Logs and other artifacts for job_id 82 are attached; for 139 and 140 can be downloaded from Jenkins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)