[
https://issues.apache.org/jira/browse/HDDS-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar updated HDDS-981:
-----------------------------
Resolution: Fixed
Fix Version/s: 0.4.0
Status: Resolved (was: Patch Available)
Thanks [~ljain] for the contribution. Thanks to [~shashikant], [~anu] and
[~msingh] for the review. Committed this to trunk.
> Block allocation should involve pipeline selection and then container
> selection
> -------------------------------------------------------------------------------
>
> Key: HDDS-981
> URL: https://issues.apache.org/jira/browse/HDDS-981
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Fix For: 0.4.0
>
> Attachments: HDDS-981.001.patch, HDDS-981.002.patch,
> HDDS-981.003.patch, HDDS-981.004.patch, HDDS-981.005.patch,
> HDDS-981.006.patch, HDDS-981.007.patch, HDDS-981.008.patch
>
>
> Currently SCM maintains a list of preallocated containers and allocates
> blocks from these containers. This approach does not work well with dynamics
> of the cluster where new nodes are being added and pipelines are destroyed.
> New containers are not created until all the preallocated containers are
> exhausted.
> The Jira aims to establish a criteria in block allocation where first a
> pipeline is selected amongst the available pipelines and then a container is
> selected in that pipeline. In order to handle the dynamics of the cluster a
> fixed interval pipeline creator job can be launched which creates pipelines
> in the system.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
