[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng resolved HDDS-4186.
-
Resolution: Fixed
> Adjust RetryPolicy of SCMConnectionManager for SCM/Recon
>
[
https://issues.apache.org/jira/browse/HDDS-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4192:
Description: (was:
Fix a bug in https://issues.apache.org/jira/browse/HDDS-3895
In
Glen Geng created HDDS-4192:
---
Summary: enable SCM Raft Group based on config ozone.scm.names
Key: HDDS-4192
URL: https://issues.apache.org/jira/browse/HDDS-4192
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4192:
Labels: (was: pull-request-available)
> enable SCM Raft Group based on config ozone.scm.names
>
[
https://issues.apache.org/jira/browse/HDDS-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4192:
Description:
Say ozone.scm.names is "ip1,ip2,ip3", scm with ip1 identifies its RaftPeerId as
scm1, scm
[
https://issues.apache.org/jira/browse/HDDS-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4192:
Description:
Say ozone.scm.names is "ip1,ip2,ip3", scm with ip1 identifies its RaftPeerId as
scm1, scm
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Description:
*The problem is:*
If setup one Recon and one SCM, then shutdown the Recon server, all
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Target Version/s: (was: 0.7.0)
> Adjust RetryPolicy of SCMConnectionManager
>
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Summary: Adjust RetryPolicy of SCMConnectionManager (was: CLONE - Improve
performance of the BufferPool
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Labels: (was: pull-request-available)
> Adjust RetryPolicy of SCMConnectionManager
>
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Summary: Adjust RetryPolicy of SCMConnectionManager for SCM/Recon (was:
Adjust RetryPolicy of
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Component/s: Ozone Datanode
> Adjust RetryPolicy of SCMConnectionManager for SCM/Recon
>
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng reassigned HDDS-4186:
---
Assignee: Glen Geng (was: Marton Elek)
> CLONE - Improve performance of the BufferPool management
Glen Geng created HDDS-4186:
---
Summary: CLONE - Improve performance of the BufferPool management
of Ozone client
Key: HDDS-4186
URL: https://issues.apache.org/jira/browse/HDDS-4186
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Description:
Current RetryPolicy of Datanode for SCM is retryForeverWithFixedSleep:
{code:java}
RetryPolicy
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Description:
Current RetryPolicy of Datanode for SCM is retryForeverWithFixedSleep:
{code:java}
RetryPolicy
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Description:
Current RetryPolicy of Datanode for SCM is retryForeverWithFixedSleep:
{code:java}
RetryPolicy
[
https://issues.apache.org/jira/browse/HDDS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4186:
Description:
*The problem is:*
If setup one Recon and one SCM, then shutdown the Recon server, all
Glen Geng created HDDS-4230:
---
Summary: CLONE - Add failover proxy to SCM block protocol
Key: HDDS-4230
URL: https://issues.apache.org/jira/browse/HDDS-4230
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4230:
Description:
like OMFailoverProxyProvider, SCMBlockLocationFailoverProxyProvider should
also handle
[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4230:
Description: like OMFailoverProxyProvider, (was: Need to supports 2N + 1
SCMs. Add configs and logic to
[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4230:
Summary: SCMBlockLocationFailoverProxyProvider should handle
LeaderNotReadyException (was: CLONE - Add
[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4230:
Description:
It is an enhancement for HDDS-3188.
Like OMFailoverProxyProvider,
[
https://issues.apache.org/jira/browse/HDDS-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng reassigned HDDS-4230:
---
Assignee: (was: Li Cheng)
> SCMBlockLocationFailoverProxyProvider should handle
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Labels: pull-requests-available (was: pull-request-available)
> add field 'num' to ALLOCATE_BLOCK of scm
Glen Geng created HDDS-4228:
---
Summary: ALLOCATE_BLOCK of scm audit log miss num
Key: HDDS-4228
URL: https://issues.apache.org/jira/browse/HDDS-4228
Project: Hadoop Distributed Data Store
Issue
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng reassigned HDDS-4228:
---
Assignee: Glen Geng (was: Marton Elek)
> ALLOCATE_BLOCK of scm audit log miss num
>
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Labels: (was: pull-request-available)
> ALLOCATE_BLOCK of scm audit log miss num
>
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Priority: Minor (was: Blocker)
> ALLOCATE_BLOCK of scm audit log miss num
>
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Description:
The scm audit log for ALLOCATE_BLOCK is as follows:
{code:java}
2020-09-10 03:42:08,196 |
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Description:
The scm audit log for ALLOCATE_BLOCK is as follows:
{code:java}
2020-09-10 03:42:08,196 |
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Summary: add field 'num' to ALLOCATE_BLOCK of scm audit log. (was:
ALLOCATE_BLOCK of scm audit log miss
[
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4228:
Description:
The sac
{code:java}
2020-09-10 03:42:08,196 | INFO | SCMAudit | user=root |
[
https://issues.apache.org/jira/browse/HDDS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190638#comment-17190638
]
Glen Geng commented on HDDS-4107:
-
I am working on the upgrade issues for this PR, found that renaming the
[
https://issues.apache.org/jira/browse/HDDS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190638#comment-17190638
]
Glen Geng edited comment on HDDS-4107 at 9/4/20, 9:06 AM:
--
I am working on the
Glen Geng created HDDS-4351:
---
Summary: DN crash while RatisApplyTransactionExecutor tries to
putBlock to rocksDB
Key: HDDS-4351
URL: https://issues.apache.org/jira/browse/HDDS-4351
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Description:
{code:java}
// If there are unhealthy replicas, then we should remove them even if it
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Summary: ReplicationManager.handleOverReplicatedContainer does not handle
(was: CLONE - OM client request
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Component/s: (was: OM HA)
SCM
> CLONE - OM client request fails with "failed to commit
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Description:
{code:java}
20/08/28 03:21:53 WARN retry.RetryInvocationHandler: A failover has occurred
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng reassigned HDDS-4343:
---
Assignee: Glen Geng (was: Bharat Viswanadham)
> CLONE - OM client request fails with "failed to
Glen Geng created HDDS-4343:
---
Summary: CLONE - OM client request fails with "failed to commit as
key is not found in OpenKey table"
Key: HDDS-4343
URL: https://issues.apache.org/jira/browse/HDDS-4343
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Summary: ReplicationManager.handleOverReplicatedContainer() does not handle
unhealthyReplicas properly.
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Description:
{code:java}
// If there are unhealthy replicas, then we should remove them even if it
[
https://issues.apache.org/jira/browse/HDDS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4343:
Priority: Minor (was: Blocker)
> ReplicationManager.handleOverReplicatedContainer() does not handle
>
[
https://issues.apache.org/jira/browse/HDDS-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17215219#comment-17215219
]
Glen Geng commented on HDDS-4351:
-
Hello [~erose] [~arp] [~bharat]
As requested by Ethan, I scheduled a
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng resolved HDDS-4128.
-
Resolution: Duplicate
> RATIS ONE Pipeline is closed but not removed when a datanode goes stale
>
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179446#comment-17179446
]
Glen Geng commented on HDDS-4128:
-
close as duplicate with HDDS-4125.
> RATIS ONE Pipeline is closed but
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179352#comment-17179352
]
Glen Geng commented on HDDS-4125:
-
RATIS THREE pipeline, if stay in closed state, should be removed by
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4128:
Description:
Since the Scheduler in SCMPipelineManager that used to destroyPipeline is
removed,
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4128:
Description:
RATIS ONE Pipeline is closed but not removed when a datanode goes stale.
Since the
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4128:
Description:
Since the Scheduler in SCMPipelineManager that used to destroyPipeline is
removed,
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179375#comment-17179375
]
Glen Geng commented on HDDS-4125:
-
Create a new Jira https://issues.apache.org/jira/browse/HDDS-4128 to
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4125:
Description:
When a node goes stale the pipelines in that node have to be closed and removed
from
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4125:
Description:
When a node goes stale the pipelines in that node have to be closed and removed
from
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4128:
Description: (was: When a node goes stale the pipelines in that node
have to be closed and removed from
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4128:
Summary: RATIS ONE Pipeline is closed but not removed when a datanode goes
stale (was: CLONE - Pipeline is
Glen Geng created HDDS-4128:
---
Summary: CLONE - Pipeline is not removed when a datanode goes stale
Key: HDDS-4128
URL: https://issues.apache.org/jira/browse/HDDS-4128
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179374#comment-17179374
]
Glen Geng commented on HDDS-4128:
-
FYI [~nanda] [~timmylicheng]
related to
[
https://issues.apache.org/jira/browse/HDDS-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng resolved HDDS-4093.
-
Release Note: PR merged.
Resolution: Fixed
> update RATIS version from 1.0.0 to
Glen Geng created HDDS-4130:
---
Summary: remove the 1st edition RatisServer of SCM HA, which is
copied from OM HA
Key: HDDS-4130
URL: https://issues.apache.org/jira/browse/HDDS-4130
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Summary: remove the 1st edition of RatisServer of SCM HA which is copied
from OM HA (was: remove the 1st
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Summary: remove the 1st edition RatisServer of SCM HA which is copied from
OM HA (was: remove the 1st
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Description: The 1st edition RatisServer of SCM HA is copied (was: The
disk layout per volume is as
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Description:
The 1st edition of RatisServer of SCM HA is copied from OM HA.
This version abandoned, since
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Labels: (was: backward-incompatible pull-request-available upgrade)
> remove the 1st edition of
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Description:
The 1st edition of RatisServer of SCM HA is copied from OM HA.
This version abandoned, since
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4130:
Description:
The 1st edition of RatisServer of SCM HA is copied from OM HA.
This version is abandoned,
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng resolved HDDS-4125.
-
Resolution: Fixed
> Pipeline is not removed when a datanode goes stale
>
Glen Geng created HDDS-4136:
---
Summary: CLONE - In ContainerStateManagerV2, modification of
RocksDB should be consistent with that of memory state.
Key: HDDS-4136
URL: https://issues.apache.org/jira/browse/HDDS-4136
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Summary: Design for Error/Exception handling in state update for
container/pipeline V2 (was: Design for
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Summary: Design for Error/Exception handling in state updates for
container/pipeline V2 (was: CLONE - In
Glen Geng created HDDS-4135:
---
Summary: In ContainerStateManagerV2, modification of RocksDB
should be in consistency with that of memory state.
Key: HDDS-4135
URL: https://issues.apache.org/jira/browse/HDDS-4135
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4135:
Description:
Fix a bug in https://issues.apache.org/jira/browse/HDDS-3895
In ContainerStateManagerV2,
[
https://issues.apache.org/jira/browse/HDDS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4135:
Labels: (was: pull-request-available)
> In ContainerStateManagerV2, modification of RocksDB should be
[
https://issues.apache.org/jira/browse/HDDS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4135:
Description:
Fix a bug in https://issues.apache.org/jira/browse/HDDS-3895
In
[
https://issues.apache.org/jira/browse/HDDS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4135:
Summary: In ContainerStateManagerV2, modification of RocksDB should be
consistent with that of memory
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handling exceptions occurred in writing RocksDB
for container
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description: (was:
Fix a bug in https://issues.apache.org/jira/browse/HDDS-3895
In
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4135:
Description:
Fix a bug in https://issues.apache.org/jira/browse/HDDS-3895
was:
The 1st edition
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4136:
Description:
I have a concern about how to handle exceptions occurred in writing RocksDB for
container V2,
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178919#comment-17178919
]
Glen Geng commented on HDDS-4125:
-
Since the thread pool that remove RATIS ONE pipeline is removed, we
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178919#comment-17178919
]
Glen Geng edited comment on HDDS-4125 at 8/17/20, 11:32 AM:
Since the thread
[
https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178917#comment-17178917
]
Glen Geng commented on HDDS-4125:
-
Hi Nanda, I encountered this issue as well, and provide a fix. Please
[
https://issues.apache.org/jira/browse/HDDS-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng resolved HDDS-4130.
-
Resolution: Fixed
> remove the 1st edition of RatisServer of SCM HA which is copied from OM HA
>
[
https://issues.apache.org/jira/browse/HDDS-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4365:
Description:
in SCMBlockLocationFailoverProxyProvider, currently it is
{code:java}
private
Glen Geng created HDDS-4365:
---
Summary: SCMBlockLocationFailoverProxyProvider should use
ScmBlockLocationProtocolPB.class in RPC.setProtocolEngine
Key: HDDS-4365
URL: https://issues.apache.org/jira/browse/HDDS-4365
[
https://issues.apache.org/jira/browse/HDDS-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4365:
Description:
in SCMBlockLocationFailoverProxyProvider, it should be
{code:java}
private
[
https://issues.apache.org/jira/browse/HDDS-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng reassigned HDDS-4365:
---
Assignee: Glen Geng
> SCMBlockLocationFailoverProxyProvider should use
>
[
https://issues.apache.org/jira/browse/HDDS-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4365:
Description:
in SCMBlockLocationFailoverProxyProvider,
currently it is
{code:java}
private
[
https://issues.apache.org/jira/browse/HDDS-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4365:
Priority: Minor (was: Major)
> SCMBlockLocationFailoverProxyProvider should use
>
[
https://issues.apache.org/jira/browse/HDDS-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221081#comment-17221081
]
Glen Geng commented on HDDS-4355:
-
cc [~avijayan]
> Deleted container is marked as missing on recon UI
>
[
https://issues.apache.org/jira/browse/HDDS-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221079#comment-17221079
]
Glen Geng commented on HDDS-4385:
-
cc @[~avijayan]
> It would be nice if there is a search function using
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
1 - 100 of 160 matches
Mail list logo
