[
https://issues.apache.org/jira/browse/KUDU-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966917#comment-15966917
]
Alexey Serbin edited comment on KUDU-1825 at 4/13/17 12:33 AM:
---------------------------------------------------------------
This bug is not valid since the kudu-jepsen ran in wrong client model: using a
separate Kudu client per test actor. That model would require to propagate
timestamp between clients for sound test results, but that was not the case.
The client model has been updated by changelist
678a309b5d88e2fe9c6a0674ba7de00daee35cac: since then all test actors share the
same Kudu client instance, so timestamp is propagated automatically.
After the client model has been updated, no error occurred so far. If any new
issues is found by the new kudu-jepsen code, please open a new JIRA item for
that.
was (Author: aserbin):
This bug is not valid since the kudu-jepsen ran in wrong client model: using a
separate Kudu client per test actor. That model would require to propagate
timestamp between clients for sound test results, but that was not the case.
The client model has been updated by changelist
678a309b5d88e2fe9c6a0674ba7de00daee35cac: since then all test actors share the
same Kudu client instance, so timestamp is propagated automatically.
> kudu-jepsen reports non-linearizable history for the
> kill-restart-all-tservers scenario
> ---------------------------------------------------------------------------------------
>
> Key: KUDU-1825
> URL: https://issues.apache.org/jira/browse/KUDU-1825
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Labels: kudu-jepsen
> Fix For: 1.4.0
>
> 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 for
> kill-restart-all-tservers scenario.
> The artifacts of the failed scenario are attached.
> It's necessary to create reproducible scenarios for that and fix, if possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
