Includes these additional votings we got 5 binding votings, and 12
non-binding votings, we have many others like Bibin/Akhil gave offline
suggestions and testing results. Thanks everyone for your help!
I've done most of staging/pushing works for the 3.1.1 release. Given Apache
mirrors will take so
For more details, see https://builds.apache.org/job/hadoop-trunk-win/552/
[Aug 7, 2018 5:15:28 PM] (virajith) HDFS-13796. Allow verbosity of
InMemoryLevelDBAliasMapServer to be
[Aug 7, 2018 7:36:55 PM] (wangda) YARN-8629. Container cleanup fails while
trying to delete Cgroups. (Suma
[Aug 7, 2018
Thanks for reporting this issue. I have filed a JIRA to address this issue.
https://issues.apache.org/jira/browse/HDDS-341
>So, consider this as a report. IMHO, cutting an Ozone release prior to a
>Hadoop release ill-advised given the distribution impact and the requirements
>of the merge vote.
> On Aug 8, 2018, at 12:56 PM, Anu Engineer wrote:
>
>> Has anyone verified that a Hadoop release doesn't have _any_ of the extra
>> ozone bits that are sprinkled outside the maven modules?
> As far as I know that is the state, we have had multiple Hadoop releases
> after ozone has been merg
> Given that there are some Ozone components spread out past the core maven
> modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more
> work going to go into segregating the Ozone components prior to release?
The official release will be a source tarball, we intend to release a
Given that there are some Ozone components spread out past the core maven
modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more work
going to go into segregating the Ozone components prior to release? Has anyone
verified that a Hadoop release doesn't have _any_ of the extr
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/862/
[Aug 7, 2018 9:33:14 AM] (msingh) HDDS-230. ContainerStateMachine should
implement readStateMachineData
[Aug 7, 2018 10:39:53 AM] (msingh) HDDS-301. ozone command shell does not
contain subcommand to run o
