Red Hat Bugzilla – Bug 842921
Clarify effect of Passivation configuration option
Last modified: 2012-09-19 23:48:02 EDT
Paragraph 126.96.36.199 currently reads:
188.8.131.52. The Cache Loader and Cache Passivation
In JBoss Data Grid, a cache loader can be used to enforce the passivation of entries and to activate eviction in a cache. Whether passivation mode or activation mode are used, the configured cache loader both reads from and writes to the data store.
When passivation is enabled in JBoss Data Grid, after the modification, addition or removal of an element is carried out the cache loader steps in to persist the changes in the store.
I think it's very confusing and the second sentence is likely wrong. We would need to clarify the difference between options passivation="true" or passivation="false". It would help to refer to table Table 10.1 or Table 10.2 as well.
Emailed Sanne for clarification about the first part of this comment.
To address ref to table 10.1/table 10.2 comment, adding links to tables outlining what occurs when passivation is on and off.
To clarify my first comment, the culprit of my doubt is in the wording
"When passivation is enabled [..] after modification, addition or removal [..] the cacheloader steps in to persist the changes"
While reading - especially the first sentence:
that seems to be the behaviour when a CacheLoader is DISABLED; when it is enabled the cacheloader should step in on an eviction event, not any other modification.
I'm not sure that a CacheLoader doesn't trigger *also* on a modification; asking someone on the Infinispan team to confirm this.
@Sanne +1, the behaviour described in the sentence you quoted is incorrect. The sentence should state "When the passivation is *disabled* .. "
Apologies, Sanne, I was looking at the first sentence of the first paragraph from the content you posted in the original post, not the first sentence of the second paragraph. Thanks for the clarifications, both of you!
Change made, will move this bug to ON_QA once it appears on the stage for verification.
This change now appears on the stage: