You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by 周倩 <zh...@126.com> on 2022/05/12 09:08:46 UTC
Fw:Expiry Policy can not working in gridgain 8.8.9
Hi,
I have a question while using gridgain 8.8.9.
I have CityKey and City objects,when i specified the CityKey.COUNTRYCODE as a affinity key,
The Expiry Policy didn‘t work.
I put one thousand pieces of data to the cache,the key is CityKey object and the value is City object ,and the expiry time is one minute.one minute later,only two pieces of data were removed, then i used cache -scan command in visor ,all the data were removed ,but if i used cache command , the data would always exist.
IF I removed the @AffinityKeyMapped annotation on CityKey.COUNTRYCODE,the expiry policy could work.
I did the same test with gridgain 8.8.18,and the expiry policy worked all the time.
So I wonder to know if this is a bug in gridgain 8.8.9,
If it’s not a bug, what’s the reason and how to solve it.
Attachments are CityKey and City objects and my test code.
Thanks.
I'll wait for your reply .
Here is the gridgain visor output.
|
visor> cache
Time of the snapshot: 2022-05-12 15:24:33
| Name(@) | Mode | Nodes | Total entries (Heap / Off-heap) | Primar
y entries (Heap / Off-heap) | Hits | Misses | Reads | Writes |
| testcity(@c0) | PARTITIONED | 1 | 1000 (0 / 1000) | min: 1
000 (0 / 1000) | min: 0 | min: 0 | min: 0 | min: 0 |
| | | | | avg: 1
000.00 (0.00 / 1000.00) | avg: 0.00 | avg: 0.00 | avg: 0.00 | avg: 0.00 |
| | | | | max: 1
000 (0 / 1000) | max: 0 | max: 0 | max: 0 | max: 0 |
+-------------------------------------------------------------------------------
----------------------------------------------------------------------------+
Use "-a" flag to see detailed statistics.
visor> cache
Time of the snapshot: 2022-05-12 15:26:50
| Name(@) | Mode | Nodes | Total entries (Heap / Off-heap) | Primar
y entries (Heap / Off-heap) | Hits | Misses | Reads | Writes |
| testcity(@c0) | PARTITIONED | 1 | 998 (0 / 998) | min: 9
98 (0 / 998) | min: 0 | min: 0 | min: 0 | min: 0 |
| | | | | avg: 9
98.00 (0.00 / 998.00) | avg: 0.00 | avg: 0.00 | avg: 0.00 | avg: 0.00 |
| | | | | max: 9
98 (0 / 998) | max: 0 | max: 0 | max: 0 | max: 0 |
+-------------------------------------------------------------------------------
----------------------------------------------------------------------------+
Use "-a" flag to see detailed statistics.
visor> cache -scan
Time of the snapshot: 2022-05-12 15:28:42
+===============================================================+
| # | Name(@) | Mode | Size (Heap / Off-heap) |
+===============================================================+
| 0 | testcity(@c0) | PARTITIONED | min: 998 (0 / 998) |
| | | | avg: 998.00 (0.00 / 998.00) |
| | | | max: 998 (0 / 998) |
+---------------------------------------------------------------+
Choose cache number ('c' to cancel) [c]: 0
Cache: testcity is empty
visor>
|
Re:Re: Fw:Expiry Policy can not working in gridgain 8.8.9
Posted by 周倩 <zh...@126.com>.
Hi Andrey,
Thank you for your reply.Actually i did the same test with gridgain 8.7.26,and the expiry policy worked too.So I'm confused.
At 2022-05-12 17:54:18, "Andrey Mashenkov" <an...@gmail.com> wrote:
Hi,
You wrote to the Apache Ignite user list.
Apache Ignite and Gridgain are different projects with their own lifecycles and roadmaps.
BTW, this looks like an issue in 8.8.9 that is already fixed in 8.8.18.
Please contact the vendor for details.
Re: Fw:Expiry Policy can not working in gridgain 8.8.9
Posted by Andrey Mashenkov <an...@gmail.com>.
Hi,
You wrote to the Apache Ignite user list.
Apache Ignite and Gridgain are different projects with their own lifecycles
and roadmaps.
BTW, this looks like an issue in 8.8.9 that is already fixed in 8.8.18.
Please contact the vendor for details.