[
https://issues.apache.org/jira/browse/KUDU-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-1837.
---------------------------------
Resolution: Invalid
Fix Version/s: 1.4.0
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 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
> Fix For: 1.4.0
>
> 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)
