[
https://issues.apache.org/jira/browse/HDDS-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771140#comment-16771140
]
Hudson commented on HDDS-1106:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15987 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15987/])
HDDS-1106. Introduce queryMap in PipelineManager. Contributed by Lokesh (yqlin:
rev f2fb6536dcbe6320f69273bf9e11d4701248172c)
* (edit)
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/hdds/scm/pipeline/TestPipelineStateManager.java
* (edit)
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/pipeline/PipelineStateMap.java
> Introduce queryMap in PipelineManager
> -------------------------------------
>
> Key: HDDS-1106
> URL: https://issues.apache.org/jira/browse/HDDS-1106
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Fix For: 0.4.0
>
> Attachments: HDDS-1106.001.patch, HDDS-1106.002.patch
>
>
> In Genesis benchmark for block allocation it was found that
> BlockManager#allocateBlock call was very slow for higher number of pipelines.
> This happens because allocateBlock call gets list of pipelines with a
> particular replication type, replication factor and state. This list is
> calculated by traversing the entries of a map. This Jira aims to optimize the
> call by introducing query map in Pipeline Manager.
> The pipeline manager would keep a maintain a list of pipelines for every
> query type i.e. for every replication type, replication factor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
