[jira] [Resolved] (HDDS-702) Used fixed/external version from hadoop jars in hdds/ozone projects

[ https://issues.apache.org/jira/browse/HDDS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-702. - Resolution: Fixed Fix Version/s: 0.4.0 I have committed this only to trunk. As if

Re: Hadoop 3.2 Release Plan proposal

Another thing is that I see a bunch of jiras under HDFS-8707, which don't have the Fix Version field listing 3.2, some have it just empty. This means they will not be populated into release notes. Thanks, --Konstantin On Thu, Oct 25, 2018 at 7:59 AM Sunil G wrote: > Thanks Konstantin for

[jira] [Resolved] (HDDS-689) Datanode shuts down on restart

[ https://issues.apache.org/jira/browse/HDDS-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh resolved HDDS-689. Resolution: Duplicate > Datanode shuts down on restart > -- > >

[DISCUSS] Hadoop RPC encryption performance improvements

Folks, I would like to invite all to discuss the various Hadoop RPC encryption performance improvements. As you probably know, Hadoop RPC encryption currently relies on Java SASL, and have _really_ bad performance (in terms of number of RPCs per second, around 15~20% of the one without SASL)

[jira] [Created] (HDFS-14030) Add query whether storage has been initialized to DN's JMXBean

Adam Antal created HDFS-14030: - Summary: Add query whether storage has been initialized to DN's JMXBean Key: HDFS-14030 URL: https://issues.apache.org/jira/browse/HDFS-14030 Project: Hadoop HDFS

[jira] [Resolved] (HDDS-543) datanode service start throwing NullPointerException

[ https://issues.apache.org/jira/browse/HDDS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal resolved HDDS-543. Resolution: Done This should be fixed as part of the restart fixes per [~msingh]. > datanode

[jira] [Resolved] (HDDS-477) remove NodeManager usage from Pipeline selector

[ https://issues.apache.org/jira/browse/HDDS-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal resolved HDDS-477. Resolution: Done Fixed as part of client refactoring per [~msingh]. > remove NodeManager usage from

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/937/ [Oct 24, 2018 4:49:28 AM] (aajisaka) HADOOP-15822. zstd compressor can fail with a small output buffer. [Oct 24, 2018 6:02:53 AM] (vinayakumarb) HADOOP-15856. Trunk build fails to compile native on

[jira] [Created] (HDFS-14029) Sleep in TestLazyPersistFiles should be put into a loop

Adam Antal created HDFS-14029: - Summary: Sleep in TestLazyPersistFiles should be put into a loop Key: HDFS-14029 URL: https://issues.apache.org/jira/browse/HDFS-14029 Project: Hadoop HDFS Issue

Re: Hadoop 3.2 Release Plan proposal

Thanks Konstantin for pointing out. As 3.2 is pretty much on RC level, its better we try to find a good solution to this issue. I ll follow up on this in the jira. - Sunil On Thu, Oct 25, 2018 at 11:35 AM Konstantin Shvachko wrote: > I've tried to attract attention to an incompatibility issue

[jira] [Created] (HDFS-14028) HDFS OIV temporary dir deletes folder

Adam Antal created HDFS-14028: - Summary: HDFS OIV temporary dir deletes folder Key: HDFS-14028 URL: https://issues.apache.org/jira/browse/HDFS-14028 Project: Hadoop HDFS Issue Type: Bug

[jira] [Created] (HDDS-738) Removing REST protocol support from OzoneClient

Nanda kumar created HDDS-738: Summary: Removing REST protocol support from OzoneClient Key: HDDS-738 URL: https://issues.apache.org/jira/browse/HDDS-738 Project: Hadoop Distributed Data Store

[jira] [Created] (HDDS-737) Introduce Incremental Container Report

Nanda kumar created HDDS-737: Summary: Introduce Incremental Container Report Key: HDDS-737 URL: https://issues.apache.org/jira/browse/HDDS-737 Project: Hadoop Distributed Data Store Issue Type:

[DISCUSS] Release Apache Hadoop Ozone 0.3.0-alpha

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

[jira] [Created] (HDDS-736) scm UI conf page throwing error 'HTTP ERROR 500'

Nilotpal Nandi created HDDS-736: --- Summary: scm UI conf page throwing error 'HTTP ERROR 500' Key: HDDS-736 URL: https://issues.apache.org/jira/browse/HDDS-736 Project: Hadoop Distributed Data Store

[jira] [Created] (HDDS-735) Remove ALLOCATED and CREATING state from ContainerStateManager

Nanda kumar created HDDS-735: Summary: Remove ALLOCATED and CREATING state from ContainerStateManager Key: HDDS-735 URL: https://issues.apache.org/jira/browse/HDDS-735 Project: Hadoop Distributed Data

[jira] [Created] (HDDS-734) Remove create container logic from OzoneClient

Nanda kumar created HDDS-734: Summary: Remove create container logic from OzoneClient Key: HDDS-734 URL: https://issues.apache.org/jira/browse/HDDS-734 Project: Hadoop Distributed Data Store

[jira] [Created] (HDDS-733) Create container if not exist, as part of chunk write

Nanda kumar created HDDS-733: Summary: Create container if not exist, as part of chunk write Key: HDDS-733 URL: https://issues.apache.org/jira/browse/HDDS-733 Project: Hadoop Distributed Data Store

Re: Hadoop 3.2 Release Plan proposal

I've tried to attract attention to an incompatibility issue through the jira, but it didn't work. So pitching in in this thread. https://issues.apache.org/jira/browse/HDFS-12026 It introduced binary incompatibility, which will prevent people from upgrading from 3.1 to 3.2. I think it can get messy