Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests newly created recordStores after imap#destroy references same M… #7884

Conversation

ahmetmircik
Copy link
Member

…apContainer

Test for the PR: #7838

@ahmetmircik ahmetmircik added this to the 3.6.3 milestone Mar 31, 2016
private static final int PARTITION_COUNT = 271;

@Test
public void testNewRecordStores_sharesSameMapContainerInstance_afterMapDestroy() throws Exception {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you please describe the scenario this test is checking? it's not very clear from the name as it's a bit ambiguous.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@ahmetmircik ahmetmircik force-pushed the fix/3.6.3/mapContainerStressTest branch from 643ea34 to e31d310 Compare April 1, 2016 09:16
…apContainer instance.

Normally, we remove mapContainer in map#destroy operation. If we call map#put after map#destroy, a new mapContainer instance is created
and all newly created recordStores references that new mapContainer instance. That referenced mapContainer instance should be the new-mapContainer-instance
 because we previously called map#destroy and removed old mapContainer instance.

This test trying to be sure that after map#destroy those all newly created recordStore instances references same
single mapContainer instance by stressing mapContainer creation process with subsequent map#put and map#destroy operations.
@ahmetmircik ahmetmircik force-pushed the fix/3.6.3/mapContainerStressTest branch from e31d310 to 7e78280 Compare April 1, 2016 09:19
@ahmetmircik
Copy link
Member Author

Test for the PR: #7838, merging this one.

@ahmetmircik ahmetmircik merged commit de7eead into hazelcast:maintenance-3.x Apr 1, 2016
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Team: Core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants