[
https://issues.apache.org/jira/browse/KUDU-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Fancher reassigned KUDU-2033:
------------------------------------
Assignee: Edward Fancher
> Add a 'torture' scenario to verify Java client's behavior during fail-over
> ---------------------------------------------------------------------------
>
> Key: KUDU-2033
> URL: https://issues.apache.org/jira/browse/KUDU-2033
> Project: Kudu
> Issue Type: Test
> Components: client, java
> Reporter: Alexey Serbin
> Assignee: Edward Fancher
> Labels: newbie, newbie++
>
> For the Kudu Java client we have {{TestLeaderFailover}} test which verifies
> how the client handles the tablet server fail-over scenario. However, the
> test covers only one fail-over event and mainly performs write operations
> while the backend handles the 'unexpected crash' of the tablet server.
> It would be nice to add more tests which cover the client's fail-over
> behavior:
> * add the mixed workload scenario, i.e. combine inserts/scans during the
> fail-over
> * induce more fail-over events while running the scenario, i.e. pause and
> then resume the tservers processes many more times and run the test longer
> * add the multi-master scenario, where both the leader tserver and leader
> master 'unexpectedly crash' during the run
> * in the mixed workload scenarios, run scan operations in READ_AT_TIMESTAMP
> mode to exercise RYW (Read-Your-Writes) behavior and add assertions to make
> sure the RYW behavior is observed as expected
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
