[
https://issues.apache.org/jira/browse/HDDS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796447#comment-16796447
]
Bharat Viswanadham edited comment on HDDS-1306 at 3/19/19 7:21 PM:
-------------------------------------------------------------------
Hi [~ljain]
One question I have here is, In this, we are using
CompletableFuture.runAsync which uses thread from ForkJoinPool, so how we are
blocking all threads. Here only one thread is being used, and it is not
spawning multiple threads.
I agree that using Scheduler will be a good idea, but here in this logic we
just wait for some time and then once wait time is completed, we set
replicaEnabled and this task will be completed.
{quote}All the threads in the common thread pool are blocked by
ReplicationActivityStatus#fireReplicationStart call
{quote}
was (Author: bharatviswa):
Hi [~ljain]
One question I have here is, In this, we are using
CompletableFuture.runAsync which uses thread from ForkJoinPool, so how we are
blocking all threads. Here only one thread is being used, and it is not
spawning multiple threads.
{quote}All the threads in the common thread pool are blocked by
ReplicationActivityStatus#fireReplicationStart call
{quote}
> TestContainerStateManagerIntegration fails in Ratis shutdown
> ------------------------------------------------------------
>
> Key: HDDS-1306
> URL: https://issues.apache.org/jira/browse/HDDS-1306
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode, test
> Reporter: Arpit Agarwal
> Assignee: Lokesh Jain
> Priority: Blocker
> Attachments: HDDS-1306.001.patch
>
>
> TestContainerStateManagerIntegration occasionally fails in Ratis shutdown.
> Other test cases like TestScmChillMode may be failing due to the same error.
> Full stack trace in a comment below since it's a lot of text.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
