This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
The Last update time of map entries used by evictors is lost in a shard replication
The following details have been provided in 08953,442,000 and we have been told to raise a RFE to get the issue fixed. This is a HIGH priority issue to ODM, because it implies a bug in the ODM DSI product and a customer has already fall into it few times.
Detail: For a map with a ttlEvictorType of type LAST_UPDATE_TIME, the last update time of map entries is reset when a map is replicated to another server that has just been started. As a result, if the map in the new server becomes primary, the evictor acts as if the LAST_UPDATE_TIME was the data at which the server started. This is highly visible in ripple start scenarios (when you need to stop and restrart servers one by one for maintainance , for example server update for security fixes and reboot). In that case the LAST_UPDATE_TIME for all the grid entries is lost.
This is seen with Xtreme Scale 22.214.171.124 (+ latest IFIX) - but alo with previous releases.
Do not place IBM confidential, company confidential, or personal information into any field.