Re: [DISCUSS] A unified and open Hadoop community sync up schedule?
Thanks @Wei-Chiu Chuang . updated gdoc On Tue, Jun 18, 2019 at 7:35 PM Wei-Chiu Chuang wrote: > Thanks Wangda, > > I just like to make a correction -- the .ics calendar file says the first > Wednesday for HDFS/cloud connector is in Mandarin whereas on the gdoc is to > host it on the third Wednesday. > > On Tue, Jun 18, 2019 at 5:29 PM Wangda Tan wrote: > > > Hi Folks, > > > > I just updated doc: > > > > > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > > with > > dial-in information, notes, etc. > > > > Here's a calendar to subscribe: > > > > > https://calendar.google.com/calendar/ical/hadoop.community.sync.up%40gmail.com/public/basic.ics > > > > I'm thinking to give it a try from next week, any suggestions? > > > > Thanks, > > Wangda > > > > On Fri, Jun 14, 2019 at 4:02 PM Wangda Tan wrote: > > > > > And please let me know if you can help with coordinate logistics stuff, > > > cross-checking, etc. Let's spend some time next week to get it > finalized. > > > > > > Thanks, > > > Wangda > > > > > > On Fri, Jun 14, 2019 at 4:00 PM Wangda Tan > wrote: > > > > > >> Hi Folks, > > >> > > >> Yufei: Agree with all your opinions. > > >> > > >> Anu: it might be more efficient to use Google doc to track meeting > > >> minutes and we can put them together. > > >> > > >> I just put the proposal to > > >> > > > https://calendar.google.com/calendar/b/3?cid=aGFkb29wLmNvbW11bml0eS5zeW5jLnVwQGdtYWlsLmNvbQ > > , > > >> you can check if the proposal time works or not. If you agree, we can > go > > >> ahead to add meeting link, google doc, etc. > > >> > > >> If you want to have edit permissions, please drop a private email to > me > > >> so I will add you. > > >> > > >> We still need more hosts, in each track, ideally we should have at > least > > >> 3 hosts per track just like HDFS blocks :), please volunteer, so we > can > > >> have enough members to run the meeting. > > >> > > >> Let's shoot by end of the next week, let's get all logistics done and > > >> starting community sync up series from the week of Jun 25th. > > >> > > >> Thanks, > > >> Wangda > > >> > > >> Thanks, > > >> Wangda > > >> > > >> > > >> > > >> On Tue, Jun 11, 2019 at 10:23 AM Anu Engineer > > > >> wrote: > > >> > > >>> 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/confluence/display/HADOOP/2019-06-10+Meeting+notes > > >>> > > >>> --Anu > > >>> > > >>> On Tue, Jun 11, 2019 at 10:20 AM Yufei Gu > > wrote: > > >>> > > +1 for this idea. Thanks Wangda for bringing this up. > > > > Some comments to share: > > > > - Agenda needed to be posted ahead of meeting and welcome any > > interested > > party to contribute to topics. > > - We should encourage more people to attend. That's whole point > of > > the > > meeting. > > - Hopefully, this can mitigate the situation that some patches > are > > waiting for review for ever, which turns away new contributors. > > - 30m per session sounds a little bit short, we can try it out > and > > see > > if extension is needed. > > > > Best, > > > > Yufei > > > > `This is not a contribution` > > > > > > On Fri, Jun 7, 2019 at 4:39 PM Wangda Tan > > wrote: > > > > > Hi Hadoop-devs, > > > > > > Previous we have regular YARN community sync up (1 hr, biweekly, > but > > not > > > open to public). Recently because of changes in our schedules, > Less > > folks > > > showed up in the sync up for the last several months. > > > > > > I saw the K8s community did a pretty good job to run their sig > > meetings, > > > there's regular meetings for different topics, notes, agenda, etc. > > Such as > > > > > > > > > > > https://docs.google.com/document/d/13mwye7nvrmV11q9_Eg77z-1w3X7Q1GTbslpml4J7F3A/edit > > > > > > > > > For Hadoop community, there are less such regular meetings open to > > the > > > public except for Ozone project and offline meetups or > > Bird-of-Features in > > > Hadoop/DataWorks Summit. Recently we have a few folks joined > > DataWorks > > > Summit at Washington DC and Barcelona, and lots (50+) of folks > join > > the > > > Ozone/Hadoop/YARN BoF, ask (good) questions and roadmaps. I think > it > > is > > > important to open such conversations to the public and let more > > > folk/companies join. > > > > > > Discussed a small group of community members and wrote a short > > proposal > > > about the form, time and topic of the community sync up, thanks > for > > >
[jira] [Created] (HADOOP-16381) The JSON License is included in binary tarball via azure-documentdb:1.16.2
Akira Ajisaka created HADOOP-16381:
--
Summary: The JSON License is included in binary tarball via
azure-documentdb:1.16.2
Key: HADOOP-16381
URL: https://issues.apache.org/jira/browse/HADOOP-16381
Project: Hadoop Common
Issue Type: Bug
Reporter: Akira Ajisaka
{noformat}
$ mvn dependency:tree
(snip)
[INFO] +- com.microsoft.azure:azure-documentdb:jar:1.16.2:compile
[INFO] | +- com.fasterxml.uuid:java-uuid-generator:jar:3.1.4:compile
[INFO] | +- org.json:json:jar:20140107:compile
[INFO] | +- org.apache.httpcomponents:httpcore:jar:4.4.10:compile
[INFO] | \- joda-time:joda-time:jar:2.9.9:compile
{noformat}
org.json:json is JSON Licensed and it must be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Re: [DISCUSS] A unified and open Hadoop community sync up schedule?
Thanks Wangda, I just like to make a correction -- the .ics calendar file says the first Wednesday for HDFS/cloud connector is in Mandarin whereas on the gdoc is to host it on the third Wednesday. On Tue, Jun 18, 2019 at 5:29 PM Wangda Tan wrote: > Hi Folks, > > I just updated doc: > > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > with > dial-in information, notes, etc. > > Here's a calendar to subscribe: > > https://calendar.google.com/calendar/ical/hadoop.community.sync.up%40gmail.com/public/basic.ics > > I'm thinking to give it a try from next week, any suggestions? > > Thanks, > Wangda > > On Fri, Jun 14, 2019 at 4:02 PM Wangda Tan wrote: > > > And please let me know if you can help with coordinate logistics stuff, > > cross-checking, etc. Let's spend some time next week to get it finalized. > > > > Thanks, > > Wangda > > > > On Fri, Jun 14, 2019 at 4:00 PM Wangda Tan wrote: > > > >> Hi Folks, > >> > >> Yufei: Agree with all your opinions. > >> > >> Anu: it might be more efficient to use Google doc to track meeting > >> minutes and we can put them together. > >> > >> I just put the proposal to > >> > https://calendar.google.com/calendar/b/3?cid=aGFkb29wLmNvbW11bml0eS5zeW5jLnVwQGdtYWlsLmNvbQ > , > >> you can check if the proposal time works or not. If you agree, we can go > >> ahead to add meeting link, google doc, etc. > >> > >> If you want to have edit permissions, please drop a private email to me > >> so I will add you. > >> > >> We still need more hosts, in each track, ideally we should have at least > >> 3 hosts per track just like HDFS blocks :), please volunteer, so we can > >> have enough members to run the meeting. > >> > >> Let's shoot by end of the next week, let's get all logistics done and > >> starting community sync up series from the week of Jun 25th. > >> > >> Thanks, > >> Wangda > >> > >> Thanks, > >> Wangda > >> > >> > >> > >> On Tue, Jun 11, 2019 at 10:23 AM Anu Engineer > >> wrote: > >> > >>> 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/confluence/display/HADOOP/2019-06-10+Meeting+notes > >>> > >>> --Anu > >>> > >>> On Tue, Jun 11, 2019 at 10:20 AM Yufei Gu > wrote: > >>> > +1 for this idea. Thanks Wangda for bringing this up. > > Some comments to share: > > - Agenda needed to be posted ahead of meeting and welcome any > interested > party to contribute to topics. > - We should encourage more people to attend. That's whole point of > the > meeting. > - Hopefully, this can mitigate the situation that some patches are > waiting for review for ever, which turns away new contributors. > - 30m per session sounds a little bit short, we can try it out and > see > if extension is needed. > > Best, > > Yufei > > `This is not a contribution` > > > On Fri, Jun 7, 2019 at 4:39 PM Wangda Tan > wrote: > > > Hi Hadoop-devs, > > > > Previous we have regular YARN community sync up (1 hr, biweekly, but > not > > open to public). Recently because of changes in our schedules, Less > folks > > showed up in the sync up for the last several months. > > > > I saw the K8s community did a pretty good job to run their sig > meetings, > > there's regular meetings for different topics, notes, agenda, etc. > Such as > > > > > > https://docs.google.com/document/d/13mwye7nvrmV11q9_Eg77z-1w3X7Q1GTbslpml4J7F3A/edit > > > > > > For Hadoop community, there are less such regular meetings open to > the > > public except for Ozone project and offline meetups or > Bird-of-Features in > > Hadoop/DataWorks Summit. Recently we have a few folks joined > DataWorks > > Summit at Washington DC and Barcelona, and lots (50+) of folks join > the > > Ozone/Hadoop/YARN BoF, ask (good) questions and roadmaps. I think it > is > > important to open such conversations to the public and let more > > folk/companies join. > > > > Discussed a small group of community members and wrote a short > proposal > > about the form, time and topic of the community sync up, thanks for > > everybody who have contributed to the proposal! Please feel free to > add > > your thoughts to the Proposal Google doc > > < > > > > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > > > > > . > > > > Especially for the following parts: > > - If you have interests to run any of the community sync-ups, please > put > > your name
Re: [DISCUSS] A unified and open Hadoop community sync up schedule?
Hi Folks, I just updated doc: https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# with dial-in information, notes, etc. Here's a calendar to subscribe: https://calendar.google.com/calendar/ical/hadoop.community.sync.up%40gmail.com/public/basic.ics I'm thinking to give it a try from next week, any suggestions? Thanks, Wangda On Fri, Jun 14, 2019 at 4:02 PM Wangda Tan wrote: > And please let me know if you can help with coordinate logistics stuff, > cross-checking, etc. Let's spend some time next week to get it finalized. > > Thanks, > Wangda > > On Fri, Jun 14, 2019 at 4:00 PM Wangda Tan wrote: > >> Hi Folks, >> >> Yufei: Agree with all your opinions. >> >> Anu: it might be more efficient to use Google doc to track meeting >> minutes and we can put them together. >> >> I just put the proposal to >> https://calendar.google.com/calendar/b/3?cid=aGFkb29wLmNvbW11bml0eS5zeW5jLnVwQGdtYWlsLmNvbQ, >> you can check if the proposal time works or not. If you agree, we can go >> ahead to add meeting link, google doc, etc. >> >> If you want to have edit permissions, please drop a private email to me >> so I will add you. >> >> We still need more hosts, in each track, ideally we should have at least >> 3 hosts per track just like HDFS blocks :), please volunteer, so we can >> have enough members to run the meeting. >> >> Let's shoot by end of the next week, let's get all logistics done and >> starting community sync up series from the week of Jun 25th. >> >> Thanks, >> Wangda >> >> Thanks, >> Wangda >> >> >> >> On Tue, Jun 11, 2019 at 10:23 AM Anu Engineer >> wrote: >> >>> 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/confluence/display/HADOOP/2019-06-10+Meeting+notes >>> >>> --Anu >>> >>> On Tue, Jun 11, 2019 at 10:20 AM Yufei Gu wrote: >>> +1 for this idea. Thanks Wangda for bringing this up. Some comments to share: - Agenda needed to be posted ahead of meeting and welcome any interested party to contribute to topics. - We should encourage more people to attend. That's whole point of the meeting. - Hopefully, this can mitigate the situation that some patches are waiting for review for ever, which turns away new contributors. - 30m per session sounds a little bit short, we can try it out and see if extension is needed. Best, Yufei `This is not a contribution` On Fri, Jun 7, 2019 at 4:39 PM Wangda Tan wrote: > Hi Hadoop-devs, > > Previous we have regular YARN community sync up (1 hr, biweekly, but not > open to public). Recently because of changes in our schedules, Less folks > showed up in the sync up for the last several months. > > I saw the K8s community did a pretty good job to run their sig meetings, > there's regular meetings for different topics, notes, agenda, etc. Such as > > https://docs.google.com/document/d/13mwye7nvrmV11q9_Eg77z-1w3X7Q1GTbslpml4J7F3A/edit > > > For Hadoop community, there are less such regular meetings open to the > public except for Ozone project and offline meetups or Bird-of-Features in > Hadoop/DataWorks Summit. Recently we have a few folks joined DataWorks > Summit at Washington DC and Barcelona, and lots (50+) of folks join the > Ozone/Hadoop/YARN BoF, ask (good) questions and roadmaps. I think it is > important to open such conversations to the public and let more > folk/companies join. > > Discussed a small group of community members and wrote a short proposal > about the form, time and topic of the community sync up, thanks for > everybody who have contributed to the proposal! Please feel free to add > your thoughts to the Proposal Google doc > < > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > > > . > > Especially for the following parts: > - If you have interests to run any of the community sync-ups, please put > your name to the table inside the proposal. We need more volunteers to help > run the sync-ups in different timezones. > - Please add suggestions to the time, frequency and themes and feel free to > share your thoughts if we should do sync ups for other topics which are not > covered by the proposal. > > Link to the Proposal Google doc > < > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > > > > Thanks, > Wangda Tan > >>>
Re: [ANNOUNCE] Aaron Fabbri as Hadoop PMC
Thank you everybody. Appreciate it. On Mon, Jun 17, 2019 at 8:43 PM Sree V wrote: > Congratulations, Aaron. > > > > Thank you./Sree > > > > On Monday, June 17, 2019, 7:31:47 PM PDT, Dinesh Chitlangia < > dchitlan...@cloudera.com.INVALID> wrote: > > Congratulations Aaron! > > -Dinesh > > > On Mon, Jun 17, 2019 at 9:29 PM Wanqiang Ji wrote: > > > Congratulations! > > > > On Tue, Jun 18, 2019 at 8:29 AM Da Zhou wrote: > > > > > Congratulations! > > > > > > Regards, > > > Da > > > > > > On Mon, Jun 17, 2019 at 5:14 PM Ajay Kumar > > .invalid> > > > wrote: > > > > > > > Congrats Aaron!! > > > > > > > > On Mon, Jun 17, 2019 at 4:00 PM Daniel Templeton > > > > wrote: > > > > > > > > > I am very pleased to announce that Aaron Fabbri has now been added > to > > > > > the Hadoop PMC. Welcome aboard, Aaron, and Congratulations! > > > > > > > > > > Daniel > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > > > > > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > > > > > > > > > > > > > > > > > > > >
Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/ [Jun 17, 2019 2:22:01 PM] (weichiu) HDFS-14535. The default 8KB buffer in [Jun 18, 2019 12:04:38 AM] (weichiu) HDFS-11950. Disable libhdfs zerocopy test on Mac. Contributed by Akira -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: XML : Parsing Error(s): hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/empty-configuration.xml hadoop-tools/hadoop-azure/src/config/checkstyle-suppressions.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/public/crossdomain.xml hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml FindBugs : module:hadoop-common-project/hadoop-common Class org.apache.hadoop.fs.GlobalStorageStatistics defines non-transient non-serializable instance field map In GlobalStorageStatistics.java:instance field map In GlobalStorageStatistics.java FindBugs : module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice-hbase/hadoop-yarn-server-timelineservice-hbase-client Boxed value is unboxed and then immediately reboxed in org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result, byte[], byte[], KeyConverter, ValueConverter, boolean) At ColumnRWHelper.java:then immediately reboxed in org.apache.hadoop.yarn.server.timelineservice.storage.common.ColumnRWHelper.readResultsWithTimestamps(Result, byte[], byte[], KeyConverter, ValueConverter, boolean) At ColumnRWHelper.java:[line 335] Failed junit tests : hadoop.contrib.bkjournal.TestBookKeeperJournalManager hadoop.hdfs.qjournal.server.TestJournalNodeRespectsBindHostKeys hadoop.hdfs.web.TestWebHdfsTimeouts hadoop.contrib.bkjournal.TestBookKeeperJournalManager hadoop.yarn.sls.TestSLSRunner hadoop.yarn.client.api.impl.TestAMRMProxy hadoop.registry.secure.TestSecureLogins hadoop.yarn.server.nodemanager.containermanager.TestContainerManager hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2 cc: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-compile-cc-root-jdk1.7.0_95.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-compile-javac-root-jdk1.7.0_95.txt [328K] cc: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-compile-cc-root-jdk1.8.0_212.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-compile-javac-root-jdk1.8.0_212.txt [308K] checkstyle: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-checkstyle-root.txt [16M] hadolint: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-patch-hadolint.txt [4.0K] pathlen: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/pathlen.txt [12K] pylint: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-patch-pylint.txt [24K] shellcheck: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-patch-shellcheck.txt [72K] shelldocs: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-patch-shelldocs.txt [8.0K] whitespace: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/whitespace-eol.txt [12M] https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/whitespace-tabs.txt [1.2M] xml: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/xml.txt [12K] findbugs: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/branch-findbugs-hadoop-common-project_hadoop-common-warnings.html [8.0K] https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/branch-findbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice-hbase_hadoop-yarn-server-timelineservice-hbase-client-warnings.html [8.0K] javadoc: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/356/artifact/out/diff-javadoc-javadoc-root-jdk1.7.0_95.txt [16K]
[jira] [Resolved] (HADOOP-16184) S3Guard: Handle OOB deletions and creation of a file which has a tombstone marker
[
https://issues.apache.org/jira/browse/HADOOP-16184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16184.
-
Resolution: Fixed
> S3Guard: Handle OOB deletions and creation of a file which has a tombstone
> marker
> -
>
> Key: HADOOP-16184
> URL: https://issues.apache.org/jira/browse/HADOOP-16184
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 3.1.0
>Reporter: Gabor Bota
>Assignee: Gabor Bota
>Priority: Major
>
> When a file is deleted in S3 using S3Guard a tombstone marker will be added
> for that file in the MetadataStore. If another process creates the file
> without using S3Guard (as an out of band operation - OOB) the file still not
> be visible for the client using S3Guard because of the deletion tombstone.
>
> The whole of S3Guard is potentially brittle to
> * OOB deletions: we skip it in HADOOP-15999, so no worse, but because the
> S3AInputStream retries on FNFE, so as to "debounce" cached 404s, it's
> potentially going to retry forever.
> * OOB creation of a file which has a deletion tombstone marker.
> The things this issue covers:
> * Write a test to simulate that deletion problem, to see what happens. We
> ought to have the S3AInputStream retry briefly on that initial GET failing,
> but only on that initial one. (after setting "fs.s3a.retry.limit" to
> something low & the interval down to 10ms or so to fail fast)
> * Sequences
> {noformat}
> 1. create; delete; open; read -> fail after retry
> 2. create; open, read, delete, read -> fail fast on the second read
> {noformat}
> The StoreStatistics of the filesystem's IGNORED_ERRORS stat will be increased
> on the ignored error, so on sequence 1 will have increased, whereas on
> sequence 2 it will not have. If either of these tests don't quite fail as
> expected, we can disable the tests and continue, at least now with some tests
> to simulate a condition we don't have a fix for.
> * For both, we just need to have some model of how long it takes for
> debouncing to stabilize. Then in this new check, if an FNFE is raised and the
> check is happening > (modtime+ debounce-delay) then it's a real FNFE.
> This issue is created based on [~ste...@apache.org] remarks and comments on
> HADOOP-15999.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-16380) ITestS3AContractRootDir failing on trunk
Steve Loughran created HADOOP-16380:
---
Summary: ITestS3AContractRootDir failing on trunk
Key: HADOOP-16380
URL: https://issues.apache.org/jira/browse/HADOOP-16380
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/s3, test
Affects Versions: 3.3.0
Reporter: Steve Loughran
Assignee: Steve Loughran
I'm seeing reproducible failures of {{ITestS3AContractRootDir}} which look like
consistency problems *even when S3Guard is enabled*.
Suspicion: root dir listings are still inconsistent, due to the way we don't
keep root entries in the table
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Proposal to make Hadoop more compatible with AArch64 platforms
Hi Hadoop, Some of you might see the related proposal in JIRA( https://issues.apache.org/jira/browse/HADOOP-16358) already, but I want to raise it to a wider audience and clarify some potential misunderstandings. I’m from OpenLab team(https://openlabtesting.org/ ,a community to do open source project testing, this is OpenLab charter: https://github.com/theopenlab/governance/blob/master/CHARTER.md). One of our goal is to make more opensource software to be more compatible for AArch64 platforms. And since Hadoop is the most important one in BigData area, we would like to propose to work on AArch64 related works in Hadoop. Even though OpenLab is a community to do open source project testing, using OpenLab for testing AArch64 related works is not mandatory, what we really want to do is to help build the AArch64 eco system in BigData area. We have a developer team that willing to work on this and we also have some AArch64 resources that we are willing to provide for Hadoop community to connect to the current CI system to perform related testings. Rome wasn't built in a day, so we plan to start a simple target to add AArch64 build job for Hadoop, to verify Hadoop and its subprojects can be compiled on AArch64 successfully, OpenLab's developers will maintain build CI jobs and address the CI issues, then we can add more complex test cases on AArch64, like: unit tests and functional tests, step by step, it's a long term works. Of course, welcome another developers join to maintain the AArch64 CI. Thanks for your attention.
