[ 
https://issues.apache.org/jira/browse/HDFS-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141474#comment-14141474
 ] 

Colin Patrick McCabe commented on HDFS-6581:
--------------------------------------------

bq. HDFS-4953 is not a subtask of HDFS-4949, and you yourself have said that it 
is an independent change. Also no numbers were cited or provided as evidence 
when calling the merge vote for HDFS-4949 so I don't think the community could 
reasonably be expected to take that into consideration.

When HDFS-4953 was created, it was a subtask of HDFS-4949.  It was moved out 
because people wanted to be able to take advantage of it more quickly and it 
was a valuable improvement even without HDFS-4949.

I don't think creating a usable eviction strategy is that hard.  I can help 
with it, but probably not for a few days.

The move from subversion to git has reduced a lot of the pain of maintaining a 
branch.  You just periodically do a "git rebase \-i trunk" and you're good to 
go.  This is once of the biggest advantages of moving to git and if you haven't 
tried rebase \-i, you should!

Can you give a summary of which tasks you are planning on completing prior to 
the merge and which after?

> Write to single replica in memory
> ---------------------------------
>
>                 Key: HDFS-6581
>                 URL: https://issues.apache.org/jira/browse/HDFS-6581
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-6581.merge.01.patch, HDFS-6581.merge.02.patch, 
> HDFS-6581.merge.03.patch, HDFS-6581.merge.04.patch, HDFS-6581.merge.05.patch, 
> HDFS-6581.merge.06.patch, HDFS-6581.merge.07.patch, 
> HDFSWriteableReplicasInMemory.pdf, Test-Plan-for-HDFS-6581-Memory-Storage.pdf
>
>
> Per discussion with the community on HDFS-5851, we will implement writing to 
> a single replica in DN memory via DataTransferProtocol.
> This avoids some of the issues with short-circuit writes, which we can 
> revisit at a later time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to