[jira] [Created] (HADOOP-19148) Update solr from 8.11.2 to 8.11.3 to address CVE-2023-50298

Brahma Reddy Battula created HADOOP-19148: - Summary: Update solr from 8.11.2 to 8.11.3 to address CVE-2023-50298 Key: HADOOP-19148 URL: https://issues.apache.org/jira/browse/HADOOP-19148

Query : Hadoop Cluster OS upgrade

Hi All, Does anybody tried out/share learnings ,using maintenance state or upgrade domains for big data cluster OS upgrades? Regards, Brahma

Re: [INFO] Hadoop-3.4 Release Update

Thanks for driving this. One query: Does all the jiras from 3.3 are part of the 3.4? On Mon, 22 Jan 2024 at 11:50 AM, slfan1989 wrote: > Thank you very much for specifying the frozen time for the > Branch-3.4.0. @Xiaoqiao > He > > If there is a need to backport any PRs to

Re: Resources for understanding Hadoop

e similar binaries so that I > can test my changes locally. Is there some documentation on how to do this? > > On Mon, 13 Jun 2022 at 00:26, Brahma Reddy Battula > wrote: > >> Hi Rahul, >> >> Welcome to hadoop world. >> >> Apart from

Re: Resources for understanding Hadoop

zed, entrypoints etc. Can someone point me to such > resources? > > Also is there a slack workspace for such discussions? Not sure if this > > mailing list is the right forum for such doubts. > > > -- --Brahma Reddy Battula

Re: Hadoop-3.2.3 Release Update

Sorry, I was looking for some CVE’s fixes.will make it progress on this… On Tue, 11 Jan 2022 at 5:58 PM, Wei-Chiu Chuang wrote: > Is this still making progress? > > On Tue, Oct 5, 2021 at 8:45 PM Brahma Reddy Battula > wrote: > > > Hi Akira, > > > > Tha

Re: Hadoop-3.2.3 Release Update

flict, So I checked in directly. > BTW, > > run some unit tests and build pseudo cluster to verify, it seems to work > > fine. > > FYI. > > > > Regards, > > - He Xiaoqiao > > > > On Thu, Sep 16, 2021 at 10:52 PM Brahma Reddy Battula > > >

[jira] [Created] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611

Brahma Reddy Battula created HADOOP-17917: - Summary: Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 Key: HADOOP-17917 URL: https://issues.apache.org/jira/browse/HADOOP-17917

Re: Hadoop-3.2.3 Release Update

in branch-3.2 & branch-3.2.3. FYI. >> >> On Tue, Sep 14, 2021 at 3:52 AM Brahma Reddy Battula >> wrote: >> >>> Hi All, >>> >>> Waiting for the following jira to commit to hadoop-3.2.3 , mostly this >>> can >>> be done by th

Re: [Conference] Uber's story on running Apache Hadoop deployment in Docker

Thanks all for attending the session, Hope we can have some more Good sessions.. Please find the recordings. https://drive.google.com/drive/u/1/folders/1mtIEUfnEUtil65U0nGGeJNAUYVsPpktt On Wed, Sep 8, 2021 at 7:37 PM Brahma Reddy Battula wrote: > Hi Sean, > > Pacific Time 9th, Sep

Re: Hadoop-3.2.3 Release Update

Hi All, Waiting for the following jira to commit to hadoop-3.2.3 , mostly this can be done by this week,then I will try to create the RC next if there is no objection. https://issues.apache.org/jira/browse/HDFS-15160 On Mon, Aug 16, 2021 at 2:22 PM Brahma Reddy Battula wrote: > @Ak

Re: [Conference] Uber's story on running Apache Hadoop deployment in Docker

> Pacific Time? > > > On Sep 8, 2021, at 1:17 AM, Brahma Reddy Battula > wrote: > > > > Hi All, > > > > Updated the meeting to record the session.. Please use the following link > > to attend the conference tomorrow. > > > > > > Uber's s

Re: [Conference] Uber's story on running Apache Hadoop deployment in Docker

://meet.google.com/few-wppc-xoa <https://meet.google.com/few-wppc-xoa>* Or dial: ‪(US) +1 443-424-3811‬ PIN: ‪384 713 518‬# More phone numbers: https://tel.meet/few-wppc-xoa?pin=7430296860915 On Fri, Aug 27, 2021 at 12:43 PM Brahma Reddy Battula wrote: > Hi All, > > Happy to announc

[Conference] Uber's story on running Apache Hadoop deployment in Docker

# <8338274491,,273569658#> United States (Toll-free) Phone Conference ID: 273 569 658# Find a local number <https://dialin.teams.microsoft.com/354a6938-11bf-45f7-97f9-0a77a564c966?id=273569658> | Reset PIN <https://mysettings.lync.com/pstnconferencing> -- Brahma Reddy Battula

Re: Hadoop-3.2.3 Release Update

t, > > it would be nice to have these on Hadoop too. > > > > > >> - > https://github.com/apache/bigtop/blob/master/bigtop-packages/src/common/hadoop/patch7-remove-phantomjs-in-yarn-ui.diff > > > > This is for aarch64 and ppe64le lacking required phantomjs. &g

Re: Hadoop-3.2.3 Release Update

oth the latest release and > > trunk branch). > > Chao Sun will validate the Spark Project (Got in touch with Chao > already). > > once RC is out. > > > > Thanks and Regards, > > - He Xiaoqiao > > > > > > On Tue, Aug 10, 2021 at 5:54 PM Brahma Redd

Hadoop-3.2.3 Release Update

me know anybody from these communities who can help on this. Planning to create RC by this month end. Any suggestions are welcome. --Brahma Reddy Battula

Re: [DISCUSS] Tips for improving productivity, workflow in the Hadoop project?

@Wei-Chiu Chuang looks this is not concluded yet... Can we move forward..? On Thu, Jul 15, 2021 at 11:09 PM Brahma Reddy Battula wrote: > > I agree with Ahmed Hussein…Jira should not be used for number generation.. > > We can always revisit the jira to see useful discussion

Re: [External Sender] Re: [DISCUSS] Hadoop 3.2.3 release

tem.mkdirs(FileSystem.java:2304) > at > > org.apache.hadoop.fs.contract.AbstractFSContractTestBase.mkdirs(AbstractFSContractTestBase.java:338) > at > > org.apache.hadoop.fs.contract.AbstractFSContractTestBase.setup(AbstractFSContractTestBase.java:193) > > On Tue,

[jira] [Resolved] (HADOOP-17840) Backport HADOOP-17837 to branch-3.2

[ https://issues.apache.org/jira/browse/HADOOP-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-17840. --- Fix Version/s: 3.2.3 Hadoop Flags: Reviewed Resolution: Fixed

[jira] [Resolved] (HADOOP-17837) Make it easier to debug UnknownHostExceptions from NetUtils.connect

[ https://issues.apache.org/jira/browse/HADOOP-17837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-17837. --- Hadoop Flags: Reviewed Resolution: Fixed [~bbeaudreault] thanks

Re: [DISCUSS] Hadoop 3.2.3 release

l unresolved issues > > (target > > >> > version/s: 3.2.3) to 3.2.4 after checking both of them are not > blocker > > >> > issues. Dashboard[1] is clean now. > > >> > > > >> > Regards, > > >> > - He Xiaoqiao > > >>

Re: [DISCUSS] Hadoop 3.2.3 release

Update on this thread. Will cut off the branch next week. And planning to release it in the last week of next month. Please try to mark jira's which are required for this release if anything is missed or reply to this mail. On Sun, Jul 25, 2021 at 5:14 PM Brahma Reddy Battula wrote

Re: [DISCUSS] Hadoop 3.2.3 release

Hi Brahma, > > > > Thank you for volunteering! > > > > -Akira > > > > On Fri, Jul 23, 2021 at 5:57 PM Brahma Reddy Battula > > wrote: > > > > > > Hi Akira, > > > > > > Thanks for bringing this.. > > > > > > I want t

Re: [DISCUSS] Hadoop 3.2.3 release

@hadoop.apache.org > For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org > > -- --Brahma Reddy Battula

Re: [DISCUSS] Tips for improving productivity, workflow in the Hadoop project?

/jira/browse/INFRA-15258> > >>>> > >>>> 4. New JIRA fields > >>>> It's possible to add new fields. For example, we can add a "Reviewer" > >>>> field, which could help improve the attention to issues. > >>>> > >>>> 5. Doc update > >>>> It is possible to set up automation such that the doc on the Hadoop > >>> website > >>>> is refreshed for every commit, providing the latest doc to the public. > >>>> > >>>> 6. Webhook > >>>> It's possible to set up webhook such that every commit in GitHub sends > >> a > >>>> notification to the ASF slack. It can be used for other kinds of > >>>> automation. Sky's the limit. > >>>> > >>>> Thoughts? What else can do we? > >>> > >>> - > >>> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > >>> For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >>> > >>> > >> > > > > > > - > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org > > -- --Brahma Reddy Battula

[jira] [Created] (HADOOP-17800) CLONE - Uber-JIRA: Hadoop should support IPv6

Brahma Reddy Battula created HADOOP-17800: - Summary: CLONE - Uber-JIRA: Hadoop should support IPv6 Key: HADOOP-17800 URL: https://issues.apache.org/jira/browse/HADOOP-17800 Project: Hadoop

Re: [ANNOUNCE] Apache Hadoop 3.3.1 release

a, Xiaoqiao He and other folks who continued helps for this > release process. > > Best Regards, > Wei-Chiu Chuang > -- --Brahma Reddy Battula

Re: [E] Re: Do I need a +1 to merge a backport PR?

> --------- > > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > -- --Brahma Reddy Battula

Re: [DISCUSS] Hadoop 3.3.1 release

t; becomes >> > > even >> > > > > > larger. >> > > > > > >> > > > > > I believe there are currently only two real blockers for a >> 3.3.1 >> > > > (using >> > > > > > this filter >> > > > > > >&

Re: [DISCUSS] Hadoop 3.3.1 release

C%20YARN%2C%20MAPREDUCE)%20AND%20cf%5B12310320%5D%20in%20(3.3.1)%20AND%20status%20not%20in%20(Resolved)%20ORDER%20BY%20priority%20DESC > > > > > ) > > > > > > > > > > > > > > > 1. HDFS-15566 <https://issues.apache.org/jira/browse/HDFS-15566> > > > > > 2. > > > > > 1. HADOOP-17112 < > > > https://issues.apache.org/jira/browse/HADOOP-17112 > > > > > > > > > > 2. > > > > > > > > > > > > > > > > > > > > Is there anyone who would volunteer to be the 3.3.1 RM? > > > > > > > > > > Also, the HowToRelease wiki does not describe the ARM build > process. > > > > That's > > > > > going to be important for future releases. > > > > > > > > - > > > > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > > > > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > > > > > > > > > > -- --Brahma Reddy Battula

[jira] [Created] (HADOOP-17236) Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640

Brahma Reddy Battula created HADOOP-17236: - Summary: Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 Key: HADOOP-17236 URL: https://issues.apache.org/jira/browse/HADOOP-17236 Project

Re: [Virtual MEETUP]: Migration to Hadoop 3

for ACL commands.Only hadoop-3 clients will work against hadoop-3 server during the upgrade. https://issues.apache.org/jira/browse/HDFS-6984 On Wed, Aug 26, 2020 at 11:06 PM Brahma Reddy Battula wrote: > > Hi Eric, > > check the following references for the same. > > 01/0

Re: [Virtual MEETUP]: Migration to Hadoop 3

- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > > -- --Brahma Reddy Battula

Re: Mandarin Hadoop online sync this week

6 Wednesday US Pacific Time 10PM > > Link: > https://cloudera.zoom.us/j/880548968 > > Past sync summary: > > https://docs.google.com/document/d/1jXM5Ujvf-zhcyw_5kiQVx6g-HeKe-YGnFS_1-qFXomI/edit > -- --Brahma Reddy Battula

[jira] [Created] (HADOOP-17225) Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172

Brahma Reddy Battula created HADOOP-17225: - Summary: Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172 Key: HADOOP-17225 URL: https://issues.apache.org/jira/browse/HADOOP

[jira] [Created] (HADOOP-17221) Upgrade log4j-1.2.17 to atlassian ( To Adress: CVE-2019-17571)

Brahma Reddy Battula created HADOOP-17221: - Summary: Upgrade log4j-1.2.17 to atlassian ( To Adress: CVE-2019-17571) Key: HADOOP-17221 URL: https://issues.apache.org/jira/browse/HADOOP-17221

[jira] [Created] (HADOOP-17220) Upgrade slf4j to 1.7.30 ( To Adress: CVE-2018-8088)

Brahma Reddy Battula created HADOOP-17220: - Summary: Upgrade slf4j to 1.7.30 ( To Adress: CVE-2018-8088) Key: HADOOP-17220 URL: https://issues.apache.org/jira/browse/HADOOP-17220 Project

Re: Progress

; > > Akira > > > > > > > > On Wed, Jul 22, 2020 at 8:39 PM Gavin McDonald > > > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > Seems there is still not much happening in the way of migrating to > > &g

[ANNOUNCE] Apache Hadoop 3.3.0 release

.3.3.0.html [4] https://hadoop.apache.org/rele <https://hadoop.apache.org/releases.html> ases.html Regards, Brahma Reddy Battula

Re: [RESULT][VOTE] Rlease Apache Hadoop-3.3.0

cut a new release candidate? > > Thanks, > > Stephen. > > On Tue, Jul 14, 2020 at 1:22 PM Brahma Reddy Battula > wrote: > > > Hi All, > > > > With 8 binding and 11 non-binding +1s and no -1s the vote for Apache > > hadoop-3.3.0 Release > > passes. >

[RESULT][VOTE] Rlease Apache Hadoop-3.3.0

+1s = Akira Ajisaka Vinayakumar B Inigo Goiri Surendra Singh Lilhore Masatake Iwasaki Rakesh Radhakrishnan Eric Badger Brahma Reddy Battula Non-binding +1s = Zhenyu Zheng Sheng Liu Yikun Jiang Tianhua huang Ayush Saxena Hemanth Boyina Bilwa S T Takanobu Asanuma Xiaoqiao He CR

Re: [VOTE] Release Apache Hadoop 3.3.0 - RC0

Xiaoqiao He wrote: > Thanks Brahma Reddy Battula for your great work here. > Stephen fixed lease leak in namenode, and it is ready now: > https://issues.apache.org/jira/browse/HDFS-14498. > I think this affects 3.3.0-RC0. Would you check this? > Sorry for reporting it so late. >

[VOTE] Release Apache Hadoop 3.3.0 - RC0

testing with my pseudo cluster. My +1 to start. Regards, Brahma Reddy Battula 1. project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.3.0) AND fixVersion not in (3.2.0, 3.2.1, 3.1.3) AND status = Resolved ORDER BY fixVersion ASC

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

YARN-10314 > > > > We should wait for that as well, should get concluded in a day or two. > > > > -Ayush > > > > > On 15-Jun-2020, at 7:21 AM, Sheng Liu wrote: > > > > > > The HADOOP-17046 <https://issues.apache.org/jira/browse/HADOOP-17046

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

has been created for quite a while. Not sure > if there is remain block issue that need to be addressed before Hadoop > 3.3.0 release publishing, maybe we can bring up to here and move the > release forward ? > > Thank. > > Brahma Reddy Battula 于2020年3月25日周三 上午1:55写道： > >

Re: [NOTICE] Removal of protobuf classes from Hadoop Token's public APIs' signature

> > > > > BlockingService scmDatanodeService = > > > > > StorageContainerDatanodeProtocolService. > > > > > newReflectiveBlockingService( > > > > > new > > StorageContainerDatanodeProtocolServerSideTranslatorPB( > > > > > server, > Mockito.mock(ProtocolMessageMetrics.class))); > > > > > > > > > > > > > > > > > > > > Ratis probably breaks as well since it depends on the Hadoop RPC > > > > framework > > > > > too. > > > > > > > > > > On Tue, Apr 28, 2020 at 10:58 PM Vinayakumar B < > > > vinayakum...@apache.org> > > > > > wrote: > > > > > > > > > > > hi Wei-Chiu, > > > > > > > > > > > > Can you elaborate on what failures you are facing related to > > > relocated > > > > > > protobuf classes.. ? > > > > > > > > > > > > IFAIK, if the issue with location of protobuf classes, still old > > jar > > > > > > protobuf-2.5.0.jar will be available in classpath. So downstream > > > > > depending > > > > > > on 2.5.0 version of protobuf still be able to access them. > > > > > > > > > > > > -vinay > > > > > > > > > > > > On Wed, 29 Apr 2020, 11:17 am Wei-Chiu Chuang, < > > weic...@cloudera.com > > > > > > > > > > wrote: > > > > > > > > > > > >> I'm sorry for coming to this late. I missed this message. It > > should > > > > have > > > > > >> been a DISCUSS thread rather than NOTICE. > > > > > >> > > > > > >> Looks like this is inevitable. But we should make the downstream > > > > > >> developers aware & make the update easier. As long as it is > stated > > > > > clearly > > > > > >> how to update the code to support Hadoop 3.3, I am okay with > that. > > > > > >> > > > > > >> Here's what I suggest: > > > > > >> (1) label the jira incompatible (just updated the jira) and > > updated > > > > the > > > > > >> release note to tell app developer how to update. > > > > > >> (2) declare ProtobufHelper a public API HADOOP-17019 > > > > > >> <https://issues.apache.org/jira/browse/HADOOP-17019> > > > > > >> > > > > > >> Tez doesn't use the removed Token API, but there's code that > > breaks > > > > with > > > > > >> the relocated protobuf class. The ProtobufHelper API will make > > this > > > > > >> transition much easier. > > > > > >> > > > > > >> Other downstreamers that break with the relocated protobuf > > include: > > > > > Ozone > > > > > >> and HBase. but neither of them use the removed Token API. > > > > > >> > > > > > >> > > > > > >> On Wed, Jan 8, 2020 at 4:40 AM Vinayakumar B < > > > vinayakum...@apache.org > > > > > > > > > > >> wrote: > > > > > >> > > > > > >>> Hi All, > > > > > >>> > > > > > >>>This mail is to notify about the Removal of following public > > > APIs > > > > > from > > > > > >>> Hadoop Common. > > > > > >>> > > > > > >>> ClassName: org.apache.hadoop.security.token.Token > > > > > >>> APIs: > > > > > >>> public Token(TokenProto tokenPB); > > > > > >>> public TokenProto toTokenProto(); > > > > > >>> > > > > > >>>Reason: These APIs are having Generated protobuf classes in > > the > > > > > >>> signature. Right now due to protobuf upgrade in trunk (soon to > be > > > > 3.3.0 > > > > > >>> release) these APIs are breaking the downstream builds, even > > though > > > > > >>> downstreams dont use these APIs (just Loading Token class). > > > > Downstreams > > > > > >>> are > > > > > >>> still referencing having older version (2.5.0) of protobuf, > hence > > > > build > > > > > >>> is > > > > > >>> being broken. > > > > > >>> > > > > > >>> These APIs were added for the internal > purpose(HADOOP-12563), > > > to > > > > > >>> support serializing tokens using protobuf in UGI Credentials. > > > > > >>> Same purpose can be achieved using the Helper classes without > > > > > introducing > > > > > >>> protobuf classes in API signatures. > > > > > >>> > > > > > >>> Token.java is marked as Evolving, so I believe APIs can be > > changed > > > > > >>> whenever > > > > > >>> absolute necessary. > > > > > >>> > > > > > >>> Jira https://issues.apache.org/jira/browse/HADOOP-16621 > has > > > been > > > > > >>> reported to solve downstream build failure. > > > > > >>> > > > > > >>> So since this API was added for internal purpose easy approach > to > > > > solve > > > > > >>> this is to remove APIs and use helper classes. Otherwise, as > > > > mentioned > > > > > in > > > > > >>> HADOOP-16621, workaround will add unnecessary codes to be > > > maintained. > > > > > >>> > > > > > >>> If anyone using these APIs outside hadoop project accidentally, > > > > please > > > > > >>> reply to this mail immediately. > > > > > >>> > > > > > >>> If no objection by next week, will go ahead with removal of > above > > > > said > > > > > >>> APIs > > > > > >>> in HADOOP-16621. > > > > > >>> > > > > > >>> -Vinay > > > > > >>> > > > > > >> > > > > > > > > > > > > > > > -- --Brahma Reddy Battula

Re: [DISCUSS] making Ozone a separate Apache project

uss the long-term future of Ozone. Managing it as a separated > TLP > > > project seems to have more benefits. > > > > > > > > > Please let me know what your opinion is... > > > > > > Thanks a lot, > > > Marton > > > > > > > > > > > > > > > > > > [1]: For more details, see: > > > https://github.com/apache/hadoop-ozone/blob/master/HISTORY.md > > > > > > [2]: > > > > > > > > > https://lists.apache.org/thread.html/0d0253f6e5fa4f609bd9b917df8e1e4d8848e2b7fdb3099b730095e6%40%3Cprivate.hadoop.apache.org%3E > > > > > > [3]: > > > > > > > > > https://lists.apache.org/thread.html/8be74421ea495a62e159f2b15d74627c63ea1f67a2464fa02c85d4aa%40%3Chdfs-dev.hadoop.apache.org%3E > > > > > > - > > > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > > > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > > > > > -- --Brahma Reddy Battula

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

rong. >> >> -Surendra >> >> >> On Sat, 25 Apr, 2020, 9:33 am Mingliang Liu, wrote: >> >> > Brahma, >> > >> > What about https://issues.apache.org/jira/browse/HADOOP-17007? >> > >> > Thanks, >> > >> > On Fri, Apr

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

he fix version to 3.3.1. > > I think now we should cut branch-3.3.0 and freeze source code except the > > blockers. > > > > -Akira > > > > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula > > wrote: > > > >> Sure, I will do that. > >

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

preparing the release. > Could you cut branch-3.3.0? I would like to backport some fixes for 3.3.1 > and not for 3.3.0. > > Thanks and regards, > Akira > > On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula > wrote: > >> Hi All, >> >> we are down to tw

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

Brahma Reddy Battula wrote: > > @Prabhu Joseph > >>> Have committed the YARN blocker YARN-10219 to trunk and cherry-picked > to branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and > HADOOP-16982 > which i will help to review and commit. Thanks. > &g

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

hich i will help to review and commit. Thanks. > >> > >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png] > >> > >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in (Blocker, > >> Critical) AND resolution = Unresolved AND "Target Version/s" = 3

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

ther JIRA (HDFS-15272) to track backport branch-3.1, close this > one to decouple release progress. > > Thanks, > Hexiaoqiao > > On Sun, Apr 12, 2020 at 2:49 AM Brahma Reddy Battula > wrote: > > > *Pending for 3.3.0 Release:* > > > > One B

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[image: Minor] PATCH AVAILABLE *Unresolved* 11/Apr/20 28/Nov/19 Actions <https://issues.apache.org/jira/rest/api/1.0/issues/13271202/ActionsAndOperations?atl_token=A5KQ-2QAV-T4JA-FDED_194e108bac53dceebb1b88ae92ef65a9eba913b0_lin> <https://issues.apache.org/jira/browse/YARN-9354>

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

solved AND (cf[12310320] > = 3.3.0 OR fixVersion = 3.3.0) ORDER BY priority DESC > > Thanks, > Prabhu Joseph > > On Tue, Apr 7, 2020 at 1:27 PM Akira Ajisaka wrote: > > > Hi Brahma, > > > > How is this issue going? > > If there are some blockers, I can help y

Re: JENKINS is not posting build results in jiras

hed in > jiras. > > >>> > > >>> For eg, > > https://builds.apache.org/job/PreCommit-YARN-Build/25735/console > > >>> has > > >>> results. but I cannot see the same in YARN-9879. Similarly in the > cases > > >>> of YARN-10198 etc. > > >>> > > >>> I could see a message in console o/p as "Adding comment to JIRA". But > > its > > >>> not happening. > > >>> > > >>> Any ideas? > > >>> > > >>> Thanks > > >>> Sunil > > >>> > > >> > > > -- --Brahma Reddy Battula

[Hadoop-3.3 Release update]- branch-3.3 has created

thread[2]). 1.https://github.com/apache/hadoop/commits/branch-3.3 2.https://lists.apache.org/list.html?common-dev@hadoop.apache.org:2020-3 --Brahma Reddy Battula

Re: Hadoop 3.3 Release Plan Proposal

AND "Target Version/s" = 3.3.0 ORDER > BY priority DESC > > > > On Thu, Feb 27, 2020 at 12:42 AM Brahma Reddy Battula > wrote: > >> Hi All, >> >> Inline with the original 3.3.0 communication proposal dated 8th Jan 2020, >> I would like to p

Re: Hadoop 3.3 Release Plan Proposal

ority DESC On Thu, Feb 27, 2020 at 12:42 AM Brahma Reddy Battula wrote: > Hi All, > > Inline with the original 3.3.0 communication proposal dated 8th Jan 2020, > I would like to provide more updates[1]. > > We are approaching previously proposed code freeze date (March 10,2020).

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

; > Still there are possible options to collaborate with RM ( as brahma > mentioned earlier) and provide ARM artifact may be before or after vote. > If feasible RM can decide to add ARM artifact by collaborating with @Brahma > Reddy Battula or me to get the ARM artifact. > > -Vin

Re: [RESULT] [VOTE] Release Apache Hadoop Thirdparty 1.0.0 - RC1

-1261/ > >> > > >> > The RC tag in git is here: > >> > https://github.com/apache/hadoop-thirdparty/tree/release-1.0.0-RC1 > >> > > >> > And my public key is at: > >> > https://dist.apache.org/repos/dist/release/hadoop/common/KEYS > >> > > >> > *This vote will run for 5 days, ending on March 18th 2020 at 11:59 pm > >> IST.* > >> > > >> > For the testing, I have verified Hadoop trunk compilation with > >> >"-DdistMgmtSnapshotsUrl= > >> > > >> > https://repository.apache.org/content/repositories/orgapachehadoop-1261/ > >> > -Dhadoop-thirdparty-protobuf.version=1.0.0" > >> > > >> > My +1 to start. > >> > > >> > -Vinay > >> > > >> > > > -- --Brahma Reddy Battula

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

lso if we go ahead then the RM documentation should be clear this is an > optional step. > > > > On Mar 17, 2020, at 11:06 AM, Brahma Reddy Battula > wrote: > > > > Sure, we can't make mandatory while voting and we can upload to downloads > > once release vote is

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

t I meant. I don’t want us to make more mandatory work for > the release manager because the job is hard enough already. > > > > On Mar 17, 2020, at 10:46 AM, Brahma Reddy Battula > wrote: > > > > Sorry,didn't get you...do you mean, once release voting is processed and

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

wrote: > Can ARM binaries be provided after the fact? We cannot increase the RM’s > burden by asking them to generate an extra set of binaries. > > > > On Mar 17, 2020, at 10:23 AM, Brahma Reddy Battula > wrote: > > > > + Dev mailing list. > > > > --

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

crete work that RM need to do extra for ARM > > release, that would help us to better understand. > > > > Thanks, > > > > Junping > > > > Akira Ajisaka 于2020年3月13日周五 上午12:34写道： > > > >> If you can provide ARM release for future releases, I'm fin

Fwd: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

+ Dev mailing list. -- Forwarded message - From: Brahma Reddy Battula Date: Tue, Mar 17, 2020 at 10:31 PM Subject: Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary To: junping_du thanks junping for your reply. bq. I think most of us in Hadoop community doesn't want

Re: [DISCUSS] Hadoop 3.3.0 Release include ARM binary

atures > for releases MUST NOT be created on ASF machines. > > We need to have dedicated physical ARM machines for each release manager, > and now it is not feasible. > If you provide an unofficial ARM binary release in some repository, that's > okay. > > -Akira > > O

[DISCUSS] Hadoop 3.3.0 Release include ARM binary

release project in jenkins..? So that future RM's just trigger the jenkin project. Please let me know your thoughts on this. 1. https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-qbt-linux-ARM-trunk/ 2.https://hadoop.apache.org/releases.html --Brahma Reddy Battula

Re: Hadoop 3.3 Release Plan Proposal

t; = 3.3.0 ORDER BY priority DESC On Wed, Jan 22, 2020 at 11:22 PM Brahma Reddy Battula wrote: > > Wiki was updated for 3.3 > https://cwiki.apache.org/confluence/display/HADOOP/Roadmap#Roadmap-3.3.0. > > > >I'll move out anything that isn't needed. > > thanks s

Re: Hadoop 3.3 Release Plan Proposal

and inevitably the big > JAR changes will have surprises. We need to fix the shaded protobuf in > Token issue to even get spark to compile. > > -Steve > > > > > > -- --Brahma Reddy Battula

Hadoop 3.3 Release Plan Proposal

y DESC Note: i) added the owners based on the jira assignee and reporter.. Please correct me ii) will update cwiki Regards, Brahma Reddy Battula

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

t;> > > >> dont care about which version of original "protobuf-java" is > > in > > > >> > > >> dependency. > > > >> > > >>6. Just keep "protobuf-java:2.5.0" in dependency tree not > to > > > >> break > > > >> > > the > > > >> > > >> downstreams. But hadoop will be originally using the latest > > > >> protobuf > > > >> > > >> present in "o.a.h.thirdparty:hadoop-shaded-protobuf". > > > >> > > >> > > > >> > > >>7. Coming back to separate repo, Following are most > > > appropriate > > > >> > > reasons > > > >> > > >> of keeping shaded dependency artifact in separate repo > instead > > of > > > >> > > >> submodule. > > > >> > > >> > > > >> > > >> 7a. These artifacts need not be built all the time. It > > needs > > > >> to > > > >> > be > > > >> > > >> built only when there is a change in the dependency version > or > > > the > > > >> > build > > > >> > > >> process. > > > >> > > >> 7b. If added as "submodule in Hadoop repo", > > > >> > > maven-shade-plugin:shade > > > >> > > >> will execute only in package phase. That means, "mvn compile" > > or > > > >> "mvn > > > >> > > >> test-compile" will not be failed as this artifact will not > have > > > >> > > relocated > > > >> > > >> classes, instead it will have original classes, resulting in > > > >> > compilation > > > >> > > >> failure. Workaround, build thirdparty submodule first and > > exclude > > > >> > > >> "thirdparty" submodule in other executions. This will be a > > > complex > > > >> > > process > > > >> > > >> compared to keeping in a separate repo. > > > >> > > >> > > > >> > > >> 7c. Separate repo, will be a subproject of Hadoop, using > > the > > > >> > same > > > >> > > >> HADOOP jira project, with different versioning prefixed with > > > >> > > "thirdparty-" > > > >> > > >> (ex: thirdparty-1.0.0). > > > >> > > >> 7d. Separate will have same release process as Hadoop. > > > >> > > >> > > > >> > > >>HADOOP-13363 ( > > > >> https://issues.apache.org/jira/browse/HADOOP-13363) > > > >> > > is > > > >> > > >> an > > > >> > > >> umbrella jira tracking the changes to protobuf upgrade. > > > >> > > >> > > > >> > > >>PR (https://github.com/apache/hadoop-thirdparty/pull/1) > has > > > >> been > > > >> > > >> raised > > > >> > > >> for separate repo creation in (HADOOP-16595 ( > > > >> > > >> https://issues.apache.org/jira/browse/HADOOP-16595) > > > >> > > >> > > > >> > > >>Please provide your inputs for the proposal and review the > > PR > > > >> to > > > >> > > >> proceed with the proposal. > > > >> > > >> > > > >> > > >> > > > >> > > >-Thanks, > > > >> > > >>Vinay > > > >> > > >> > > > >> > > >> On Fri, Sep 27, 2019 at 11:54 AM Vinod Kumar Vavilapalli < > > > >> > > >> vino...@apache.org> > > > >> > > >> wrote: > > > >> > > >> > > > >> > > >> > Moving the thread to the dev lists. > > > >> > > >> > > > > >> > > >> > Thanks > > > >> > > >> > +Vinod > > > >> > > >> > > > > >> > > >> > > On Sep 23, 2019, at 11:43 PM, Vinayakumar B < > > > >> > > vinayakum...@apache.org> > > > >> > > >> > wrote: > > > >> > > >> > > > > > >> > > >> > > Thanks Marton, > > > >> > > >> > > > > > >> > > >> > > Current created 'hadoop-thirdparty' repo is empty right > > now. > > > >> > > >> > > Whether to use that repo for shaded artifact or not will > > be > > > >> > > >> monitored in > > > >> > > >> > > HADOOP-13363 umbrella jira. Please feel free to join the > > > >> > discussion. > > > >> > > >> > > > > > >> > > >> > > There is no existing codebase is being moved out of > hadoop > > > >> repo. > > > >> > So > > > >> > > I > > > >> > > >> > think > > > >> > > >> > > right now we are good to go. > > > >> > > >> > > > > > >> > > >> > > -Vinay > > > >> > > >> > > > > > >> > > >> > > On Mon, Sep 23, 2019 at 11:38 PM Marton Elek < > > > e...@apache.org> > > > >> > > wrote: > > > >> > > >> > > > > > >> > > >> > >> > > > >> > > >> > >> I am not sure if it's defined when is a vote required. > > > >> > > >> > >> > > > >> > > >> > >> https://www.apache.org/foundation/voting.html > > > >> > > >> > >> > > > >> > > >> > >> Personally I think it's a big enough change to send a > > > >> > notification > > > >> > > to > > > >> > > >> > the > > > >> > > >> > >> dev lists with a 'lazy consensus' closure > > > >> > > >> > >> > > > >> > > >> > >> Marton > > > >> > > >> > >> > > > >> > > >> > >> On 2019/09/23 17:46:37, Vinayakumar B < > > > >> vinayakum...@apache.org> > > > >> > > >> wrote: > > > >> > > >> > >>> Hi, > > > >> > > >> > >>> > > > >> > > >> > >>> As discussed in HADOOP-13363, protobuf 3.x jar (and may > > be > > > >> more > > > >> > in > > > >> > > >> > >> future) > > > >> > > >> > >>> will be kept as a shaded artifact in a separate repo, > > which > > > >> will > > > >> > > be > > > >> > > >> > >>> referred as dependency in hadoop modules. This > approach > > > >> avoids > > > >> > > >> shading > > > >> > > >> > >> of > > > >> > > >> > >>> every submodule during build. > > > >> > > >> > >>> > > > >> > > >> > >>> So question is does any VOTE required before asking to > > > >> create a > > > >> > > git > > > >> > > >> > repo? > > > >> > > >> > >>> > > > >> > > >> > >>> On selfserve platform > > > >> > > https://gitbox.apache.org/setup/newrepo.html > > > >> > > >> > >>> I can access see that, requester should be PMC. > > > >> > > >> > >>> > > > >> > > >> > >>> Wanted to confirm here first. > > > >> > > >> > >>> > > > >> > > >> > >>> -Vinay > > > >> > > >> > >>> > > > >> > > >> > >> > > > >> > > >> > >> > > > >> > > > > > - > > > >> > > >> > >> To unsubscribe, e-mail: > > > private-unsubscr...@hadoop.apache.org > > > >> > > >> > >> For additional commands, e-mail: > > > >> private-h...@hadoop.apache.org > > > >> > > >> > >> > > > >> > > >> > >> > > > >> > > >> > > > > >> > > >> > > > > >> > > >> > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > > -- --Brahma Reddy Battula

Re: [DISCUSS] drop mapreduce-pipes

actually launched a > pipe job other than during testing. > > As such, it's a background noise maintenance problem and extra delays in > test runs. > > What do people think about deleting it? > > -Steve > -- --Brahma Reddy Battula

Re: [DISCUSS] Hadoop 2019 Release Planning

t; > > > > > > In addition, I saw community discussion to do a 2.8.6 release for > > > > security > > > > > fixes. > > > > > > > > > > Any other releases? I think there're release plans for Ozone as > well. > > > And > > > > > please add your thoughts. > > > > > > > > > > Volunteers welcome! If you have interests to run a release as > Release > > > > > Manager (or co-Resource Manager), please respond to this email > thread > > > so > > > > we > > > > > can coordinate. > > > > > > > > > > Thanks, > > > > > Wangda Tan > > > > > > > > > > [1] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = > Fixed > > > AND > > > > > fixVersion = 3.1.3 > > > > > [2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = > Fixed > > > AND > > > > > fixVersion = 3.2.1 > > > > > [3] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND resolution = > Fixed > > > AND > > > > > fixVersion = 3.3.0 > > > > > > > > > > > > > > > -- --Brahma Reddy Battula

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

t; classes, instead it will have original classes, resulting in > >> > compilation > >> > > >> failure. Workaround, build thirdparty submodule first and exclude > >> > > >> "thirdparty" submodule in other executions. This will be a > complex > >> > > process > >> > > >> compared to keeping in a separate repo. > >> > > >> > >> > > >> 7c. Separate repo, will be a subproject of Hadoop, using the > >> > same > >> > > >> HADOOP jira project, with different versioning prefixed with > >> > > "thirdparty-" > >> > > >> (ex: thirdparty-1.0.0). > >> > > >> 7d. Separate will have same release process as Hadoop. > >> > > >> > >> > > >>HADOOP-13363 ( > >> https://issues.apache.org/jira/browse/HADOOP-13363) > >> > > is > >> > > >> an > >> > > >> umbrella jira tracking the changes to protobuf upgrade. > >> > > >> > >> > > >>PR (https://github.com/apache/hadoop-thirdparty/pull/1) has > >> been > >> > > >> raised > >> > > >> for separate repo creation in (HADOOP-16595 ( > >> > > >> https://issues.apache.org/jira/browse/HADOOP-16595) > >> > > >> > >> > > >>Please provide your inputs for the proposal and review the PR > >> to > >> > > >> proceed with the proposal. > >> > > >> > >> > > >> > >> > > >-Thanks, > >> > > >>Vinay > >> > > >> > >> > > >> On Fri, Sep 27, 2019 at 11:54 AM Vinod Kumar Vavilapalli < > >> > > >> vino...@apache.org> > >> > > >> wrote: > >> > > >> > >> > > >> > Moving the thread to the dev lists. > >> > > >> > > >> > > >> > Thanks > >> > > >> > +Vinod > >> > > >> > > >> > > >> > > On Sep 23, 2019, at 11:43 PM, Vinayakumar B < > >> > > vinayakum...@apache.org> > >> > > >> > wrote: > >> > > >> > > > >> > > >> > > Thanks Marton, > >> > > >> > > > >> > > >> > > Current created 'hadoop-thirdparty' repo is empty right now. > >> > > >> > > Whether to use that repo for shaded artifact or not will be > >> > > >> monitored in > >> > > >> > > HADOOP-13363 umbrella jira. Please feel free to join the > >> > discussion. > >> > > >> > > > >> > > >> > > There is no existing codebase is being moved out of hadoop > >> repo. > >> > So > >> > > I > >> > > >> > think > >> > > >> > > right now we are good to go. > >> > > >> > > > >> > > >> > > -Vinay > >> > > >> > > > >> > > >> > > On Mon, Sep 23, 2019 at 11:38 PM Marton Elek < > e...@apache.org> > >> > > wrote: > >> > > >> > > > >> > > >> > >> > >> > > >> > >> I am not sure if it's defined when is a vote required. > >> > > >> > >> > >> > > >> > >> https://www.apache.org/foundation/voting.html > >> > > >> > >> > >> > > >> > >> Personally I think it's a big enough change to send a > >> > notification > >> > > to > >> > > >> > the > >> > > >> > >> dev lists with a 'lazy consensus' closure > >> > > >> > >> > >> > > >> > >> Marton > >> > > >> > >> > >> > > >> > >> On 2019/09/23 17:46:37, Vinayakumar B < > >> vinayakum...@apache.org> > >> > > >> wrote: > >> > > >> > >>> Hi, > >> > > >> > >>> > >> > > >> > >>> As discussed in HADOOP-13363, protobuf 3.x jar (and may be > >> more > >> > in > >> > > >> > >> future) > >> > > >> > >>> will be kept as a shaded artifact in a separate repo, which > >> will > >> > > be > >> > > >> > >>> referred as dependency in hadoop modules. This approach > >> avoids > >> > > >> shading > >> > > >> > >> of > >> > > >> > >>> every submodule during build. > >> > > >> > >>> > >> > > >> > >>> So question is does any VOTE required before asking to > >> create a > >> > > git > >> > > >> > repo? > >> > > >> > >>> > >> > > >> > >>> On selfserve platform > >> > > https://gitbox.apache.org/setup/newrepo.html > >> > > >> > >>> I can access see that, requester should be PMC. > >> > > >> > >>> > >> > > >> > >>> Wanted to confirm here first. > >> > > >> > >>> > >> > > >> > >>> -Vinay > >> > > >> > >>> > >> > > >> > >> > >> > > >> > >> > >> > > > - > >> > > >> > >> To unsubscribe, e-mail: > private-unsubscr...@hadoop.apache.org > >> > > >> > >> For additional commands, e-mail: > >> private-h...@hadoop.apache.org > >> > > >> > >> > >> > > >> > >> > >> > > >> > > >> > > >> > > >> > > >> > >> > > > > >> > > > >> > > >> > > -- --Brahma Reddy Battula

[jira] [Resolved] (HADOOP-16310) Log of a slow RPC request should contain the parameter of the request

[ https://issues.apache.org/jira/browse/HADOOP-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-16310. --- Resolution: Duplicate > Log of a slow RPC request should cont

RE: [VOTE] Moving Submarine to a separate Apache project proposal

+1, Thanks for Wangda's proposal. I am interested to participate in this project. Please include me -Original Message- From: Wanqiang Ji [mailto:wanqiang...@gmail.com] Sent: Wednesday, September 04, 2019 6:53 PM To: Wangda Tan Cc: submarine-dev ; yarn-dev ; Hdfs-dev ; mapreduce-dev

Re: [Notice] Merge HDFS-13891(RBF) to trunk

Merged. thanks to Arpit for quoting the merge process. From: Brahma Reddy Battula Sent: Tuesday, June 25, 2019 12:39 AM To: hdfs-...@hadoop.apache.org; common-dev@hadoop.apache.org Cc: Akira Ajisaka; Chittaranjan Hota; Giovanni Matteo Fumarola; Hadoop Common

[Notice] Merge HDFS-13891(RBF) to trunk

-Build/27044/console From: Brahma Reddy Battula Sent: Sunday, June 9, 2019 9:56 PM To: Xiaoqiao He Cc: Akira Ajisaka; Chittaranjan Hota; Giovanni Matteo Fumarola; Hadoop Common; Hdfs-dev; Iñigo Goiri Subject: Re: [VOTE] Merge HDFS-13891(RBF) to trunk Hi All

[RESULT][VOTE] Merge HDFS-13891(RBF) to trunk

gt; From: Xiaoqiao He > Sent: Monday, June 10, 2019 15:47 > To: Ranith Sardar > Cc: Brahma Reddy Battula; Hadoop Common; Hdfs-dev > Subject: Re: [VOTE] Merge HDFS-13891(RBF) to trunk > > +1 (non-binding) > > - Try to merge branch HDFS-13891(RBF) to trunk at local and no

Re: [DISCUSS] Merge HDFS-13891(RBF) to trunk

why ECBlockGroupStats is > modified. > > +0 apart from that. > > > On Jun 1, 2019, at 8:40 PM, Brahma Reddy Battula > wrote: > > Dear Hadoop Developers > > I would like to propose RBF Branch (HDFS-13891) merge into trunk. We have > been working on this feature from last sever

[VOTE] Merge HDFS-13891(RBF) to trunk

Updated mail... -- Forwarded message - From: Brahma Reddy Battula Date: Sun, Jun 9, 2019 at 7:26 PM Subject: Re: [VOTE] Merge HDFS-13891(RBF) to trunk To: Xiaoqiao He Cc: Akira Ajisaka , Chittaranjan Hota < chitts.h...@gmail.com>, Giovanni Matteo Fumarola < giova

Re: [VOTE] Merge HDFS-13891(RBF) to trunk

. 2. Added Security support for RBF 3. Added Missing Client Protocol API's 4. Bug Fixes/ Improvments The vote will run for 7 days, ending Sat June 15th. I will start this vote with my +1. Regards, Brahma Reddy Battula 1). https://lists.apache.org/thread.html

[DISCUSS] Merge HDFS-13891(RBF) to trunk

and contiue to work. Reference: 1) https://issues.apache.org/jira/browse/HDFS-13532 2) https://issues.apache.org/jira/browse/HDFS-13655 --Brahma Reddy Battula

[RESULT][VOTE] Unprotect HDFS-13891 (HDFS RBF Branch)

Here is my +1 too. Thanks to everyone that participated. The vote to “unprotect the HDFS-13891 branch” is now closed. It PASSED with 4(+1 binding) votes and no 0 or -1 votes: Binding Votes: === Íñigo Goiri Akira Ajisaka Anu Engineer Brahma Reddy Battula Non Binding votes

Re: [VOTE] Unprotect HDFS-13891 (HDFS RBF Branch)

gt; > > > On Tue, May 14, 2019 at 4:58 AM Takanobu Asanuma > > > wrote: > > > >> +1. > >> > >> Thanks! > >> - Takanobu > >> > >> ____________ > >> From: Akira Ajisaka > >>

[VOTE] Unprotect HDFS-13891 (HDFS RBF Branch)

as this is blocking all branch commits?? -- --Brahma Reddy Battula

Re: [ANNOUNCE] Eric Badger is now a committer!

Congratulations Eric!!! On Tue, Mar 5, 2019 at 10:50 PM, Eric Payne wrote: > It is my pleasure to announce that Eric Badger has accepted an invitation > to become a Hadoop Core committer. > > Congratulations, Eric! This is well-deserved! > > -Eric Payne > -- --Brahma Reddy Battula

Re: [VOTE] Release Apache Hadoop 3.2.0 - RC1

t; [2] project in (YARN, HADOOP, MAPREDUCE, HDFS) AND fixVersion in (3.2.0) > AND fixVersion not in (3.1.0, 3.0.0, 3.0.0-beta1) AND status = Resolved > ORDER BY fixVersion ASC > -- --Brahma Reddy Battula

RE: [Result] [VOTE - 2] Merge HDFS-12943 branch to trunk - Consistent Reads from Standby

My late +1. Really it's useful feature.. Great work. -Original Message- From: Konstantin Shvachko [mailto:shv.had...@gmail.com] Sent: Saturday, December 22, 2018 6:48 AM To: Hadoop Common ; hdfs-dev Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: [Result] [VOTE

Re: [DISCUSS] Move to gitbox

the repository will be migrated by > February 7th. > > Regards, > Akira > > - > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > -- --Brahma Reddy Battula

RE: [VOTE] Release Apache Hadoop 2.9.2 (RC0)

Akira, Thanks for driving this release. +1 (binding) -- Built from source -- Installed HA cluster --Verified basic operations --Ran Sample Jobs --Browsed the UI -Brahma Reddy Battula -Original Message- From: Akira Ajisaka [mailto:aajis...@apache.org] Sent: Wednesday, November 14

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

+1 It’s better to new version link in old version. Brahma Reddy Battula On Fri, Aug 31, 2018 at 9:59 PM, Sangjin Lee wrote: > +1. Thanks for the work, Marton! > > On Fri, Aug 31, 2018 at 8:37 AM Vinod Kumar Vavilapalli < > vino...@apache.org> > wrote: > > > I

Re: [VOTE] Release Apache Hadoop 3.1.1 - RC0

+1 ,(binding). Wangda Tan thanks for driving this. --Built with source. --Installed the HA cluster --Ran basic hdfs operations through shell/API --Ran Sample jobs like pi, wordcount --Browsed UI. On Fri, Aug 3, 2018 at 12:14 AM Wangda Tan wrote: > Hi folks, > > I've created RC0 for Apache

RE: [VOTE] Release Apache Hadoop 2.8.4 (RC0)

Thanks Junping for driving this release. +1 (binding) -- Build successfully from the source code -- Start HA cluster -- Verified basic shell operations -- Ran pi,wordcount -- Browsed the NN and RM UI -Brahma Reddy Battula -Original Message- From: 俊平堵 [mailto:junping

RE: Apache Hadoop 3.1.1 release plan

Thanks Wangda Tan for driving the 3.1.1 release.Yes,This can be better addition to 3.1 line release for improving quality. Looks only following two are pending which are in review state. Hope you are monitoring these two. https://issues.apache.org/jira/browse/YARN-8265

RE: [VOTE] Release Apache Hadoop 2.7.6 (RC0)

Konstantin thanks for driving this. +1 (binding) --Built from the source --Installed HA cluster -Verified the basic shell commands -Ran sample jobs like pi,wordcount -Browsed the UI's -Original Message- From: Konstantin Shvachko [mailto:shv.had...@gmail.com] Sent: 10 April 2018

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

Wangda thanks for driving this. +1(binding) --Built from source --Installed HA cluster --Verified Basic Shell commands --Ran Sample Jobs --Browsed the UI's. On Fri, Mar 30, 2018 at 9:45 AM, Wangda Tan wrote: > Hi folks, > > Thanks to the many who helped with this release

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

Thanks Lei Xu for driving this. +1(binding) --Built from the source --Installed the HA Cluster --Verified hdfs operations --Ran sample jobs --Verified the UI's --Brahma Reddy Battula -Original Message- From: Lei Xu [mailto:l...@apache.org] Sent: 18 March 2018 12:11 To: Hadoop

  1   2   3   >