+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
— Anu
> On Dec 6, 2019, at 5:26 PM, Dinesh Chitlangia wrote:
>
> All,
> Since the Apache Hadoop Ozone 0.4.1 release, we have had significant
> bug fixes towards performance & stability.
>
> With that in mind, 0.4.2 release would be good to consolidate all those fixes.
>
> Pls share your t
@Vinod Kumar Vavilapalli
Do we need a separate vote thread for this? there are already JIRAs in
place for ozone code removal and I gather it is same for Submarine.
Would it be possible to treat this thread as consensus and act upon the
JIRA itself?
Thanks
Anu
On Sun, Oct 27, 2019 at 6:58 PM 俊
+1 for Ozone. We are in our own repo now. It would be good to remove this
code from Hadoop, otherwise it will confuse new contributors.
I would like to add a git tag tro Hadoop, so that people have the ability
to sync back and see the code evolution.
--Anu
On Thu, Oct 24, 2019 at 4:03 PM Giovanni
+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
Is it possible to unprotect the branches and not the trunk? Generally, a
force push to trunk indicates a mistake and we have had that in the past.
This is just a suggestion, even if this request is not met, I am still +1.
Thanks
Anu
On Tue, May 14, 2019 at 4:58 AM Takanobu Asanuma
wrote:
> +
+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
[
https://issues.apache.org/jira/browse/HADOOP-16026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer resolved HADOOP-16026.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.3.0
+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, on AssertJ usage, thanks for getting this done.
--Anu
On 3/31/19, 9:37 PM, "Akira Ajisaka" wrote:
Hi folks,
Now I'm going to upgrade the JUnit version from 4 to 5 for Java 11 support.
I wanted to start with the small module, so I uploaded a patch to upgrade
the API in h
Anu Engineer created HADOOP-16215:
-
Summary: Genconfig does not generate LOG4j configs
Key: HADOOP-16215
URL: https://issues.apache.org/jira/browse/HADOOP-16215
Project: Hadoop Common
Issue
Konstantin,
Just a nitpicky thought, if we move this branch to Java-8 on Jenkins, but still
hope to release code that can run on Java 7, how will we detect
Java 8 only changes? I am asking because till now whenever I checked in Java 8
features in branch-2 Jenkins would catch that issue.
With t
+1
--Anu
On 2/1/19, 3:02 PM, "Jonathan Hung" wrote:
+1. Thanks Wangda.
Jonathan Hung
On Fri, Feb 1, 2019 at 2:25 PM Dinesh Chitlangia <
dchitlan...@hortonworks.com> wrote:
> +1 (non binding), thanks Wangda for organizing this.
>
> Regards,
> D
>> I propose to adopt Ozone model: which is the same master branch, different
>> release cycle, and different release branch. It is a great example to show
>> agile release we can do (2 Ozone releases after Oct 2018) with less
>> overhead to setup CI, projects, etc.
I second this, especially this
Marton please correct me I am wrong, but I believe that without this branch it
is hard for us to push to Apache DockerHub. This allows for Apache account
integration and dockerHub.
Does YARN publish to the Docker Hub via Apache account?
Thanks
Anu
On 1/29/19, 4:54 PM, "Eric Yang" wrote:
With twelve +1 votes (9 Binding and 3 Non-Binding) and no -1 or 0, this
vote passes. Thank you all for voting. We will merge HDDS-4 branch to Ozone
soon.
Thanks
Anu
On Fri, Jan 11, 2019 at 7:40 AM Anu Engineer wrote:
> Since I have not heard any concerns, I will start a VOTE thread
+1, (Binding)
Deployed a pseudo-distributed cluster.
Tried out HDFS commands and verified everything works.
--Anu
On 1/14/19, 11:26 AM, "Virajith Jalaparti" wrote:
Thanks Sunil and others who have worked on the making this release happen!
+1 (non-binding)
- Built
Since I have not heard any concerns, I will start a VOTE thread now.
This vote will run for 7 days and will end on Jan/18/2019 @ 8:00 AM PST.
I will start with my vote, +1 (Binding)
Thanks
Anu
-- Forwarded message -
From: Anu Engineer
Date: Mon, Jan 7, 2019 at 5:10 PM
Subject
Hi All,
I would like to propose a merge of HDDS-4 branch to the Hadoop trunk.
HDDS-4 branch implements the security work for HDDS and Ozone.
HDDS-4 branch contains the following features:
- Hadoop Kerberos and Tokens support
- A Certificate infrastructure used by Ozone and HDDS.
- Aud
[
https://issues.apache.org/jira/browse/HADOOP-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer resolved HADOOP-16012.
---
Resolution: Fixed
> Typo in daemonlog d
Anu Engineer created HADOOP-16012:
-
Summary: Typo in daemonlog docs
Key: HADOOP-16012
URL: https://issues.apache.org/jira/browse/HADOOP-16012
Project: Hadoop Common
Issue Type: Bug
+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
Just reverted, Thanks for root causing this.
Thanks
Anu
On 8/15/18, 9:37 AM, "Allen Wittenauer"
wrote:
> On Aug 15, 2018, at 4:49 AM, Kitti Nánási
wrote:
>
> Hi All,
>
> We noticed that the checkstyle run by the pre commit job started to show
> false positive
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
+1, on the Non-Routable Idea. We like it so much that we added it to the Ozone
roadmap.
https://issues.apache.org/jira/browse/HDDS-231
If there is consensus on bringing this to Hadoop in general, we can build this
feature in common.
--Anu
On 7/5/18, 1:09 PM, "Sean Busbey" wrote:
I reall
Based on conversations with Giovanni and Subru, I have pushed a revert for this
merge.
Thanks
Anu
On 7/5/18, 12:55 PM, "Giovanni Matteo Fumarola"
wrote:
+ common-dev and hdfs-dev as fyi.
Thanks Subru and Sean for the answer.
On Thu, Jul 5, 2018 at 12:14 PM, Subru Krishn
+1, I have code reviewed many of these changes and it is an essential set of
changes for HDDS/Ozone.
Thank you for getting this done.
Thanks
Anu
On 6/29/18, 3:14 PM, "Bharat Viswanadham" wrote:
Fixing subject line of the mail.
Thanks,
Bharat
On 6/29/18
Hi Owen,
Thanks for the proposal. I was hoping for same releases, but I am okay with
different releases as well.
@Konstantin, I am completely open to the name changes, let us discuss that
in HDFS-10419
and we can make the corresponding change.
--Anu
On 3/19/18, 10:52 AM, "Owen O'Mal
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
Anu Engineer created HADOOP-15204:
-
Summary: Add Configuration API for parsing storage sizes
Key: HADOOP-15204
URL: https://issues.apache.org/jira/browse/HADOOP-15204
Project: Hadoop Common
Anu Engineer created HADOOP-15128:
-
Summary: TestViewFileSystem tests are broken in trunk
Key: HADOOP-15128
URL: https://issues.apache.org/jira/browse/HADOOP-15128
Project: Hadoop Common
-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
Can I please get access too, Confluence user name : anu
Thanks
Anu
On 9/11/17, 4:08 PM, "Arun Suresh" wrote:
>I've added Subru and Chris.
>
>@Vrushali, I could not find your username. I think you need to sign up to
>confluence first with your apache id.
>
>Cheers
>-Arun
>
>
>
>On Mon, Sep 1
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
Agreed, but I was under the impression that we would kill the container under
OOM conditions and not the whole base machine.
Thanks
Anu
On 3/8/17, 2:41 PM, "Allen Wittenauer" wrote:
>
>> On Mar 8, 2017, at 2:21 PM, Anu Engineer wrote:
>>
>> Hi Allen,
>&
Hi Allen,
> Likely something in the HDFS-7240 branch or with this patch that's
> doing Bad Things (tm).
Thanks for bringing this to my attention, But I am surprised that a mvn command
is able to kill a test machine.
I have pasted the call stack from the issue that you pointed out to be th
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
[
https://issues.apache.org/jira/browse/HADOOP-13935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer resolved HADOOP-13935.
---
Resolution: Implemented
This feature is already implemented via envvars command, which is
Anu Engineer created HADOOP-13935:
-
Summary: A command to print JAVA_VERSION used by Hadoop/HDFS
Key: HADOOP-13935
URL: https://issues.apache.org/jira/browse/HADOOP-13935
Project: Hadoop Common
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
Anu Engineer created HADOOP-13352:
-
Summary: Make X-FRAME-OPTIONS configurable in HttpServer2
Key: HADOOP-13352
URL: https://issues.apache.org/jira/browse/HADOOP-13352
Project: Hadoop Common
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
.
Thanks
Anu
On 6/8/16, 9:58 AM, "Allen Wittenauer"
wrote:
>
> You guys know that the build machines in the Yahoo data center
> temporarily lose network all the time, right? It's been happening for months
> now...
>
>
>
>> On Jun 8, 2016, at 9:
Another instance of the same failure.
https://builds.apache.org/job/PreCommit-HADOOP-Build/9690/console
I am going to open a JIRA so that we can track this issue there. This is on H1
so I don’t think it is machine specific.
Thanks
Anu
On 6/7/16, 5:30 PM, "Anu Engineer" wrote:
Hi Chris,
Thanks for bringing this up. I just ran into the same issue.
https://builds.apache.org/job/PreCommit-HDFS-Build/15700/console
But in my case it seems like a different host. “Building remotely on H0”.
Thanks
Anu
On 6/6/16, 3:44 PM, "Chris Nauroth" wrote:
>I'm curious if anyone has
Hi Vikram,
Welcome. Following query looks for JIRAs with newbie tag. They are usually
easier JIRAs to look at and understand.
The following query restricts the search to HDFS, YARN, HADOOP COMMON and
HBASE. Feel free to look at other sub-projects too if you like.
https://issues.apache.org/jira/
Anu Engineer created HADOOP-13102:
-
Summary: Update GroupsMapping documentation to reflect the new
changes
Key: HADOOP-13102
URL: https://issues.apache.org/jira/browse/HADOOP-13102
Project: Hadoop
An overview of HDFS is here in this paper —
http://pages.cs.wisc.edu/~akella/CS838/F15/838-CloudPapers/hdfs.pdf , a bit
dated but still the best reference to HDFS.
If you looking for a book that covers the breadth of Hadoop eco-system, I would
recommend Hadoop: The Definitive Guide by White.
Hi Luis,
Welcome to Hadoop. We have a very nascent process for forking and for pull
requests using Github. It is still evolving and the process is slightly
different from standard github flow.
The easiest way to contribute your work is to follow the process outlined in
this document.
https:/
I ran into the same issue and filed an INFRA jira too.
https://issues.apache.org/jira/browse/INFRA-10720
So +1 for having the git control back
Thanks
Anu
On 11/10/15, 2:45 PM, "Steve Loughran" wrote:
>
>> On 10 Nov 2015, at 22:07, Karthik Kambatla wrote:
>>
>> Hi folks,
>>
>> Recent
+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
Anu Engineer created HADOOP-12325:
-
Summary: RPC Metrics : Add the ability track and log slow RPCs
Key: HADOOP-12325
URL: https://issues.apache.org/jira/browse/HADOOP-12325
Project: Hadoop Common
Anu Engineer created HADOOP-12322:
-
Summary: typos in rpcmetrics.java
Key: HADOOP-12322
URL: https://issues.apache.org/jira/browse/HADOOP-12322
Project: Hadoop Common
Issue Type: Bug
Anu Engineer created HADOOP-11957:
-
Summary: if an IOException error is thrown in DomainSocket.close
we go into infinite loop.
Key: HADOOP-11957
URL: https://issues.apache.org/jira/browse/HADOOP-11957
Anu Engineer created HADOOP-11861:
-
Summary: test-patch script always fails when option
"--build-native=false" is specified
Key: HADOOP-11861
URL: https://issues.apache.org/jira/browse/HA
[
https://issues.apache.org/jira/browse/HADOOP-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer resolved HADOOP-11832.
---
Resolution: Won't Fix
> spnego authentication logs only log in debug mode so its d
Anu Engineer created HADOOP-11832:
-
Summary: spnego authentication logs only log in debug mode so its
difficult to debug auth isues
Key: HADOOP-11832
URL: https://issues.apache.org/jira/browse/HADOOP-11832
79 matches
Mail list logo
