[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063749#comment-17063749
]
Mukul Kumar Singh commented on HDDS-3241:
-
[~linyiqun], The issue described by you is a case where
smengcl commented on issue #696: HDDS-3056. Allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-601912322
Discussed with @arp7 @xiaoyuyao @dineshchitlangia . Our conclusion is that
we want to allow users who have access to some volumes to
Aravindan Vijayan created HDDS-3243:
---
Summary: Recon should not have the ability to send Create/Close
Container commands to Datanode.
Key: HDDS-3243
URL: https://issues.apache.org/jira/browse/HDDS-3243
[
https://issues.apache.org/jira/browse/HDDS-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan reassigned HDDS-3243:
---
Assignee: Aravindan Vijayan
> Recon should not have the ability to send Create/Close
[
https://issues.apache.org/jira/browse/HDDS-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-3221.
-
Fix Version/s: 0.6.0
Resolution: Fixed
> Refactor SafeModeHandler to use a
Stephen O'Donnell created HDDS-3242:
---
Summary: Investigate use of EventQueue by SafeModeHandler instead
of notifying objects directly
Key: HDDS-3242
URL: https://issues.apache.org/jira/browse/HDDS-3242
sodonnel merged pull request #690: HDDS-3221. Refactor SafeModeHandler to use a
Notification Interface
URL: https://github.com/apache/hadoop-ozone/pull/690
This is an automated message from the Apache Git Service.
To
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063440#comment-17063440
]
Yiqun Lin edited comment on HDDS-3241 at 3/20/20, 3:02 PM:
---
Hi [~elek],
In HDFS
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063440#comment-17063440
]
Yiqun Lin commented on HDDS-3241:
-
Hi [~elek],
In HDFS world, invalid blocks reported to NameNode will be
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDDS-3241:
Description:
For the invalid or out-updated container reported by Datanode,
ContainerReportHandler in SCM
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063418#comment-17063418
]
Marton Elek commented on HDDS-3241:
---
> We could have a setting to control this auto-deletion behavior if
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDDS-3241:
Description:
For the invalid or out-updated container reported by Datanode,
ContainerReportHandler in SCM
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDDS-3241:
Status: Patch Available (was: Open)
> Invalid container reported to SCM should be deleted
>
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3241:
-
Labels: pull-request-available (was: )
> Invalid container reported to SCM should be deleted
>
linyiqun opened a new pull request #702: HDDS-3241. Invalid container reported
to SCM should be deleted.
URL: https://github.com/apache/hadoop-ozone/pull/702
## What changes were proposed in this pull request?
SCM takes delete action for invalid container that reported by Datanodes.
[
https://issues.apache.org/jira/browse/HDDS-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDDS-3241:
Affects Version/s: 0.4.1
> Invalid container reported to SCM should be deleted
>
Yiqun Lin created HDDS-3241:
---
Summary: Invalid container reported to SCM should be deleted
Key: HDDS-3241
URL: https://issues.apache.org/jira/browse/HDDS-3241
Project: Hadoop Distributed Data Store
sodonnel commented on a change in pull request #668: HDDS-3139 Pipeline
placement should max out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#discussion_r395613532
##
File path:
sodonnel commented on a change in pull request #668: HDDS-3139 Pipeline
placement should max out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#discussion_r395615512
##
File path:
sodonnel commented on a change in pull request #668: HDDS-3139 Pipeline
placement should max out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#discussion_r395613532
##
File path:
sodonnel commented on a change in pull request #668: HDDS-3139 Pipeline
placement should max out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#discussion_r395610027
##
File path:
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Summary: Improve write efficiency by creating container in parallel. (was:
Improve write efficiency by
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description:
1. As the image shows, when stage is
DispatcherContext.WriteChunkStage.WRITE_DATA, the
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description:
1. As the image shows, when stage is
DispatcherContext.WriteChunkStage.WRITE_DATA, the
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description:
1.As the image shows, when stage is
DispatcherContext.WriteChunkStage.WRITE_DATA, the
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063324#comment-17063324
]
runzhiwang commented on HDDS-3240:
--
I'm working on it.
> Improve write efficiency by creating container
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description:
As the image shows, when write data, the leader datanode execute two steps:
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description:
1.As the image shows, when write data, the leader datanode execute two steps:
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang reassigned HDDS-3240:
Assignee: runzhiwang
> Improve write efficiency by creating container parallel.
>
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description:
!screenshot-1.png!
was: !screenshot-1.png!
> Improve write efficiency by creating
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Description: !screenshot-1.png!
> Improve write efficiency by creating container parallel.
>
runzhiwang created HDDS-3240:
Summary: Improve write efficiency by creating container parallel.
Key: HDDS-3240
URL: https://issues.apache.org/jira/browse/HDDS-3240
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3240:
-
Attachment: screenshot-1.png
> Improve write efficiency by creating container parallel.
>
sodonnel commented on a change in pull request #668: HDDS-3139 Pipeline
placement should max out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#discussion_r395584916
##
File path:
sodonnel commented on a change in pull request #668: HDDS-3139 Pipeline
placement should max out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#discussion_r395583248
##
File path:
[
https://issues.apache.org/jira/browse/HDDS-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-2691:
---
Status: Patch Available (was: Open)
> Ozone Shell code cleanup
>
>
adoroszlai opened a new pull request #701: HDDS-2691. Ozone Shell code cleanup
URL: https://github.com/apache/hadoop-ozone/pull/701
## What changes were proposed in this pull request?
Reduce code duplication in Ozone Shell by:
1. moving the [common structure of subcommand
[
https://issues.apache.org/jira/browse/HDDS-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-2691:
-
Labels: pull-request-available (was: )
> Ozone Shell code cleanup
>
>
>
Marton Elek created HDDS-3239:
-
Summary: Provide message-level metrics from the generic protocol
dispatch
Key: HDDS-3239
URL: https://issues.apache.org/jira/browse/HDDS-3239
Project: Hadoop Distributed
sodonnel commented on issue #690: HDDS-3221. Refactor SafeModeHandler to use a
Notification Interface
URL: https://github.com/apache/hadoop-ozone/pull/690#issuecomment-601637938
Bahart has given this a +1. I spoke to Nanda offline who is also happy.
I am going to commit this by end
[
https://issues.apache.org/jira/browse/HDDS-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-2943:
---
Status: Patch Available (was: In Progress)
> Parameterize unit tests for chunk manager
41 matches
Mail list logo
