Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1059814

Summary: L1WriteSynchronizer can cause thread to hang
Product: [JBoss] JBoss Data Grid 6 Reporter: William Burns <wburns>
Component: InfinispanAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED UPSTREAM QA Contact: Martin Gencur <mgencur>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: jdg-bugs, vjuranek
Target Milestone: CR1   
Target Release: 6.2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:35:00 UTC 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 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

Comment 4 Red Hat Bugzilla 2025-02-10 03:35:00 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.