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

IMap entries with Max-Idle not expiring when member shuts down #13630

Closed
Danny-Hazelcast opened this issue Aug 24, 2018 · 6 comments
Closed

IMap entries with Max-Idle not expiring when member shuts down #13630

Danny-Hazelcast opened this issue Aug 24, 2018 · 6 comments

Comments

@Danny-Hazelcast
Copy link
Member

@Danny-Hazelcast Danny-Hazelcast commented Aug 24, 2018

in this cluster member controlled shutdown restart test, with map put max idle.

https://hazelcast-l337.ci.cloudbees.com/view/shutdown/job/shutdown-x/122/console

we see

/disk1/jenkins/workspace/shutdown-x/3.11-BETA-1/2018_08_23-16_19_27/max-idle Failed

fail HzClient3HZ maxIdle_map-putWaitGetHD hzcmd.map.PutTtlMaxIdleWaitGetNull threadId=3 global.AssertionException: val not null mapBak1HD-maxIdle_map-putWaitGetHD-17 key=1992950290 val=[B@553853eb 

http://54.82.84.143/~jenkins/workspace/shutdown-x/3.11-BETA-1/2018_08_23-16_19_27/max-idle

in the stable cluster version of this test, we do not see val not null

the operation/function hzcmd.map.PutTtlMaxIdleWaitGetNull is

https://github.com/hazelcast/hzCmd-bench/blob/zeta/src/main/java/hzcmd/map/PutTtlMaxIdleWaitGetNull.java

http://54.82.84.143/~jenkins/workspace/shutdown-x/3.11-BETA-1/2018_08_23-16_19_27/max-idle/put

where we put in entry with a max idle and a TTL of 0, then wait for max idle expiration.

get the same entry and assert that it is null. all threads of all drivers make put operations on a there own map which has a unique name to each thread running PutTtlMaxIdleWaitGetNull

@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Aug 24, 2018

although in the test described above. the cluster version is 3.11 and members are being shutdown.

could the issue below (multi version stable cluster) be related
#13618

@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Aug 24, 2018

I also note that this issue / test is failing randomly, it is possible to have passing and failing run's
of the same test.

@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Aug 24, 2018

I also note that i do not see the put TTL version of this test failing in the same way.

@vbekiaris vbekiaris self-assigned this Aug 24, 2018
@tkountis tkountis changed the title map put max idle member shutdown items not expired. IMap entries with Max-Idle not expiring when member shuts down Aug 24, 2018
@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Aug 24, 2018

@vbekiaris i also see in this test

https://hazelcast-l337.ci.cloudbees.com/view/split/job/split-multi-v/39/console

a split brain test, that it looks like put TTL also has the same kind of issue.

fail HzClient3HZBB putTTL_mapBak1 hzcmd.map.PutTtlWaitGetNull threadId=0 global.AssertionException: val not null mapBak1_putTTl-6 key=972221479 val=[B@5ed7e698 
@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Aug 24, 2018

now i see that the TTL shutdown test has also started to fail.

https://hazelcast-l337.ci.cloudbees.com/view/shutdown/job/shutdown-x2/37/console

which i think is a regression.

@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Aug 27, 2018

in this shutdown MAX idle test https://hazelcast-l337.ci.cloudbees.com/view/shutdown/job/shutdown-x/131/console
I reduced the delay
max idle was 1 second, and the delay before get was 1 seconds
and got the fail.
however now i re-check but getting the key/val again
and i see that it will return null so the value is expired in the end.

and @vbekiaris fix also looks like it fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.