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

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

                Author: ASF GitHub Bot
            Created on: 13/Oct/19 07:33
            Start Date: 13/Oct/19 07:33
    Worklog Time Spent: 10m 
      Work Description: elek commented on issue #1610: HDDS-1868. Ozone 
pipelines should be marked as ready only after the leader election is complete.
URL: https://github.com/apache/hadoop/pull/1610#issuecomment-541394654
 
 
   
   Thank you very much to open this pull request.
   
   During the weekend the Ozone source code has been moved out from 
[apache/hadoop](https://github.com/apache/hadoop) repository to 
[apache/hadoop-ozone](https://github.com/apache/hadoop-ozone) repository.
   
   This git commits are rewritten, but the branch of this pull request is also 
transformed (state of Saturday morning), you can use the new, migrated branch 
to recreate this pull request.
   
   Your pull request is important for us: **Can you please re-create your pull 
request in the new repository?**
   
   **1**. Create a new fork of https://github.com/apache/hadoop-ozone
   
   **2**. Clone it and have both your fork and the apache repo as remotes:
   
   ```
   git clone g...@github.com:swagle/hadoop-ozone.git
   cd hadoop-ozone
   git remote add apache g...@github.com:apache/hadoop-ozone.git
   git fetch apache
   ```
   
   **3**. Fetch your migrated branch and push it to your fork.
   
   ```
   git checkout -b HDDS-1868 apache/HDDS-1868
   git push origin HDDS-1868
   ```
   
   **4**. And create the new pull request on the new repository.
   
   
https://github.com/apache/hadoop-ozone/compare/master...swagle:HDDS-1868?expand=1
   
   If you need more information, please check 
[this](https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Ozone+source+tree+split)
 wiki page or contact with me (my github user name + apache.org).
   
   Thank you, and sorry for the inconvenience.
 
----------------------------------------------------------------
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: 327451)
    Time Spent: 3h  (was: 2h 50m)

> Ozone pipelines should be marked as ready only after the leader election is 
> complete
> ------------------------------------------------------------------------------------
>
>                 Key: HDDS-1868
>                 URL: https://issues.apache.org/jira/browse/HDDS-1868
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode, SCM
>    Affects Versions: 0.4.0
>            Reporter: Mukul Kumar Singh
>            Assignee: Siddharth Wagle
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>         Attachments: HDDS-1868.01.patch, HDDS-1868.02.patch, 
> HDDS-1868.03.patch, HDDS-1868.04.patch, HDDS-1868.05.patch, HDDS-1868.06.patch
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> Ozone pipeline on create and restart, start in allocated state. They are 
> moved into open state after all the pipeline have reported to it. However, 
> this potentially can lead into an issue where the pipeline is still not ready 
> to accept any incoming IO operations.
> The pipelines should be marked as ready only after the leader election is 
> complete and leader is ready to accept incoming IO.



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