[
https://issues.apache.org/jira/browse/CASSANDRA-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995732#comment-13995732
]
Russ Hatch commented on CASSANDRA-6626:
---------------------------------------
With the recent work on the upgrade tests I changed the counters testing there
a little bit.
Now the test creates 100 separate counter cells. These are updated randomly for
15 seconds (so we'll get sorta even distribution of counts across the 100).
Then the counts are read back and compared to expected values. On some versions
I was running into very slow counter updates which is why I opted for a max
time approach instead of a fixed count, though in retrospect maybe those very
slow scenarios are worth investigating more.
[~iamaleksey] does this update seem like reasonable coverage, or should we
extend it a bit more? Let me know if there's any specifics you'd want to see
covered in a test.
> Create 2.0->2.1 counter upgrade dtests
> --------------------------------------
>
> Key: CASSANDRA-6626
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6626
> Project: Cassandra
> Issue Type: Test
> Reporter: Aleksey Yeschenko
> Assignee: Russ Hatch
> Fix For: 2.1 rc1
>
>
> Create 2.0->2.1 counter upgrade dtests. Something more extensive, yet more
> specific than
> https://github.com/riptano/cassandra-dtest/blob/master/upgrade_through_versions_test.py
--
This message was sent by Atlassian JIRA
(v6.2#6252)
