[
https://issues.apache.org/jira/browse/GEODE-9671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437647#comment-17437647
]
Darrel Schneider commented on GEODE-9671:
-----------------------------------------
It turns out that this test had an invalid expectation. It thought that if it
killed the primary during a zadd that the zadd would be done only once. But it
can actually be done once or twice. Jedis sees that the server it was connected
to died and retries the zadd. But the first zadd could have actually completed
on the secondary server. In that case the retry goes to this server (the old
secondary becomes the new primary) and ends up doing the zadd twice.
To fix this test it how expected the zadd to have been done once or twice when
a server crash happens.
> ZAddIncrOptionDUnitTest.zAddWithIncrOptionCanIncrementScoresDuringPrimaryIsCrashed
> Fails
> ----------------------------------------------------------------------------------------
>
> Key: GEODE-9671
> URL: https://issues.apache.org/jira/browse/GEODE-9671
> Project: Geode
> Issue Type: Test
> Components: redis
> Reporter: Wayne
> Assignee: Darrel Schneider
> Priority: Major
>
> The
> ZAddIncrOptionDUnitTest.zAddWithIncrOptionCanIncrementScoresDuringPrimaryIsCrashed
> test is currently failing and is annotated with @Ignore. The @Ignore
> annotation indicates that the test failure is due to GEODE-9310 and
> GEODE-9311. However, both of these tickets indicate that they have been
> fixed. The test needs to be investigated to see why the failure is still
> occurring.
> +Acceptance Criteria+
> The
> ZAddIncrOptionDUnitTest.zAddWithIncrOptionCanIncrementScoresDuringPrimaryIsCrashed
> test no longer fails and the @Ignore annotation has been removed.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
