[infinispan-issues] [JBoss JIRA] Commented: (ISPN-575) Corruption in data when using a permanent store

[Sanne Grinovero (JIRA)]

    [ https://jira.jboss.org/browse/ISPN-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12544200#action_12544200 ] 

Sanne Grinovero commented on ISPN-575:
--------------------------------------

please see ISPN-590 too, it appears the Lucene directory was writing a value twice using SKIP_LOCK. Fixing it the corruptions were not reproduced anymore.

It is writing the second value in the same thread which wrote the first value, so even if the SKIP_LOCK might be questionable as this value is not totally immutable, I would expect the order of operations to be safe and be able to read only the lastly put value after that, while it appears that in some situations under load - when the store is enabled only - I will get() the first written value instead of the last one.

> Corruption in data when using a permanent store
> -----------------------------------------------
>
>                 Key: ISPN-575
>                 URL: https://jira.jboss.org/browse/ISPN-575
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Loaders and Stores
>    Affects Versions: 4.0.0.Final, 4.1.0.CR2
>            Reporter: Sanne Grinovero
>            Assignee: Galder Zamarreno
>            Priority: Critical
>             Fix For: 4.1.0.CR3, 4.1.0.Final
>
>         Attachments: [ISPN-575]_(Corruption_in_data_when_using_a_permanent_store)_Extra_debugging_info_.patch, ISPN-575-previewOfTest-dontapply.patch
>
>
> We verified the issue while using the Lucene Directory; using the Directory under stress leads to no issues even during long running tests of several hours.
> If during the same stress test a permanent store is enabled, all works still fine, until the CacheManager is stopped. No errors during the stop(), but after starting it again the checksum on some data fails and the index is unusable.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira