On Mon, Jan 8, 2018 at 11:28 PM, Aaron T. Myers wrote:
> Thanks a lot for the response, Larry. Comments inline.
>
> On Mon, Jan 8, 2018 at 6:44 PM, larry mccay wrote:
>
>> Question...
>>
>> Can this be addressed in some way during or before upgrade that allows it
>> to only affect new installs?
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/651/
[Jan 8, 2018 9:20:17 PM] (billie) YARN-7704. Document improvement for registry
dns. Contributed by Jian He
[Jan 8, 2018 10:25:39 PM] (weiy) HDFS-12945. Switch to ClientProtocol instead
of NamenodeProtocols
Is this for the confluence wiki at
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Home
On 4 Jan 2018, at 20:25, Ajay Kumar
mailto:ajay.ku...@hortonworks.com>> wrote:
Hi,
Can someone please help me get wiki access?
For one of the jira (HADOOP-14969) I want to add some information a
Granted Ajay write access to the confluence wiki.
On 1/9/18, 10:38 AM, "Steve Loughran" wrote:
Is this for the confluence wiki at
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+Home
On 4 Jan 2018, at 20:25, Ajay Kumar
mailto:ajay.ku...@hortonworks.com>> wrote
Hi, All
We have released Apache Hadoop 3.0.0 in December [1]. To further
improve the quality of release, we plan to cut branch-3.0.1 branch
tomorrow for the preparation of Apache Hadoop 3.0.1 release. The focus
of 3.0.1 will be fixing blockers (3), critical bugs (1) and bug fixes
[2]. No new feat
Particularly since 9820 isn't in the contiguous range of ports in
HDFS-9427, is there any value in this change?
Let's change it back to prevent the disruption to users, but
downstream projects should treat this as a bug in their tests. Please
open JIRAs in affected projects. -C
On Tue, Jan 9, 20
Hi Eddy, thanks for taking this on,
Historically we've waited for the first RC to cut the release branch since
it keeps things simpler for committers.
Also, could you check the permissions on your JIRA filter? It shows as
private for me.
Best,
Andrew
On Tue, Jan 9, 2018 at 11:17 AM, Lei Xu wro
Is it necessary to cut the branch so far ahead of the release? branch-3.0
is already a maintenance line for 3.0.x releases. Is there a known
feature/improvement planned to go into branch-3.0 that is not desirable for
the 3.0.1 release?
I have found in the past that branching so early leads to ma
Hi, Andrew and Jason
Thanks for the feedback!
I will follow the pattern and cut the branch on Feb 1st and start the
RC vote around Feb 5th then.
Best
On Tue, Jan 9, 2018 at 11:35 AM, Jason Lowe wrote:
> Is it necessary to cut the branch so far ahead of the release? branch-3.0
> is already a m
Hi, Andrew and Jason
Thanks for the feedback!
I will follow the pattern and cut the branch on Feb 1st and start the
RC vote around Feb 5th then.
Best
On Tue, Jan 9, 2018 at 11:35 AM, Jason Lowe wrote:
> Is it necessary to cut the branch so far ahead of the release? branch-3.0
> is already a m
While I agree the original port change was unnecessary, I don’t think Hadoop NN
port change is a bad thing.
I worked for a Hadoop distro that NN RPC port was default to port 9000. When
we migrate from BigInsights to IOP and now to HDP, we have to move customer
Hive metadata to new NN RPC port.
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/652/
[Jan 9, 2018 11:09:33 AM] (sunilg) YARN-7718. DistributedShell failed to
specify resource other than
[Jan 9, 2018 12:27:01 PM] (bibinchundatt) YARN-7508. NPE in FiCaSchedulerApp
when debug log enabled in
[
On Tue, Jan 9, 2018 at 3:15 PM, Eric Yang wrote:
> While I agree the original port change was unnecessary, I don’t think
> Hadoop NN port change is a bad thing.
>
> I worked for a Hadoop distro that NN RPC port was default to port 9000.
> When we migrate from BigInsights to IOP and now to HDP, we
13 matches
Mail list logo