sadanand48 commented on PR #5445:
URL: https://github.com/apache/ozone/pull/5445#issuecomment-1782348910
Yes @ChenSammi , The inconsistency problem is solved in the current patch by
adding a delete marker in the cache but since cache has a bound, it can cause
issues. Like I mentioned above , The changes that need to be made in this PR are
- make guava cache unbounded . This can be simply done by not setting
maximumSize and expiryTime in the cache builder as by default behaviour is
unbounded
``` java
cache = CacheBuilder.newBuilder()
.expireAfterWrite(expireTime)
.maximumSize(maxSize)
.build();
```
- During double buffer flush the cache needs to be invalidated
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
