Inconsistency in Redisson's RLiveObjectService.find() Method: Retrieving Outdated Data Despite Updates about redisson HOT 6 CLOSED

The search should be conducted based on the latest value of the status field, but it continues to retrieve objects with older status values, leading to inconsistency in the retrieved data.

you need to define readMode = MASTER setting in Redisson configuration.

from redisson.

Hi @mrniko Thanks for your reply, I believe default readmode would be a MASTER, anyway i tried with updating readMode to MASTER, but still issue exists.

from redisson.

Please set trace logging level for org.redisson and share the log output

from redisson.

@mrniko Thanks..! I understand your request for trace logging level output for org.redisson. However, due to the sensitive nature of the information contained within the logs—particularly regarding connection host-related entries—I am unable to share the entire log file.
In lieu of sharing the complete logs, I would like to highlight specific observations we have made during our debugging process.
LiveObjectSearch.class

 if (cond instanceof EQCondition) {
                EQCondition eqc = (EQCondition)cond;
                indexName = namingScheme.getIndexName(entityClass, eqc.getName());
                if (eqc.getValue() instanceof Number) {
                    values = new RedissonScoredSortedSet(namingScheme.getCodec(), this.commandExecutor, indexName, (RedissonClient)null);
                    eqNumericNames.put(values, (Number)eqc.getValue());
                } **else {
                    RSetMultimap<Object, Object> map = new RedissonSetMultimap(namingScheme.getCodec(), this.commandExecutor, indexName);
                    RSet<Object> values = map.get(eqc.getValue());
                    eqNames.add(((RedissonObject)values).getRawName());
                }**
            }

in org.redisson.liveobject.LiveObjectSearch.class Within this segment of else block(line 61), the instantiation of the 'map' object using the RedissonSetMultimap constructor indicates the retrieval of a set multimap indexed under a specific 'indexName'. Subsequently, the 'values' variable, representing the retrieved set, undergoes further processing.

However, it has come to my attention that the 'values' set contains entries encompassing older keys, some of which may have already expired. Additionally, the presence of keys associated with object values marked with a status of 'completed' is notable, particularly in scenarios where the queried 'eqc.getValue()' evaluates to 'processing'.

This discrepancy raises concerns regarding the integrity of the data retrieval process and suggests potential inconsistencies within the system's behavior.

I appreciate your understanding of this limitation and your willingness to collaborate in resolving this matter effectively. Please let me know if there are specific log excerpts or details you require, and I will do my utmost to provide them promptly.

from redisson.

Can you share some code snippet to reproduce the issue? Including RLiveObjectService.find() method

from redisson.

However, it has come to my attention that the 'values' set contains entries encompassing older keys, some of which may have already expired

you need to define Redis notify-keyspace-events setting contains the letters Kx.

from redisson.