zhangyubiao created HDFS-7137:
-
Summary: HDFS Federation -- Adding a new Namenode to an existing
HDFS cluster Document Has an Error
Key: HDFS-7137
URL: https://issues.apache.org/jira/browse/HDFS-7137
Pr
Hi,
I am worry about KMS and transparent encryption since there are quite many bugs
discovered after it got merged to branch-2. It gives us an impression that the
feature is not yet well tested. Indeed, transparent encryption is a
complicated feature which changes the core part of HDFS. It i
[
https://issues.apache.org/jira/browse/HDFS-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA resolved HDFS-2247.
-
Resolution: Duplicate
Now "-force" option can be used.
> Provide a "-y" option that skips the conf
This seems like a really aggressive timeframe for a merge. We still
haven't implemented:
* Checksum skipping on read and write from lazy persisted replicas.
* Allowing mmaped reads from the lazy persisted data.
* Any eviction strategy other than LRU.
* Integration with cache pool limits (how do H
+1. This is a very useful feature and the performance number looks
convincing.
Thanks,
-Jing
On Tue, Sep 23, 2014 at 5:12 PM, Xiaoyu Yao wrote:
> +1 non-binding. I’ve reviewed most of the changes in the branch and the
> E2E perf numbers looks good.
>
> Thanks,
> Xiaoyu
>
> On Sep 23, 2014, at 4
+1 non-binding. I’ve reviewed most of the changes in the branch and the E2E
perf numbers looks good.
Thanks,
Xiaoyu
On Sep 23, 2014, at 4:55 PM, Arpit Agarwal wrote:
> I have posted write benchmark results to the Jira.
>
> On Tue, Sep 23, 2014 at 3:41 PM, Arpit Agarwal
> wrote:
>
>> Hi Andr
I am also +1 for the end of next week. YARN-1492 (shared cache) is near the
final stages of the review, and with a little more time it would make it
easier to put it in.
On Tue, Sep 23, 2014 at 4:48 PM, Subramaniam V K wrote:
> +1 for end of next week.
>
> We have got all the patches for YARN-10
I have posted write benchmark results to the Jira.
On Tue, Sep 23, 2014 at 3:41 PM, Arpit Agarwal
wrote:
> Hi Andrew, I said "it is not going to be a substantial fraction of memory
> bandwidth". That is certainly not the same as saying it won't be good or
> there won't be any improvement.
>
> An
+1 for end of next week.
We have got all the patches for YARN-1051 committed to the branch. We are
currently fixing test-patch & plan to call a merge vote soon. Hopefully it
will go through by end of next week.
Thanks,
Subru
On Tue, Sep 23, 2014 at 4:31 PM, Karthik Kambatla
wrote:
> Looking at
Looking at the patches, we might be able to get most of YARN-1492 in by the
end of next week. There would be a couple of security items still
remaining, but we can may be call the feature alpha-ready without them.
On Tue, Sep 23, 2014 at 4:25 PM, Chris Trezzo wrote:
> I would like to see the sha
I think we should delay cutting the branch beyond the end of the week then,
seeing as the HDFS-6581 merge vote (assuming it goes through) doesn't close
until 12am on Tuesday next week. Archival storage is also still finishing
up user APIs and I had a few other q's posted on HDFS-7081, so again migh
I would like to see the shared cache (YARN-1492) make it in as well. We are
going through the final review process (with Karthik and Vinod) and should
be fairly close to complete. This is another feature that has been under
development for a while.
Thanks,
Chris
On Tue, Sep 23, 2014 at 4:00 PM, S
I actually would like to see both archival storage and single replica
memory writes to be in 2.6 release. Archival storage is in the final stages
of getting ready for branch-2 merge as Nicholas has already indicated on
the dev mailing list. Hopefully HDFS-6581 gets ready sooner. Both of these
featu
[
https://issues.apache.org/jira/browse/HDFS-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HDFS-7136.
Resolution: Duplicate
Fix Version/s: HDFS-6534
HDFS-6534 is a better fix. Closing as a
Hi Andrew, I said "it is not going to be a substantial fraction of memory
bandwidth". That is certainly not the same as saying it won't be good or
there won't be any improvement.
Any time you have transfers over RPC or the network stack you will not get
close to the memory bandwidth even for intra
Allen Wittenauer created HDFS-7136:
--
Summary: libhdfs doesn't compile on OS X
Key: HDFS-7136
URL: https://issues.apache.org/jira/browse/HDFS-7136
Project: Hadoop HDFS
Issue Type: Bug
Hey Arun,
Maybe we could do a quick run through of the Roadmap wiki and add/retarget
things accordingly?
I think the KMS and transparent encryption are ready to go. We've got a
very few further bug fixes pending, but that's it.
Two HDFS things that I think probably won't make the end of the week
Looks like most of the content is in and hadoop-2.6 is shaping up nicely.
I'll create branch-2.6 by end of the week and we can go from there to
stabilize it - hopefully in the next few weeks.
Thoughts?
thanks,
Arun
On Tue, Aug 12, 2014 at 1:34 PM, Arun C Murthy wrote:
> Folks,
>
> With hadoo
Sorry, coming to discussion late.
We all agreed that 2.6 would the *last* release supporting JDK6 and
hadoop-2.7 would drop support for JDK6. We could easily do 2.7 right after
2.6 (maybe with few critical bug-fixes) with the defining feature of 2.7
being *JDK7 only*. I've checked with HBase, Pig
Hi Arpit,
Here is the comment. It was certainly not my intention to misquote anyone.
https://issues.apache.org/jira/browse/HDFS-6581?focusedCommentId=14138223&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14138223
Quote:
It would be nice to see that would could g
Andrew, don't misquote me. Can you link the comment where I said
performance wasn't going to be good?
I will add some add some preliminary write results to the Jira later today.
> What's the plan to improve write performance?
I described this in response to your and Colin's comments on the Jira.
Hi Arpit,
On HDFS-6581, I asked for write benchmarks on Sep 19th, and you responded
that the performance wasn't going to be good. However, I thought the
primary goal of this JIRA was to improve write performance, and write
performance is listed as the first feature requirement in the design doc.
+1. I have reviewed most of the code in the branch, and I think its ready
to be merged to trunk.
On Mon, Sep 22, 2014 at 5:24 PM, Arpit Agarwal
wrote:
> HDFS Devs,
>
> We propose merging the HDFS-6581 development branch to trunk.
>
> The work adds support to write to HDFS blocks in memory. The
[
https://issues.apache.org/jira/browse/HDFS-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe resolved HDFS-6957.
Resolution: Duplicate
> Allow DFSClient to manually specify that a request should be
[
https://issues.apache.org/jira/browse/HDFS-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe reopened HDFS-7135:
Not a duplicate.
> Add trace command to FsShell
>
>
>
Masatake Iwasaki created HDFS-7135:
--
Summary: Add trace command to FsShell
Key: HDFS-7135
URL: https://issues.apache.org/jira/browse/HDFS-7135
Project: Hadoop HDFS
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HDFS-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee resolved HDFS-7114.
--
Resolution: Invalid
> Secondary NameNode failed to rollback from 2.4.1 to 2.2.0
> ---
gurmukh singh created HDFS-7134:
---
Summary: Replication count for a block should not update till the
blocks have settled on Datanodes
Key: HDFS-7134
URL: https://issues.apache.org/jira/browse/HDFS-7134
P
28 matches
Mail list logo
