[ 
https://issues.apache.org/jira/browse/HDDS-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Geng updated HDDS-4560:
----------------------------
    Description: 
Add ReadWriteLock into PipelineStateMap to protect contention between 
RaftServer and PipelineManager.

If current SCM step-down while there is some on-going transaction, there might 
be contention that new leader replicate some method(addPipeline/removePipeline) 
to underlying RaftServer, and at the same time PipelineManager is doing some 
getPipeline operations.

  was:
Add ReadWriteLock into PipelineStateMap to protect contention between 
RaftServer and PipelineManager.

If current SCM step-down while there is some on-going transaction, there might 
be contention that new leader replicate some method(addPipeline/removePipeline) 
to underlying RaftServer and PipelineManager is doing some getPipeline 
operations.


> Add ReadWriteLock into PipelineStateMap to protect contention between 
> RaftServer and PipelineManager
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-4560
>                 URL: https://issues.apache.org/jira/browse/HDDS-4560
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: SCM HA
>    Affects Versions: 1.1.0
>            Reporter: Glen Geng
>            Priority: Major
>
> Add ReadWriteLock into PipelineStateMap to protect contention between 
> RaftServer and PipelineManager.
> If current SCM step-down while there is some on-going transaction, there 
> might be contention that new leader replicate some 
> method(addPipeline/removePipeline) to underlying RaftServer, and at the same 
> time PipelineManager is doing some getPipeline operations.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to