Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

2017-12-12 Thread Elek, Marton
+1 (non-binding) * built from the source tarball (archlinux) / verified signature * Deployed to a kubernetes cluster (10/10 datanode/nodemanager pods) * Enabled ec on hdfs directory (hdfs cli) * Started example yarn jobs (pi/terragen) * checked yarn ui/ui2 Thanks for all the efforts.

Re: [DISCUSS] Feature Branch Merge and Security Audits

2017-10-21 Thread Elek, Marton
On 10/21/2017 02:41 AM, larry mccay wrote: "We might want to start a security section for Hadoop wiki for each of the services and components. This helps to track what has been completed." Do you mean to keep the audit checklist for each service and component there? Interesting idea, I

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-02-16 Thread Elek, Marton
Hi, I would like to bump this thread up. TLDR; There is a proposed version of a new hadoop site which is available from here: https://elek.github.io/hadoop-site-proposal/ and https://issues.apache.org/jira/browse/HADOOP-14163 Please let me know what you think about it. Longer version:

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-06-21 Thread Elek, Marton
. - We then modify the existing web-site to say that there is a new site/experience that folks can click on a link and navigate to - As this new website matures and gets feedback & fixes, we finally pull the plug at a later point of time when we think we are good to go. Thoughts? +Vinod On Feb 16

Re: [VOTE] Release Apache Hadoop 3.1.1 - RC0

2018-08-07 Thread Elek, Marton
+1 (non-binding) 1. Built from the source package. 2. Checked the signature 3. Started docker based pseudo cluster and smoketested some basic functionality (hdfs cli, ec cli, viewfs, yarn examples, spark word count job) Thank you very much the work Wangda. Marton On 08/02/2018 08:43 PM,

[DISCUSS] Alpha Release of Ozone

2018-08-06 Thread Elek, Marton
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; Security and HA, work on these features are progressing in Branches HDDS-4 and HDDS-151. Right now, Ozone can handle millions of keys and has a

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-09-07 Thread Elek, Marton
very soon. Thanks, Marton ps: Please give me write permission to the OLD wiki (https://wiki.apache.org/hadoop/), if you can. My username is MartonElek Thanks a lot. On 08/31/2018 10:07 AM, Elek, Marton wrote: Bumping this thread at last time. I have the following proposal: 1. I will request

Re: HADOOP-14163 proposal for new hadoop.apache.org

2018-08-31 Thread Elek, Marton
with this plan. Please comment if you have objections. Again: it allows immediate fallback at any time as svn repo will be kept as is (+ I will keep it up-to-date in the next 2 months) Thanks, Marton On 06/21/2018 09:00 PM, Elek, Marton wrote: Thank you very much to bump up this thread

Re: [VOTE] Release Apache Hadoop 3.0.1 (RC1)

2018-03-22 Thread Elek, Marton
+1 (non binding) I did a full build from source code, created a docker container and did various basic level tests with robotframework based automation and docker-compose based pseudo clusters[1]. Including: * Hdfs federation smoke test * Basic ViewFS configuration * Yarn example jobs *

[DISCUSS] Release Apache Hadoop Ozone 0.3.0-alpha

2018-10-25 Thread Elek, Marton
Hi all, Since the previous 0.2.1-alpha ozone release more than 170 patches have been committed to the apache trunk under hadoop-ozone/hadoop-hdds subprojects. The 0.3.0-alpha release carries an S3 compatible rest server. This allows S3 applications to work against Ozone with zero-changes. The

[VOTE] Release Apache Hadoop Ozone 0.3.0-alpha (RC0)

2018-11-13 Thread Elek, Marton
Hi all, I've created the first release candidate (RC0) for Apache Hadoop Ozone 0.3.0-alpha according to the plans shared here previously. This is the second release of Apache Hadoop Ozone. Notable changes since the first release: * A new S3 compatible rest server is added. Ozone can be used

[CANCELED] [VOTE] Release Apache Hadoop Ozone 0.3.0-alpha (RC0)

2018-11-14 Thread Elek, Marton
Unfortunately a memory issue is found with the default settings. Fixed in HDDS-834 (thanks Mukul and Shashikant) I cancel this vote and start a rc1 soon. Marton On 11/13/18 1:53 PM, Elek, Marton wrote: > Hi all, > > I've created the first release candidate (RC0) for Apache Hadoop Ozon

[VOTE] Release Apache Hadoop Ozone 0.3.0-alpha (RC1)

2018-11-14 Thread Elek, Marton
Hi all, I've created the second release candidate (RC1) for Apache Hadoop Ozone 0.3.0-alpha including one more fix on top of the previous RC0 (HDDS-854) This is the second release of Apache Hadoop Ozone. Notable changes since the first release: * A new S3 compatible rest server is added. Ozone

[ANNOUNCE] Apache Hadoop Ozone 0.2.1-alpha release

2018-10-01 Thread Elek, Marton
It gives me great pleasure to announce that the Apache Hadoop community has voted to release Apache Hadoop Ozone 0.2.1-alpha. Apache Hadoop Ozone is an object store for Hadoop built using Hadoop Distributed Data Store. For more information and to download, please check

[VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)

2018-09-19 Thread Elek, Marton
Hi all, After the recent discussion about the first Ozone release I've created the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha. This release is alpha quality: it’s not recommended to use in production but we believe that it’s stable enough to try it out the feature set

Re: [VOTE] Release Apache Hadoop 2.8.5 (RC0)

2018-09-19 Thread Elek, Marton
repository is correct for clone? I can clone readable repository (https://github.com/apache/hadoop-site) successfully though but cannot push back changes which is expected. Thanks, Junping Elek, Marton mailto:e...@apache.org>>于2018年9月17日 周一上午6:15写道: Hi Junping, Thank you t

[RESULT][VOTE] Release Apache Hadoop Ozone 0.2.1-alpha (RC0)

2018-09-26 Thread Elek, Marton
Thank you very much the tests and the votes for all of you. The vote is PASSED with the following details: 3 binding +1, (thanks Anu, Xiaoyu, Arpit) 10 non-binding +1, (thanks Hanisha, Bharat, Shashikant, Sandeep, Lokesh, Nanda, Mukul, Ajay, Dinesh) together with my closing +1 [*] no -1/0

Re: [VOTE] Release Apache Hadoop 2.8.5 (RC0)

2018-09-23 Thread Elek, Marton
refreshed. It seems like to need some manually steps to refresh the website -if so, can you also update to the wiki? Thanks, Junping Elek, Marton 于2018年9月20日 周四下午1:40写道: > Please try > > git clone https://gitbox.apache.org/repos/

Re: [Urgent] Question about Nexus repo and Hadoop release

2019-01-15 Thread Elek, Marton
he pgp pool? That's what Nexus is validating >> against. It might take time to propagate if you just pushed it. >> >> On Mon, Jan 14, 2019 at 9:59 AM Elek, Marton wrote: >> >>> Seems to be an INFRA issue for me: >>> >>> 1. I downloaded a sam

Re: [VOTE] Release Apache Hadoop 3.2.0 - RC1

2019-01-14 Thread Elek, Marton
Thanks Sunil to manage this release. +1 (non-binding) 1. built from the source (with clean local maven repo) 2. verified signatures + checksum 3. deployed 3 node cluster to Google Kubernetes Engine with generated k8s resources [1] 4. Executed basic HDFS commands 5. Executed basic yarn example

Re: [Urgent] Question about Nexus repo and Hadoop release

2019-01-14 Thread Elek, Marton
Seems to be an INFRA issue for me: 1. I downloaded a sample jar file [1] + the signature from the repository and it was ok, locally I verified it. 2. I tested it with an other Apache project (Ratis) and my key. I got the same problem even if it worked at last year during the 0.3.0 release. (I

Re: [DISCUSS] Move to gitbox

2018-12-13 Thread Elek, Marton
On 12/12/18 12:27 PM, Akira Ajisaka wrote: > Thank you for your positive feedback! I'll file a jira to INFRA in this > weekend. > >> If I understood well the only bigger task here is to update all the jenkins >> jobs. (I am happy to help/contribute what I can do) > Thank you Elek for the

Re: [DISCUSS] Move to gitbox

2018-12-09 Thread 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 here is to update all the jenkins jobs. (I am happy to help/contribute what I can do) Marton On 12/8/18 6:25 AM, Akira Ajisaka wrote: > Hi all, > > Apache Hadoop

[ANNOUNCE] Apache Hadoop Ozone 0.3.0-alpha release

2018-11-22 Thread Elek, Marton
It gives me great pleasure to announce that the Apache Hadoop community has voted to release Apache Hadoop Ozone 0.3.0-alpha (Arches). Apache Hadoop Ozone is an object store for Hadoop built using Hadoop Distributed Data Store. This release contains a new S3 compatible interface and additional

[RESULT][VOTE] Release Apache Hadoop Ozone 0.3.0-alpha (RC1)

2018-11-19 Thread Elek, Marton
Thank you very much the tests and the votes for all of you. The vote is PASSED with the following details: 3 binding +1, (thanks Arpit, Anu, Jitendra) 6 non-binding +1, (thanks Dinesh, Shashikant, Lokesh, Mukul, Bharat) together with my closing +1 [*] no -1/0 Thanks again, will publish the

Re: [NOTICE] Move to gitbox

2019-01-07 Thread Elek, Marton
t; > >> On 7 Jan 2019, at 06:55, Akira Ajisaka > <mailto:aajis...@apache.org>> wrote: >> >> Thanks Ayush for the report and thanks Elek for the fix! >> >> -Akira >> >> 2019年1月3日(木) 0:54 Elek, Marton > <mailto:e...@apache.org>>: >

Re: [OZONE] Community calls

2019-01-07 Thread Elek, Marton
ack is welcome, Thanks, Marton On 10/5/18 5:51 PM, Elek, Marton wrote: > > Hi everybody, > > > We start a new community call series about Apache Hadoop Ozone. It's an > informal discussion about the current items, short-term plans, > directions and contribution possibilities.

Re: [NOTICE] Move to gitbox

2019-01-08 Thread Elek, Marton
of the git.apache.org. It seems to be a mirror page only for the old-style+svn repositories)) On 1/7/19 3:18 PM, Steve Loughran wrote: > OK. so the original git://git.apache.org/hadoop.git is in fact deceased? > > > On 7 Jan 2019, at 14:15, Elek, Marton > mailto:e...@apache.org>&g

Re: [NOTICE] Move to gitbox

2019-01-02 Thread Elek, Marton
Thanks the report Ayush, The bogus repository is removed by the INFRA: https://issues.apache.org/jira/browse/INFRA-17526 And the cwiki page[1] is updated to use the gitbox url instead of git.apache.org Marton [1] https://cwiki.apache.org/confluence/display/HADOOP/Git+And+Hadoop On 1/2/19

Re: [DISCUSS] Docker build process

2019-03-19 Thread Elek, Marton
Thank you Eric to describe the problem. I have multiple small comments, trying to separate them. I. separated vs in-build container image creation > The disadvantages are: > > 1. Require developer to have access to docker. > 2. Default build takes longer. These are not the only

Re: [DISCUSS] Docker build process

2019-03-21 Thread Elek, Marton
> If versioning is done correctly, older branches can have the same docker > subproject, and Hadoop 2.7.8 can be released for older Hadoop branches. We > don't generate timeline paradox to allow changing the history of Hadoop > 2.7.1. That release has passed and let it stay that way. I

Re: [DISCUSS] Docker build process

2019-03-22 Thread Elek, Marton
release is ok to have wriggle room for developers, but I don't think that > flexibility is necessary for official release. > > Regards, > Eric > > On 3/21/19, 2:44 PM, "Elek, Marton" wrote: > > > > > If versioning is done correctly, older branches

Re: proposed new repository for hadoop/ozone docker images (+update on docker works)

2019-01-30 Thread Elek, Marton
YARN-7129 style of build process, and see this is a possible solution to > solve docker image generation issue? Thanks > > Regards, > Eric > > On 1/29/19, 3:44 PM, "Arpit Agarwal" > wrote: > > I’ve request

Re: [DISCUSS] Making submarine to different release model like Ozone

2019-02-01 Thread Elek, Marton
+1. I like the idea. For me, submarine/ML-job-execution seems to be a natural extension of the existing Hadoop/Yarn capabilities. And like the proposed project structure / release lifecycle, too. I think it's better to be more modularized but keep the development in the same project. IMHO it

Re: proposed new repository for hadoop/ozone docker images (+update on docker works)

2019-01-31 Thread Elek, Marton
> dockerfile-maven-plugin approach. > > Regards, > Eric > > On 1/30/19, 12:56 AM, "Elek, Marton" wrote: > > Thanks Eric the suggestions. > > Unfortunately (as Anu wrote it) our use-case is slightly different. > > It was

Re: proposed new repository for hadoop/ozone docker images (+update on docker works)

2019-02-05 Thread Elek, Marton
maven project version, which minimize > version number management between maven and docker. > > Regards, > Eric > > On 1/31/19, 8:59 AM, "Elek, Marton" wrote: > > > Hi Eric, > > Thanks for the answers > >

Re: [VOTE] Propose to start new Hadoop sub project "submarine"

2019-02-04 Thread Elek, Marton
+1 (non-binding) (my arguments are in the discuss thread. small move, huge benefit) Thanks, Marton On 2/1/19 11:15 PM, Wangda Tan wrote: > Hi all, > > According to positive feedbacks from the thread [1] > > This is vote thread to start a new subproject named "hadoop-submarine" > which follows

Re: VOTE: Hadoop Ozone 0.4.0-alpha RC1

2019-04-20 Thread Elek, Marton
+1 (non-binding) - build from source - run all the smoketest (from the fresh build based on the src package) - run all the smoketest from the binary package - signature files are checked - sha512 checksums are verified - ozone version shows the right commit information Thanks Ajay all the

Re: VOTE: Hadoop Ozone 0.4.0-alpha RC2

2019-05-04 Thread Elek, Marton
+1 (non-binding). Thanks the continuous effort Ajay. This is the best Ozone release package what I have ever seen: I checked the following: * Signatures are checked: OK * sha512 checksums are checked: OK * can be built from the source: OK * smoketest executed from the bin package (after

Re: [DISCUSS] Docker build process

2019-05-06 Thread Elek, Marton
Thanks the answers Eric Yang, I think we have similar view about how the releases are working and what you wrote is exactly the reason why I prefer the current method (docker image creation from separated branch) instead of the proposed one (create images from maven). 1. Not all the branches can

[DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree

2019-09-17 Thread Elek, Marton
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] to be part of the source tree but with separated release cadence, mainly

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree

2019-09-18 Thread Elek, Marton
oes for filesystem contract tests. are you happy with that? On Tue, Sep 17, 2019 at 10:48 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

Re: [VOTE] Release Apache Hadoop 3.2.1 - RC0

2019-09-18 Thread Elek, Marton
+1 (binding) Thanks Rohith the work with the release. * built from the source (archlinux) * verified signatures * verified sha512 checksums * started a docker-based pseudo cluster * tested basic HDFS operations with CLI * Checked if the sources are uploaded to the maven staging repo

[VOTE] Force "squash and merge" option for PR merge on github UI

2019-07-17 Thread Elek, Marton
Hi, Github UI (ui!) helps to merge Pull Requests to the proposed branch. There are three different ways to do it [1]: 1. Keep all the different commits from the PR branch and create one additional merge commit ("Create a merge commit") 2. Squash all the commits and commit the change as one

Re: [VOTE] Force "squash and merge" option for PR merge on github UI

2019-07-22 Thread Elek, Marton
Thanks for all the positive feedback, I opened INFRA-18777 to request the proposed change. Marton On 7/18/19 10:02 AM, Masatake Iwasaki wrote: > +1 > > Thanks, > Masatake Iwasaki > > On 7/17/19 15:07, Elek, Marton wrote: >> Hi, >> >> Github U

[VOTE] create ozone-dev and ozone-issues mailing lists

2019-10-27 Thread Elek, Marton
As discussed earlier in the thread of "Hadoop-Ozone repository mailing list configurations" [1] I suggested to solve the current misconfiguration problem with creating separated mailing lists (dev/issues) for Hadoop Ozone. It would have some additional benefit: for example it would make

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

2019-10-29 Thread Elek, Marton
point github to that? On Sun, Oct 27, 2019 at 10:12 PM Dinesh Chitlangia wrote: +1 -Dinesh On Sun, Oct 27, 2019, 4:25 AM Elek, Marton As discussed earlier in the thread of "Hadoop-Ozone repository mailing list configurations" [1] I suggested to solve the current misconfiguration problem w

Re: [Discuss] Hadoop-Ozone repository mailing list configurations

2019-10-23 Thread Elek, Marton
Thanks to report this problem Rohith, Yes, it seems to be configured with the wrong mailing list. I think the right fix is to create ozone-dev@ and ozone-issues@ and use them instead of hdfs-(dev/issues). Is there any objections against creating new ozone-* mailing lists? Thanks, Marton

Re: [VOTE] create ozone-dev and ozone-issues mailing lists

2019-10-31 Thread Elek, Marton
Thanks for all the votes and feedback. The vote is passed with no -1 and with many +1 The mailing lists will be created soon and the notification settings will be updated. Thank you for your patience. Marton On 10/27/19 9:25 AM, Elek, Marton wrote: As discussed earlier in the thread

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree [discussion -> lazy vote]

2019-09-23 Thread Elek, Marton
> Do you see a Submarine like split-also-into-a-TLP for Ozone? If not now, sometime further down the line? Good question, and I don't know what is the best answer right now. It's definitely an option, But Submarine move hasn't been finished, so it's not yet possible to learn form the

Re: [DISCUSS] Release Docs pointers Hadoop site

2019-10-08 Thread Elek, Marton
To be honest, I have no idea. I don't know about the historical meaning. But as there is no other feedback, here are my guesses based on pure logic: * current -> should point to the release with the highest number (3.2.1) * stable -> to the stable 3.x release with the highest number (3.2.1

Re: [VOTE] Release Apache Hadoop Ozone 0.4.1-alpha

2019-10-10 Thread Elek, Marton
+1 Thank you Nanda the enormous work to make this release happen. * GPG Signatures are fine * SHA512 signatures are fine * Can be built from the source package (in isolated environment without cached hadoop/ozone artifacts) * Started the pseudo cluster with `compose/ozone` * Executed

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree [discussion -> lazy vote]

2019-10-13 Thread Elek, Marton
Sure. Will do it that way. Thanks the feedback. Marton On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote: On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton wrote: As the overall feedback was positive (in fact many of the answers were simple +1 votes) I don't think the thread should

[NOTE] Ozone is moved out from Hadoop trunk

2019-10-13 Thread Elek, Marton
As discussed earlier Ozone is moved out from Hadoop trunk. Please commit / create pull requests to the --> https://github.com/apache/hadoop-ozone in the future. Remaining Ozone code will be deleted from Hadoop trunk with HDDS-2288. Marton

Re: [VOTE] Release Apache Hadoop Thirdparty 1.0.0

2020-02-28 Thread Elek, Marton
Thank you very much to work on this release Vinay, 1.0.0 is always a hard work... 1. I downloaded it and I can build it from the source 2. Checked the signature and the sha512 of the src package and they are fine 3. Yetus seems to be included in the source package. I am not sure if it's

[DISCUSS] making Ozone a separate Apache project

2020-05-13 Thread Elek, Marton
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 October of 2017 a discussion has been started to merge it to the Hadoop main branch

Re: [DISCUSS] making Ozone a separate Apache project

2020-05-18 Thread Elek, Marton
One question, for the committers who contributed to Ozone before and got the committer-role in the past (like me), will they carry the committer-role to the new repo? In short: yes. In more details: This discussion (if there is an agreement) should be followed by a next discussion +

Re: [VOTE] Apache Hadoop Ozone 0.5.0-beta RC2

2020-03-20 Thread Elek, Marton
+1 * signatures checked * sha512 checked * can be built from the source (without using my local mvn cache: using apache/ozone-build docker image) * created docker image with the provided Dockerfile * Deployed to Kubernetes together with Yarn and Hdfs * tested with 100G teragen (one

Re: [DISCUSS] making Ozone a separate Apache project

2020-05-27 Thread Elek, Marton
(based on the proposal) here 4. Voted proposal will be sent to the ASF board to be discussed/decided/approved. Thanks, again, all your feedback, Marton On 5/13/20 9:52 AM, Elek, Marton wrote: I would like to start a discussion to make a separate Apache project for Ozone ### HISTORY

Re: [DISCUSS] Removing the archiac master branch

2020-06-22 Thread Elek, Marton
On 6/19/20 7:19 PM, Owen O'Malley wrote: We unfortunately have a lot of master/slave and whitelist/blacklist terminology usage in Hadoop. It will take a while to fix them all, but one is easy to fix. In particular, we have a "master" branch that hasn't been used since the project

Re: [VOTE] Release Apache Hadoop 3.1.4 (RC4)

2020-08-03 Thread Elek, Marton
+1 (binding) * checked signature * built from source * deployed binary package to kubernetes * executed teragen with automatic tests [1] * checked "hadoop version" and compared with git revision * checked if the staging repository contains src packages Thanks the work (and the toughness)

[jira] [Created] (HADOOP-14160) Create dev-support scripts to do the bulk jira update required by the release process

2017-03-08 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-14160: - Summary: Create dev-support scripts to do the bulk jira update required by the release process Key: HADOOP-14160 URL: https://issues.apache.org/jira/browse/HADOOP-14160

[jira] [Created] (HADOOP-14164) Update the skin of maven-site during doc generation

2017-03-08 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-14164: - Summary: Update the skin of maven-site during doc generation Key: HADOOP-14164 URL: https://issues.apache.org/jira/browse/HADOOP-14164 Project: Hadoop Common

[jira] [Created] (HADOOP-14162) Improve release scripts to automate missing steps

2017-03-08 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-14162: - Summary: Improve release scripts to automate missing steps Key: HADOOP-14162 URL: https://issues.apache.org/jira/browse/HADOOP-14162 Project: Hadoop Common

[jira] [Created] (HADOOP-14163) Refactor existing hadoop site to use more usable static website generator

2017-03-08 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-14163: - Summary: Refactor existing hadoop site to use more usable static website generator Key: HADOOP-14163 URL: https://issues.apache.org/jira/browse/HADOOP-14163

[jira] [Created] (HADOOP-14898) Create official Docker images for development and testing features

2017-09-22 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-14898: - Summary: Create official Docker images for development and testing features Key: HADOOP-14898 URL: https://issues.apache.org/jira/browse/HADOOP-14898 Project

[jira] [Created] (HADOOP-14850) Read HttpServer2 resources directly from the source tree (if exists)

2017-09-08 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-14850: - Summary: Read HttpServer2 resources directly from the source tree (if exists) Key: HADOOP-14850 URL: https://issues.apache.org/jira/browse/HADOOP-14850 Project

[jira] [Created] (HADOOP-15065) Make mapreduce specific GenericOptionsParser arguments optional

2017-11-22 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15065: - Summary: Make mapreduce specific GenericOptionsParser arguments optional Key: HADOOP-15065 URL: https://issues.apache.org/jira/browse/HADOOP-15065 Project: Hadoop

[jira] [Created] (HADOOP-15122) Lock down version of doxia-module-markdown plugin

2017-12-15 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15122: - Summary: Lock down version of doxia-module-markdown plugin Key: HADOOP-15122 URL: https://issues.apache.org/jira/browse/HADOOP-15122 Project: Hadoop Common

[jira] [Resolved] (HADOOP-14162) Improve release scripts to automate missing steps

2017-11-09 Thread Elek, Marton (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton resolved HADOOP-14162. --- Resolution: Won't Fix > Improve release scripts to automate missing st

[jira] [Resolved] (HADOOP-14160) Create dev-support scripts to do the bulk jira update required by the release process

2017-11-09 Thread Elek, Marton (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton resolved HADOOP-14160. --- Resolution: Won't Fix > Create dev-support scripts to do the bulk jira update requi

[jira] [Created] (HADOOP-15084) Create docker images for latest stable hadoop2 build

2017-12-01 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15084: - Summary: Create docker images for latest stable hadoop2 build Key: HADOOP-15084 URL: https://issues.apache.org/jira/browse/HADOOP-15084 Project: Hadoop Common

[jira] [Created] (HADOOP-15083) Create base image for running hadoop in docker containers

2017-12-01 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15083: - Summary: Create base image for running hadoop in docker containers Key: HADOOP-15083 URL: https://issues.apache.org/jira/browse/HADOOP-15083 Project: Hadoop Common

[jira] [Created] (HADOOP-15539) Make start-build-env.sh usable in non-interactive mode

2018-06-14 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15539: - Summary: Make start-build-env.sh usable in non-interactive mode Key: HADOOP-15539 URL: https://issues.apache.org/jira/browse/HADOOP-15539 Project: Hadoop Common

[jira] [Created] (HADOOP-15259) Provide docker file for the development builds

2018-02-23 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15259: - Summary: Provide docker file for the development builds Key: HADOOP-15259 URL: https://issues.apache.org/jira/browse/HADOOP-15259 Project: Hadoop Common

[jira] [Created] (HADOOP-15256) Create docker images for latest stable hadoop3 build

2018-02-23 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15256: - Summary: Create docker images for latest stable hadoop3 build Key: HADOOP-15256 URL: https://issues.apache.org/jira/browse/HADOOP-15256 Project: Hadoop Common

[jira] [Created] (HADOOP-15257) Provide example docker compose file for developer builds

2018-02-23 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15257: - Summary: Provide example docker compose file for developer builds Key: HADOOP-15257 URL: https://issues.apache.org/jira/browse/HADOOP-15257 Project: Hadoop Common

[jira] [Created] (HADOOP-15258) Create example docker-compse file for documentations

2018-02-23 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15258: - Summary: Create example docker-compse file for documentations Key: HADOOP-15258 URL: https://issues.apache.org/jira/browse/HADOOP-15258 Project: Hadoop Common

[jira] [Created] (HADOOP-15656) Support byteman in hadoop-runner baseimage

2018-08-09 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15656: - Summary: Support byteman in hadoop-runner baseimage Key: HADOOP-15656 URL: https://issues.apache.org/jira/browse/HADOOP-15656 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-15673) Hadoop:3 image is missing from dockerhub

2018-08-15 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15673: - Summary: Hadoop:3 image is missing from dockerhub Key: HADOOP-15673 URL: https://issues.apache.org/jira/browse/HADOOP-15673 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-15730) Add Ozone submodule to the hadoop.apache.org

2018-09-07 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15730: - Summary: Add Ozone submodule to the hadoop.apache.org Key: HADOOP-15730 URL: https://issues.apache.org/jira/browse/HADOOP-15730 Project: Hadoop Common

[jira] [Created] (HADOOP-15302) Enable DataNode/NameNode service plugins with Service Provider interface

2018-03-09 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15302: - Summary: Enable DataNode/NameNode service plugins with Service Provider interface Key: HADOOP-15302 URL: https://issues.apache.org/jira/browse/HADOOP-15302 Project

[jira] [Created] (HADOOP-15367) Update the initialization code in the docker hadoop-runner baseimage

2018-04-05 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15367: - Summary: Update the initialization code in the docker hadoop-runner baseimage Key: HADOOP-15367 URL: https://issues.apache.org/jira/browse/HADOOP-15367 Project

[jira] [Created] (HADOOP-15369) Avoid usage of ${project.version} in parent pom

2018-04-06 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15369: - Summary: Avoid usage of ${project.version} in parent pom Key: HADOOP-15369 URL: https://issues.apache.org/jira/browse/HADOOP-15369 Project: Hadoop Common

[jira] [Created] (HADOOP-15352) FIx default local maven repository path in create-release script

2018-03-29 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15352: - Summary: FIx default local maven repository path in create-release script Key: HADOOP-15352 URL: https://issues.apache.org/jira/browse/HADOOP-15352 Project

[jira] [Created] (HADOOP-15353) Bump default yetus version in the yetus-wrapper

2018-03-29 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15353: - Summary: Bump default yetus version in the yetus-wrapper Key: HADOOP-15353 URL: https://issues.apache.org/jira/browse/HADOOP-15353 Project: Hadoop Common

[jira] [Created] (HADOOP-15339) Support additional key/value propereties in JMX bean registration

2018-03-23 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15339: - Summary: Support additional key/value propereties in JMX bean registration Key: HADOOP-15339 URL: https://issues.apache.org/jira/browse/HADOOP-15339 Project

[jira] [Created] (HADOOP-15340) Fix the RPC server name usage to provide information about the metrics

2018-03-23 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15340: - Summary: Fix the RPC server name usage to provide information about the metrics Key: HADOOP-15340 URL: https://issues.apache.org/jira/browse/HADOOP-15340 Project

[jira] [Created] (HADOOP-15857) Remove ozonefs class name definition from core-default.xml

2018-10-16 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15857: - Summary: Remove ozonefs class name definition from core-default.xml Key: HADOOP-15857 URL: https://issues.apache.org/jira/browse/HADOOP-15857 Project: Hadoop Common

[jira] [Reopened] (HADOOP-15339) Support additional key/value propereties in JMX bean registration

2018-10-29 Thread Elek, Marton (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton reopened HADOOP-15339: --- Since the commit we use this change from ozone/hdds and it worked well. This change

[jira] [Created] (HADOOP-15791) Remove Ozone related sources from the 3.2 branch

2018-09-25 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-15791: - Summary: Remove Ozone related sources from the 3.2 branch Key: HADOOP-15791 URL: https://issues.apache.org/jira/browse/HADOOP-15791 Project: Hadoop Common

[jira] [Created] (HADOOP-16063) Docker based pseudo-cluster definitions and test scripts for Hdfs/Yarn

2019-01-22 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16063: - Summary: Docker based pseudo-cluster definitions and test scripts for Hdfs/Yarn Key: HADOOP-16063 URL: https://issues.apache.org/jira/browse/HADOOP-16063 Project

[jira] [Created] (HADOOP-16064) Load configuration values from external sources

2019-01-22 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16064: - Summary: Load configuration values from external sources Key: HADOOP-16064 URL: https://issues.apache.org/jira/browse/HADOOP-16064 Project: Hadoop Common

[jira] [Created] (HADOOP-16003) Migrate the Hadoop jenkins jobs to use new gitbox urls

2018-12-13 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16003: - Summary: Migrate the Hadoop jenkins jobs to use new gitbox urls Key: HADOOP-16003 URL: https://issues.apache.org/jira/browse/HADOOP-16003 Project: Hadoop Common

[jira] [Created] (HADOOP-16146) Make start-build-env.sh safe in case of misusage of DOCKER_INTERACTIVE_RUN

2019-02-25 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16146: - Summary: Make start-build-env.sh safe in case of misusage of DOCKER_INTERACTIVE_RUN Key: HADOOP-16146 URL: https://issues.apache.org/jira/browse/HADOOP-16146

[jira] [Created] (HADOOP-16183) Use latest Yetus to support ozone specific build process

2019-03-13 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16183: - Summary: Use latest Yetus to support ozone specific build process Key: HADOOP-16183 URL: https://issues.apache.org/jira/browse/HADOOP-16183 Project: Hadoop Common

[jira] [Created] (HADOOP-16091) Create hadoop/ozone docker images with inline build process

2019-02-05 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16091: - Summary: Create hadoop/ozone docker images with inline build process Key: HADOOP-16091 URL: https://issues.apache.org/jira/browse/HADOOP-16091 Project: Hadoop

[jira] [Created] (HADOOP-16092) Move the source of hadoop/ozone containers to the same repository

2019-02-05 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16092: - Summary: Move the source of hadoop/ozone containers to the same repository Key: HADOOP-16092 URL: https://issues.apache.org/jira/browse/HADOOP-16092 Project

[jira] [Resolved] (HADOOP-16092) Move the source of hadoop/ozone containers to the same repository

2019-06-03 Thread Elek, Marton (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton resolved HADOOP-16092. --- Resolution: Won't Fix > Move the source of hadoop/ozone containers to the same reposit

[jira] [Created] (HADOOP-16338) Use exec in hadoop-runner base image instead of fork

2019-05-30 Thread Elek, Marton (JIRA)
Elek, Marton created HADOOP-16338: - Summary: Use exec in hadoop-runner base image instead of fork Key: HADOOP-16338 URL: https://issues.apache.org/jira/browse/HADOOP-16338 Project: Hadoop Common

  1   2   >