[ 
https://issues.apache.org/jira/browse/HDDS-2034?focusedWorklogId=316443&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-316443
 ]

ASF GitHub Bot logged work on HDDS-2034:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Sep/19 07:03
            Start Date: 23/Sep/19 07:03
    Worklog Time Spent: 10m 
      Work Description: ChenSammi commented on pull request #1469: HDDS-2034. 
Async RATIS pipeline creation and destroy through heartbea…
URL: https://github.com/apache/hadoop/pull/1469#discussion_r326968982
 
 

 ##########
 File path: hadoop-hdds/common/src/main/resources/ozone-default.xml
 ##########
 @@ -1388,6 +1379,25 @@
     </description>
   </property>
 
+  <property>
+    <name>hdds.scm.safemode.pipeline.creation</name>
+    <value>true</value>
+    <tag>HDDS,SCM,OPERATION</tag>
+    <description>
+      Boolean value to enable background pipeline creation in SCM safe mode.
+    </description>
+  </property>
+
+  <property>
+    <name>hdds.scm.safemode.min.pipeline</name>
 
 Review comment:
   When a new cluster startup, it will exit safemode immediately currently.  
Because there is pipeline to  wait for it's report from datanode.   So if we 
don't add a min pipeline threshold, we will exit safemode without any pipeline 
ready to use.  
   The desired state is when safenode off, Ozone should be ready for read/write 
object. 
   Thant's the reason this property is added.  
HDDS_SCM_SAFEMODE_HEALTHY_PIPELINE_THRESHOLD_PCT_DEFAULT cannot fulfill this 
purpose, because the total pipeline number at the start of a new cluster is 0. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 316443)
    Time Spent: 3h 10m  (was: 3h)

> Async RATIS pipeline creation and destroy through heartbeat commands
> --------------------------------------------------------------------
>
>                 Key: HDDS-2034
>                 URL: https://issues.apache.org/jira/browse/HDDS-2034
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Sammi Chen
>            Assignee: Sammi Chen
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Currently, pipeline creation and destroy are synchronous operations. SCM 
> directly connect to each datanode of the pipeline through gRPC channel to 
> create the pipeline to destroy the pipeline.  
> This task is to remove the gRPC channel, send pipeline creation and destroy 
> action through heartbeat command to each datanode.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to