Commit 5f48e23
Suranjan Kumar
Instead of sync on PersistentMemberManager using CopyOnWrite structure
There was a deadlock with revoke and unblock where revoke was taking
lock on PersistentMemberManager and then requires lock on PersistenceAdvisorImpl.
The intialization thread takes lock PersistenceAdvisorImpl and then to check
whether the diskid is unblocked and requires lock on PersistentmemberManager1 parent bf2d978 commit 5f48e23
1 file changed
Lines changed: 3 additions & 2 deletions
File tree
- gemfire-core/src/main/java/com/gemstone/gemfire/internal/cache/persistence
Lines changed: 3 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
| 33 | + | |
33 | 34 | | |
34 | 35 | | |
35 | 36 | | |
| |||
47 | 48 | | |
48 | 49 | | |
49 | 50 | | |
50 | | - | |
| 51 | + | |
51 | 52 | | |
52 | 53 | | |
53 | 54 | | |
| |||
69 | 70 | | |
70 | 71 | | |
71 | 72 | | |
72 | | - | |
| 73 | + | |
73 | 74 | | |
74 | 75 | | |
75 | 76 | | |
| |||
0 commit comments