hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Junping Du <...@hortonworks.com>
Subject Re:
Date Tue, 21 Nov 2017 21:11:43 GMT
Just filed HADOOP-15059 to track this.


Thanks,


Junping


________________________________
From: Junping Du
Sent: Tuesday, November 21, 2017 1:09 PM
To: Vinod Kumar Vavilapalli; Allen Wittenauer
Cc: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Another issue I just found is we have token format compatibility issue between 2.x and 3.0.
I tried to run a simple MR job on 3.0 RC0 against with 2.9.0 tarball which is failed. This
incompatibility change should also break other applications which will break rolling upgrade.
I think it is another blocker for 3.0.0 release.

Thanks,

Junping
________________________________________
From: Vinod Kumar Vavilapalli <vinodkv@apache.org>
Sent: Tuesday, November 21, 2017 12:59 PM
To: Allen Wittenauer
Cc: common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org;
hdfs-dev@hadoop.apache.org
Subject: Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

>>> - Cannot enable new UI in YARN because it is under a non-default
>>> compilation flag. It should be on by default.
>>>
>>
>> The yarn-ui profile has always been off by default, AFAIK. It's documented
>> to turn it on in BUILDING.txt for release builds, and we do it in
>> create-release.
>>
>> IMO not a blocker. I think it's also more of a dev question (do we want to
>> do this on every YARN build?) than a release one.
>
>       -1 on making yarn-ui always build.
>
>       For what is effectively an optional component (the old UI is still there), it's
heavy dependency requirements make it a special burden outside of the Docker container.


Thanks for the background on this.

I got schooled offline too about the heaviness of the dependencies.


> If it can be changed such that it either always downloads the necessary bits (regardless
of the OS/chipset!) and/or doesn't kill the maven build if those bits can't be found  (i.e.,
truly optional), then I'd be less opposed.  (and, actually, quite pleased because then the
docker image build would be significantly faster.)


This is a good idea (to the extend I understand your proposal). Long term, we'd like YARN
UI2 to replace current UI, so it shouldn't be optionally build and hence the build should
be fast. Let me track this separately as a non-blocker.

Thanks
+Vinod
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message