[jira] [Commented] (HDFS-13876) HttpFS: Implement ALLOWSNAPSHOT, DISALLOWSNAPSHOT

[ https://issues.apache.org/jira/browse/HDFS-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625384#comment-16625384 ] Wei-Chiu Chuang commented on HDFS-13876: +1 from me too. [~ljain] anything else you'd like to

[jira] [Commented] (HDFS-13876) HttpFS: Implement ALLOWSNAPSHOT, DISALLOWSNAPSHOT

[ https://issues.apache.org/jira/browse/HDFS-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625153#comment-16625153 ] Shashikant Banerjee commented on HDFS-13876: Thanks [~smeng], for updating the patch. The

[jira] [Commented] (HDDS-447) separate ozone-dist and hadoop-dist projects with real classpath separation

[ https://issues.apache.org/jira/browse/HDDS-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625182#comment-16625182 ] Elek, Marton commented on HDDS-447: --- Jenkins is constantly failing with unit test timeout. Don't know if

[jira] [Resolved] (HDDS-63) OzoneManager crashes on jmx call

[ https://issues.apache.org/jira/browse/HDDS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar resolved HDDS-63. - Resolution: Duplicate > OzoneManager crashes on jmx call > > >

[jira] [Commented] (HDDS-535) Ozone Manager tries to start on non OM host

[ https://issues.apache.org/jira/browse/HDDS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625010#comment-16625010 ] Nanda kumar commented on HDDS-535: -- [~nmaheshwari], this is expected behavior. {{'ozone om'}} command,

[jira] [Comment Edited] (HDDS-535) Ozone Manager tries to start on non OM host

[ https://issues.apache.org/jira/browse/HDDS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625010#comment-16625010 ] Nanda kumar edited comment on HDDS-535 at 9/23/18 7:25 AM: --- [~nmaheshwari], this

[jira] [Commented] (HDDS-63) OzoneManager crashes on jmx call

[ https://issues.apache.org/jira/browse/HDDS-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624979#comment-16624979 ] Nanda kumar commented on HDDS-63: - [~anu], [~elek] The problem was with RocksDB. We have upgraded rocksdb

[jira] [Comment Edited] (HDDS-535) Ozone Manager tries to start on non OM host

[ https://issues.apache.org/jira/browse/HDDS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625010#comment-16625010 ] Nanda kumar edited comment on HDDS-535 at 9/23/18 7:26 AM: --- [~nmaheshwari], this

[jira] [Comment Edited] (HDDS-535) Ozone Manager tries to start on non OM host

[ https://issues.apache.org/jira/browse/HDDS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625010#comment-16625010 ] Nanda kumar edited comment on HDDS-535 at 9/23/18 7:27 AM: --- [~nmaheshwari], this

[jira] [Commented] (HDFS-13713) Add specification of Multipart Upload API to FS specification, with contract tests

[ https://issues.apache.org/jira/browse/HDFS-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625083#comment-16625083 ] Steve Loughran commented on HDFS-13713: --- {checkstyle}

[jira] [Updated] (HDFS-13934) Multipart uploaders to be created through API call to FileSystem/FileContext, not service loader

[ https://issues.apache.org/jira/browse/HDFS-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-13934: -- Description: the Multipart Uploaders are created via service loaders. This is troublesome #

[jira] [Commented] (HDDS-221) Create acceptance test to test ./start-ozone.sh and ./stop-ozone.sh for ozone/hdds

[ https://issues.apache.org/jira/browse/HDDS-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625119#comment-16625119 ] Sandeep Nemuri commented on HDDS-221: - [~anu], Even the new tests are starting the daemons

[jira] [Created] (HDFS-13934) Multipart uploaders to be created through API call to FileSystem/FileContext, not service loader

Steve Loughran created HDFS-13934: - Summary: Multipart uploaders to be created through API call to FileSystem/FileContext, not service loader Key: HDFS-13934 URL: https://issues.apache.org/jira/browse/HDFS-13934

[jira] [Comment Edited] (HDFS-13713) Add specification of Multipart Upload API to FS specification, with contract tests

[ https://issues.apache.org/jira/browse/HDFS-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625083#comment-16625083 ] Steve Loughran edited comment on HDFS-13713 at 9/23/18 12:02 PM: - {code}

[jira] [Comment Edited] (HDDS-535) Ozone Manager tries to start on non OM host

[ https://issues.apache.org/jira/browse/HDDS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625010#comment-16625010 ] Nanda kumar edited comment on HDDS-535 at 9/23/18 1:34 PM: --- [~nmaheshwari], this

[jira] [Commented] (HDDS-223) Create acceptance test for using datanode plugin

[ https://issues.apache.org/jira/browse/HDDS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625140#comment-16625140 ] Sandeep Nemuri commented on HDDS-223: - [~elek] This requirement seems to be addressed by HDDS-446, Do

[jira] [Created] (HDDS-542) Move Pipeline Creation to Ozone client

Shashikant Banerjee created HDDS-542: Summary: Move Pipeline Creation to Ozone client Key: HDDS-542 URL: https://issues.apache.org/jira/browse/HDDS-542 Project: Hadoop Distributed Data Store