Bug 987520 - Putting entries with memcached is ignoring the queue-flush-interval parameter
Putting entries with memcached is ignoring the queue-flush-interval parameter
Status: ASSIGNED
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity medium
: CR1
: 6.2.0
Assigned To: Tristan Tarrant
Martin Gencur
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-23 10:49 EDT by Jakub Markos
Modified: 2016-03-23 10:17 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
The queue-flush-interval and queue-size attributes of a replicated cache are ignored when data is stored remotely from Memcached client. This is caused by the "distribution-based replication" algorithm in JBoss Data Grid: a key's primary owner might not be the local node, so a synchronous put operation is sent to the key owner, thus overriding the async queue. </para> <para> Consequently, data is replicated immediately and the queue-flush-interval and queue-size attributes are not respected.
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: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker ISPN-3293 Major Resolved Putting entries with memcached is ignoring the queue-flush-interval parameter 2016-05-03 03:57 EDT

  None (edit)
Description Jakub Markos 2013-07-23 10:49:36 EDT
Please see the linked JIRA for more information.
Comment 2 JBoss JIRA Server 2013-07-26 07:42:54 EDT
Tristan Tarrant <ttarrant@redhat.com> made a comment on jira ISPN-3293

Nothing do to with the issue itself, but

assertTrue(null == mc2.get("key1"));

should be

assertNull(mc2.get("key1"));
Comment 3 JBoss JIRA Server 2013-07-26 07:47:09 EDT
Tristan Tarrant <ttarrant@redhat.com> made a comment on jira ISPN-3293

Which version did this happen on ?
Comment 4 JBoss JIRA Server 2013-07-26 08:42:38 EDT
Tristan Tarrant <ttarrant@redhat.com> made a comment on jira ISPN-3293

This issue is caused by the new "distribution-based replication" algorithm in Infinispan: a key's primary owner might not be the local node, so a synchronous put operation is sent to the key owner, thus overriding the async queue. The fact that the test works for HotRod is probably because the encoding of the key differs. The actual solution to this problem will be solved by ISPN-3371
Comment 5 JBoss JIRA Server 2016-03-23 10:17:04 EDT
Dan Berindei <dberinde@redhat.com> updated the status of jira ISPN-3293 to Resolved

Note You need to log in before you can comment on or make changes to this bug.