+1.
--Anu
On Thu, Sep 24, 2020 at 10:59 PM Elek, Marton wrote:
> Hi all,
>
> Thank you for all the feedback and requests,
>
> As we discussed in the previous thread(s) [1], Ozone is proposed to be a
> separated Apache Top Level Project (TLP)
>
> The proposal with all the details, motivation and
+1
—Anu
> On May 13, 2020, at 12:53 AM, Elek, Marton wrote:
>
>
>
> I would like to start a discussion to make a separate Apache project for Ozone
>
>
>
> ### HISTORY [1]
>
> * Apache Hadoop Ozone development started on a feature branch of Hadoop
> repository (HDFS-7240)
>
> * In the Oc
+1
> On Jan 23, 2020, at 2:51 PM, Jitendra Pandey
> wrote:
>
> +1 for the feature branch.
>
>> On Thu, Jan 23, 2020 at 1:34 PM Wei-Chiu Chuang
>> wrote:
>>
>> Hi we are working on a feature to improve Erasure Coding, and I would like
>> to seek your opinion on creating a feature branch fo
+1, Binding.
Verified the KEYS
Built from sources and ran tests:
- General Ozone command line tests
- Applications like MR and YARN.
--Anu
On Sat, Oct 12, 2019 at 10:25 AM Xiaoyu Yao
wrote:
> +1 binding. Verified
> * Verify the signature.
> * Build from source.
> * Deploy docker compose
+1
—Anu
> On Sep 17, 2019, at 2:49 AM, Elek, Marton wrote:
>
>
>
> TLDR; I propose to move Ozone related code out from Hadoop trunk and store it
> in a separated *Hadoop* git repository apache/hadoop-ozone.git
>
>
>
>
> When Ozone was adopted as a new Hadoop subproject it was proposed[1]
t; >
> >> >> Thanx Vinay for the initiative, Makes sense to add support for
> >> different
> >> >> architectures.
> >> >>
> >> >> +1, for the branch idea.
> >> >> Good Luck!!!
> >> >>
> >> >>
+1, for the branch idea. Just FYI, Your biggest problem is proving that
Hadoop and the downstream projects work correctly after you upgrade core
components like Protobuf.
So while branching and working on a branch is easy, merging back after you
upgrade some of these core components is insanely har
For Ozone, we have started using the Wiki itself as the agenda and after
the meeting is over, we convert it into the meeting notes.
Here is an example, the project owner can edit and maintain it, it is like
10 mins work - and allows anyone to add stuff into the agenda too.
https://cwiki.apache.org
+1 (Binding)
-- Built from sources.
-- Ran smoke tests and verified them.
--Anu
On Sun, May 5, 2019 at 8:05 PM Xiaoyu Yao wrote:
> +1 Binding. Thanks all who contributed to the release.
>
> + Download sources and verify signature.
> + Build from source and ran docker-based ad-hot security tes
+1 (Binding)
-- Verified the checksums.
-- Built from sources.
-- Sniff tested the functionality.
--Anu
On Mon, Apr 15, 2019 at 4:09 PM Ajay Kumar
wrote:
> Hi all,
>
> We have created the second release candidate (RC1) for Apache Hadoop Ozone
> 0.4.0-alpha.
>
> This release contains security
+1
--Anu
On 12/10/18, 6:38 PM, "Vinayakumar B" wrote:
+1
-Vinay
On Mon, 10 Dec 2018, 1:22 pm Elek, Marton
> Thanks Akira,
>
> +1 (non-binding)
>
> I think it's better to do it now at a planned date.
>
> If I understood well the only bigger task
Hi Daryn,
I have just started reading the patch. Hence my apologies if my question has a
response somewhere hidden in the patch.
Are you concerned that FSEditLock is taken in GlobalStateIdContext on Server
side, and worried that a malicious or stupid client would
cause this lock to be held up
+1. (Binding)
Thanks for getting this release done. Verified the signatures and S3 Gateway.
--Anu
On 11/16/18, 5:15 AM, "Shashikant Banerjee" wrote:
+1 (non-binding).
- Verified signatures
- Verified checksums
- Checked LICENSE/NOTICE files
- Built from source
Hi Marton,
+1 (binding)
1. Verified the Signature
2. Verified the Checksums - MD5 and Sha*
3. Build from Sources.
4. Ran all RPC and REST commands against the cluster via Robot.
5. Tested the OzoneFS functionality
Thank you very much for creating the first release of Ozone.
--Anu
On 9/19/18,
I believe that you need to regenerate the site using ‘hugo’ command (hugo is a
site builder). Then commit and push the generated files.
Thanks
Anu
On 9/22/18, 9:56 AM, "俊平堵" wrote:
Martin, thanks for your reply. It works now, but after git changes - I
haven’t seen Apache Hadoop websit
omes from that.
Thanks
Anu
On 8/8/18, 1:19 PM, "Allen Wittenauer" wrote:
> 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
> 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
+1, It will allow many users to get a first look at Ozone/HDDS.
Thanks
Anu
On 8/6/18, 10:34 AM, "Elek, Marton" wrote:
Hi All,
I would like to discuss creating an Alpha release for Ozone. The core
functionality of Ozone is complete but there are two missing features;
Se
July 6, 2018 at 10:59 AM
> To: Vinod Kumar Vavilapalli
> Cc: Anu Engineer , Arpit Agarwal <
> aagar...@hortonworks.com>, "su...@apache.org" , "
> yarn-...@hadoop.apache.org" , "
> hdfs-...@hadoop.apache.org" , &qu
Hi All,
[ Thanks to Arpit for working offline and verifying that branch is indeed good.]
I want to summarize what I know of this issue and also solicit other points of
view.
We reverted the commit(c163d1797) from the branch, as soon as we noticed it.
That is, we have made no other commits afte
I ran “git revert -c c163d1797ade0f47d35b4a44381b8ef1dfec5b60 -m 1”
that will remove all changes from Giovanni’s branch (There are 3 YARN commits).
I am presuming that he can recommit the dropped changes directly into trunk.
I do not know off a better way than to lose changes from his branch. I
Hi Owen,
>> 1. It is hard to tell what has changed. git rebase -i tells me the
>> branch has 722 commits. The rebase failed with a conflict. It would really
>> help if you rebased to current trunk.
Thanks for the comments. I have merged trunk to HDFS-7240 branch.
Hopefully, this makes it
Hi All,
I wanted to bring to your attention that HDFS-12990 has been committed to trunk
and branch 3.0.1.
This change reverts the Namenode RPC port to the familiar 8020, making it same
as Apache Hadoop 2.x series.
In Hadoop 3.0.0 release, the default port is 9820. If you have deployed Hadoop
3
Hi Eddy,
Thanks for driving this release. Just a quick question, do we have time to
close this issue?
https://issues.apache.org/jira/browse/HDFS-12990
or are we abandoning it? I believe that this is the last window for us to fix
this issue.
Should we have a call and get this resolved one way
-1 (binding)
Thank you for all the hard work on 2.9 series. Unfortunately, this is one of
the times I have to -1 this release.
Looks like HADOOP-14840 added a dependency on “oj! Algorithms - version 43.0”,
but we have just added “oj! Algorithms - version 43.0” to the
“LICENSE.txt”. The right a
Hi Steve,
In addition to everything Weiwei mentioned (chapter 3 of user guide), if you
really want to drill down to REST protocol you might want to apply this patch
and build ozone.
https://issues.apache.org/jira/browse/HDFS-12690
This will generate an Open API (https://www.openapis.org , http
Hi Wangda,
We are planning to start the Ozone merge discussion by the end of this month. I
am hopeful that it will be merged pretty soon after that.
Please add Ozone to the list of features that are being tracked for Apache
Hadoop 3.1.
We would love to release Ozone as an alpha feature in Had
Could you please attach the PDFs to the JIRA. I think the mailer is stripping
them off from the mail.
Thanks
Anu
On 9/5/17, 9:44 AM, "Daniel Templeton" wrote:
>Resending with a broader audience, and reattaching the PDFs.
>
>Daniel
>
>On 9/4/17 9:01 AM, Daniel Templeton wrote:
>> All, in pr
Hi Erik,
Looking forward to the release of this tool. Thank you very much for the
contribution.
Had a couple of questions about how the tool works.
1. Would you be able to provide the traces along with this tool? In other
words, would I be able to use this out of the box, or do I have to build
Hi Allen,
https://issues.apache.org/jira/browse/INFRA-13902
That happened with ozone branch too. It was an inadvertent force push. Infra
has advised us to force push the latest branch if you have it.
Thanks
Anu
On 4/17/17, 7:10 AM, "Allen Wittenauer" wrote:
>Looks like someone reset HEAD b
Hi Andrew,
Thank you for all the hard work. I am really excited to see us making progress
towards a 3.0 release.
+1 (Non-Binding)
1. Deployed the downloaded bits on 4 node cluster with 1 Namenode and 3
datanodes.
2. Verified all normal HDFS operations like create directory, create file ,
del
rience.
Thanks
Anu
On 9/9/16, 3:06 PM, "Allen Wittenauer" wrote:
>
>> On Sep 9, 2016, at 2:15 PM, Anu Engineer wrote:
>>
>> +1, Thanks for the effort. It brings in a world of consistency to the hadoop
>> vars; and as usual reading your bash code was very e
+1, Thanks for the effort. It brings in a world of consistency to the hadoop
vars; and as usual reading your bash code was very educative.
I had a minor suggestion though. since we have classified the _OPTS to client
and daemon opts, for new people it is hard to know which of these subcommands
I actively work on two branches (Diskbalancer and ozone) and I agree with most
of what Sangjin said.
There is an overhead in working with branches, there are both technical costs
and administrative issues
which discourages developers from using branches.
I think the biggest issue with branch b
+1 ( Non-binding)
- Downloaded 2.6.1 — created a cluster with namenode and a bunch of data nodes.
- verified that Rolling upgrade and Rollback options work correctly in moving
from 2.61 to 2.6.2
—Anu
On 10/22/15, 2:14 PM, "sjl...@gmail.com on behalf of Sangjin Lee"
wrote:
>Hi all,
>
>I ha
35 matches
Mail list logo
