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

Prashant Pogde updated HDDS-897:
--------------------------------
    Target Version/s: 1.2.0

I am managing the 1.1.0 release and we currently have more than 600 issues 
targeted for 1.1.0. I am moving the target field to 1.2.0. 

If you are actively working on this jira and believe this should be targeted to 
1.1.0 release, Please change the target field back to 1.1.0 before Feb 05, 
2021. 

> all healthy datanodes are not involved in pipeline allocation
> -------------------------------------------------------------
>
>                 Key: HDDS-897
>                 URL: https://issues.apache.org/jira/browse/HDDS-897
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode, SCM
>            Reporter: Nilotpal Nandi
>            Priority: Major
>         Attachments: active_datanode1.png, active_datanode2.png, 
> all-node-ozone-logs-1543837271.tar.gz
>
>
> Please find the attached screenshot. There are 6 active datanodes , but there 
> is only 1 pipeline created. All new writes are now done on a single pipeline 
> even when there are 3  more free and active datanodes.
> !active_datanode2.png!
> !active_datanode1.png!
>  
> {noformat}
> [root@ctr-e139-1542663976389-11261-01-000007 meta]# ozone scmcli listPipelines
> Pipeline[ Id: 202f7208-6977-4f65-b070-c1e7e57cb2ed, Nodes: 
> 06e074f7-67b4-4dde-8f20-a437ca60b7a1{ip: 172.27.20.97, host: 
> ctr-e139-1542663976389-11261-01-000007.hwx.site}c5bf9a9f-d471-4cef-aae4-61cb387ea9e3{ip:
>  172.27.79.145, host: 
> ctr-e139-1542663976389-11261-01-000006.hwx.site}96c18fe3-5520-4941-844b-ff7186a146a6{ip:
>  172.27.55.132, host: ctr-e139-1542663976389-11261-01-000003.hwx.site}, 
> Type:RATIS, Factor:THREE, State:ALLOCATED]{noformat}
>  



--
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