I just committed YARN-8768 to trunk. Thanks for the report and quick fix.
Thanks,
-Shane
On Wed, Sep 12, 2018 at 2:28 PM Naganarasimha Garla <
naganarasimha...@apache.org> wrote:
> Thanks for reporting Sean and Sunil for acting on it. My bad i had used
> alias to compile which was skipping the j
Thanks for reporting Sean and Sunil for acting on it. My bad i had used
alias to compile which was skipping the javadoc !
Will try to commit as soon as the jenkins results are out.
On Thu, Sep 13, 2018 at 1:18 AM Sunil G wrote:
> Thanks Sean
>
> YARN-8768 is raised and we will get this in very s
Thanks Sean
YARN-8768 is raised and we will get this in very soon.
- Sunil
On Wed, Sep 12, 2018 at 9:16 PM Sean Mackrory wrote:
> `mvn install` fails on trunk right now due to javadoc error in yarn-api. Is
> that related? If so, can we revert or fix ASAP please?
>
> On Wed, Sep 12, 2018 at 6:0
`mvn install` fails on trunk right now due to javadoc error in yarn-api. Is
that related? If so, can we revert or fix ASAP please?
On Wed, Sep 12, 2018 at 6:05 AM Naganarasimha Garla <
naganarasimha...@apache.org> wrote:
> Hi All,
> Me and Sunil have successfully merged YARN-3409 to the
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/894/
[Sep 11, 2018 4:42:34 AM] (brahma) HDFS-13237. [Documentation] RBF: Mount
points across multiple
[Sep 11, 2018 5:34:23 AM] (xiao) HDFS-13051. Fix dead lock during async editlog
rolling if edit queue is
[Se
+1 (binding)
- Built from source
- Brought up a single node cluster
- Checked basic HDFS functions and checked the UIs
- Ran several simple jobs.
On Mon, Sep 10, 2018 at 7:01 AM 俊平堵 wrote:
> Hi all,
>
> I've created the first release candidate (RC0) for Apache
> Hadoop 2.8.5. This is our
Hi All,
Me and Sunil have successfully merged YARN-3409 to the trunk and
we have created new umbrella jira YARN-8766 to track the pending jiras and
the remaining planned improvement features.
Thanks all for the support !
Regards,
+ Naga
On Wed, Sep 12, 2018 at 7:46 AM Naganarasimha Garl
Hi All,
Inline with the original 3.2 communication proposal dated 17th July 2018, I
would like to provide more updates.
We are approaching previously proposed code freeze date (September 14,
2018). So I would like to cut 3.2 branch on 17th Sept and point existing
trunk to 3.3 if there are no issu
