[jira] [Resolved] (HDDS-1486) Ozone write fails in allocateBlock while writing >10MB files in multiple threads.

[ https://issues.apache.org/jira/browse/HDDS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved HDDS-1486. - Resolution: Cannot Reproduce > Ozone write fails in allocateBlock while writing >10MB

[jira] [Reopened] (HDDS-1486) Ozone write fails in allocateBlock while writing >10MB files in multiple threads.

[ https://issues.apache.org/jira/browse/HDDS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reopened HDDS-1486: - > Ozone write fails in allocateBlock while writing >10MB files in multiple > threads. >

[jira] [Resolved] (HDDS-1486) Ozone write fails in allocateBlock while writing >10MB files in multiple threads.

[ https://issues.apache.org/jira/browse/HDDS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved HDDS-1486. - Resolution: Won't Fix [~msingh] Not seeing this in recent runs. I will reopen if I see

[jira] [Resolved] (HDFS-14636) SBN : If you configure the default proxy provider still read Request going to Observer namenode only.

[ https://issues.apache.org/jira/browse/HDFS-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshakiran Reddy resolved HDFS-14636. -- Resolution: Duplicate Resolved as Duplicate, HDFS-14660 has further discussion on

[jira] [Created] (HDDS-1846) Default value for checksum bytes is different in ozone-site.xml and code

Bharat Viswanadham created HDDS-1846: Summary: Default value for checksum bytes is different in ozone-site.xml and code Key: HDDS-1846 URL: https://issues.apache.org/jira/browse/HDDS-1846

[jira] [Resolved] (HDDS-1799) Add goofyfs to the ozone-runner docker image

[ https://issues.apache.org/jira/browse/HDDS-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anu Engineer resolved HDDS-1799. Resolution: Fixed Fix Version/s: 0.4.1 0.5.0 I have committed this patch

[jira] [Resolved] (HDDS-1585) Add LICENSE.txt and NOTICE.txt to Ozone Recon Web

[ https://issues.apache.org/jira/browse/HDDS-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anu Engineer resolved HDDS-1585. Resolution: Fixed Fix Version/s: 0.4.1 0.5.0 [~vivekratnavel] Thank you

[jira] [Created] (HDDS-1845) OMVolumeSetQuotaRequest#validateAndUpdateCache should not return OMVolumeCreateResponse

Xiaoyu Yao created HDDS-1845: Summary: OMVolumeSetQuotaRequest#validateAndUpdateCache should not return OMVolumeCreateResponse Key: HDDS-1845 URL: https://issues.apache.org/jira/browse/HDDS-1845 Project:

Re: [DISCUSS] Prefer Github PR Integration over patch in JIRA

Where would JIRA fit into the PR workflow? Would we file JIRAs just to track github PRs and have all of the discussion on the PR? Eric On Mon, Jul 22, 2019 at 1:10 PM Dinesh Chitlangia wrote: > +1 Absolutely. It also makes it easy/clean for reviewers to leave specific > comments and the

Re: [DISCUSS] Prefer Github PR Integration over patch in JIRA

+1 Absolutely. It also makes it easy/clean for reviewers to leave specific comments and the authors can make incremental changes without the hassles of generating iterative patch files. Thanks, Dinesh On Mon, Jul 22, 2019 at 2:06 PM Wei-Chiu Chuang wrote: > Historically, Hadoop developers

[DISCUSS] Prefer Github PR Integration over patch in JIRA

Historically, Hadoop developers create patches and attache them to JIRA, andthen the Yetus bot runs precommit against the patch in the JIRA. The Github PR is more convenient for code review and less hassle for committers to merge a commit. I am proposing for the community to prefer Github PR over

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1205/ No changes -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

[jira] [Created] (HDDS-1844) Tune the stateMachineDataCache to a reasonable fraction of Datanode Heap

Shashikant Banerjee created HDDS-1844: - Summary: Tune the stateMachineDataCache to a reasonable fraction of Datanode Heap Key: HDDS-1844 URL: https://issues.apache.org/jira/browse/HDDS-1844

[jira] [Created] (HDDS-1843) Close container command should sync the Rocks db before changing to closed state.

Shashikant Banerjee created HDDS-1843: - Summary: Close container command should sync the Rocks db before changing to closed state. Key: HDDS-1843 URL: https://issues.apache.org/jira/browse/HDDS-1843

[jira] [Created] (HDFS-14661) RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist

xuzq created HDFS-14661: --- Summary: RBF：updateMountTableEntry shouldn't update mountTableEntry if targetPath not exist Key: HDFS-14661 URL: https://issues.apache.org/jira/browse/HDFS-14661 Project: Hadoop HDFS

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

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/390/ No changes -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

Re: Any thoughts making Submarine a separate Apache project?

@adam.antal The submarine development team has completed the following preparations: 1. Established a temporary test repository on Github. 2. Change the package name of hadoop submarine from org.hadoop.submarine to org.submarine 3. Combine the Linkedin/TonY code into the Hadoop submarine module;

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

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 UI (ui!) helps to merge Pull Requests to the