[jira] [Created] (HDDS-1875) Fix failures in TestS3MultipartUploadAbortResponse

2019-07-30 Thread Bharat Viswanadham (JIRA)
Bharat Viswanadham created HDDS-1875: Summary: Fix failures in TestS3MultipartUploadAbortResponse Key: HDDS-1875 URL: https://issues.apache.org/jira/browse/HDDS-1875 Project: Hadoop Distributed

[jira] [Resolved] (HDDS-152) Support HA for Ozone Manager

2019-07-30 Thread Arpit Agarwal (JIRA)
[ https://issues.apache.org/jira/browse/HDDS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal resolved HDDS-152. Resolution: Duplicate > Support HA for Ozone Manager > > >

[jira] [Reopened] (HDDS-152) Support HA for Ozone Manager

2019-07-30 Thread Arpit Agarwal (JIRA)
[ https://issues.apache.org/jira/browse/HDDS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal reopened HDDS-152: > Support HA for Ozone Manager > > > Key: HDDS-152 >

[jira] [Resolved] (HDDS-151) Add HA support for Ozone

2019-07-30 Thread Arpit Agarwal (JIRA)
[ https://issues.apache.org/jira/browse/HDDS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal resolved HDDS-151. Resolution: Duplicate Resolving as a duplicate of HDDS-505. This was filed first, however OM HA

[jira] [Resolved] (HDFS-14542) Remove redundant code when verify quota

2019-07-30 Thread Jinglun (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinglun resolved HDFS-14542. Resolution: Duplicate Thanks [~jojochuang] for your reminding, I'll close this with Resolution:

[jira] [Reopened] (HDFS-14631) The DirectoryScanner doesn't fix the wrongly placed replica.

2019-07-30 Thread Jinglun (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinglun reopened HDFS-14631: > The DirectoryScanner doesn't fix the wrongly placed replica. >

[jira] [Reopened] (HDFS-8708) DFSClient should ignore dfs.client.retry.policy.enabled for HA proxies

2019-07-30 Thread Chengbing Liu (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-8708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengbing Liu reopened HDFS-8708: - I have different opinion so I'm reopening this issue. In our production environment, we have both HA

[jira] [Created] (HDDS-1874) Describe how ozoneManagerDoubleBuffer works in ascii art in code

2019-07-30 Thread Bharat Viswanadham (JIRA)
Bharat Viswanadham created HDDS-1874: Summary: Describe how ozoneManagerDoubleBuffer works in ascii art in code Key: HDDS-1874 URL: https://issues.apache.org/jira/browse/HDDS-1874 Project: Hadoop

[jira] [Resolved] (HDFS-14496) Backport HDFS-13056 into branch-2.8/2.9/2

2019-07-30 Thread Wei-Chiu Chuang (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-14496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HDFS-14496. Resolution: Duplicate > Backport HDFS-13056 into branch-2.8/2.9/2 >

[jira] [Resolved] (HDFS-14641) Possible Intermediate Block Report Race Condition

2019-07-30 Thread Wei-Chiu Chuang (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-14641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HDFS-14641. Resolution: Invalid [~belugabehr] I think this is the expected behavior. COMITTED means

[jira] [Resolved] (HDFS-10927) Lease Recovery: File not getting closed on HDFS when block write operation fails

2019-07-30 Thread Wei-Chiu Chuang (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HDFS-10927. Resolution: Duplicate Resolve as adup. Thanks everyone for chiming in! > Lease Recovery:

[jira] [Created] (HDFS-14682) TestStateStoreFileSystem failed because /tmp/hadoop/dfs/name/current can't be removed

2019-07-30 Thread Wei-Chiu Chuang (JIRA)
Wei-Chiu Chuang created HDFS-14682: -- Summary: TestStateStoreFileSystem failed because /tmp/hadoop/dfs/name/current can't be removed Key: HDFS-14682 URL: https://issues.apache.org/jira/browse/HDFS-14682

[jira] [Created] (HDFS-14681) TestDisableRouterQuota failed because port 8888 was occupied

2019-07-30 Thread Wei-Chiu Chuang (JIRA)
Wei-Chiu Chuang created HDFS-14681: -- Summary: TestDisableRouterQuota failed because port was occupied Key: HDFS-14681 URL: https://issues.apache.org/jira/browse/HDFS-14681 Project: Hadoop HDFS

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2019-07-30 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1213/ [Jul 29, 2019 8:27:55 AM] (elek) HDDS-1867. Invalid Prometheus metric name from JvmMetrics [Jul 29, 2019 8:46:11 AM] (elek) HDDS-1852. Fix typo in TestOmAcls [Jul 29, 2019 9:04:45 AM] (elek) HDDS-1682.

Re: [DISCUSS] EOL 2.8 or another 2.8.x release?

2019-07-30 Thread 俊平堵
+1 for 1 more release in 2.8.x. However, it sounds too early to declare 2.8 is EoL. I would prefer to discuss this after seeing most people are migrated to 2.9 or 3.x. Thanks, Junping Akira Ajisaka 于2019年7月26日周五 下午12:03写道: > I'm +1 for 1 more release in 2.8.x and declare that 2.8 is EoL. > >

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

2019-07-30 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/398/ [Jul 29, 2019 9:34:31 PM] (weichiu) HDFS-14429. Block remain in COMMITTED but not COMPLETE caused by [Jul 29, 2019 9:36:57 PM] (xkrogen) HDFS-12703. Exceptions are fatal to decommissioning monitor.

[jira] [Created] (HDFS-14680) StorageInfoDefragmenter should handle exceptions more gently

2019-07-30 Thread Chen Zhang (JIRA)
Chen Zhang created HDFS-14680: - Summary: StorageInfoDefragmenter should handle exceptions more gently Key: HDFS-14680 URL: https://issues.apache.org/jira/browse/HDFS-14680 Project: Hadoop HDFS

Re: Any thoughts making Submarine a separate Apache project?

2019-07-30 Thread 俊平堵
Thanks Vinod for these great suggestions. I agree most of your comments above. "For the Apache Hadoop community, this will be treated simply as code-change and so need a committer +1?". IIUC, this should be treated as feature branch merge, so may be 3 committer +1 is needed here according to