Bug 1235140

Summary: Async stores can lose updates
Product: [JBoss] JBoss Data Grid 6 Reporter: Dan Berindei <dberinde>
Component: InfinispanAssignee: Tristan Tarrant <ttarrant>
Status: VERIFIED --- QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: chuffman, jdg-bugs, vjuranek
Target Milestone: ER1   
Target Release: 6.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
<classname>AsyncCacheWriter</classname> could drop updates if it was unable to write <literal>modificationQueueSize</literal> entries within the <parameter>shutdownTimeout</parameter>, as older changes overwrote newer ones in the back-end store. This issue was primarily caused by a large queue size or a slow back-end store with a relatively small <classname>AsyncStore</classname> <parameter>shutdownTimeout</parameter> (25 seconds by default). Now <classname>AsyncStore</classname> will write everything to the backing store before shutting down, and the <parameter>shutdownTimeout</parameter> has been removed. This issue is resolved as of Red Hat JBoss Data Grid 6.5.1.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Berindei 2015-06-24 07:09:18 UTC
When the backing store is slow and it cannot write modificationQueueSize entries in shutdownTimeout milliseconds, AsyncCacheWriter can drop updates or issue them in the wrong order.