Bug 1059814 - L1WriteSynchronizer can cause thread to hang
Summary: L1WriteSynchronizer can cause thread to hang
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: 6.2.1
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-30 17:55 UTC by William Burns
Modified: 2022-03-03 09:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
L1 cache in distributed mode with concurrent gets originating from the same node for the same key can result in one being stuck if there is no value found. This can cause massive degradation of performance as the request would never complete.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3956 0 Major Resolved L1WriteSynchronizer can cause locking with concurrent gets when value is not present 2015-09-10 13:30:51 UTC

Description William Burns 2014-01-30 17:55:48 UTC 
Description of problem: L1 with concurrent gets originating from the same node for the same key can result in 1 being stuck if there is no value found.  This can cause massive degradation of performance as the request would never complete.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Dan Berindei 2014-01-31 08:05:46 UTC 
Pull request integrated: https://github.com/infinispan/jdg/pull/18
Note You need to log in before you can comment on or make changes to this bug.