You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2023/05/30 18:26:00 UTC

[jira] [Resolved] (HDDS-4411) Ozone DataNode has GRPC shutdown error in stderr

     [ https://issues.apache.org/jira/browse/HDDS-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arpit Agarwal resolved HDDS-4411.
---------------------------------
    Resolution: Done

> Ozone DataNode has GRPC shutdown error in stderr 
> -------------------------------------------------
>
>                 Key: HDDS-4411
>                 URL: https://issues.apache.org/jira/browse/HDDS-4411
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Datanode
>    Affects Versions: 1.0.0
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>
> I am not sure if this belongs to Ratis or Ozone. Please feel free to move to a more suitable place. Found lots of error messages in stderr after I lost a disk and Ozone started to replicate containers around.
> {noformat}
> Oct 29, 2020 11:29:23 AM org.apache.ratis.thirdparty.io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference cleanQueue
> SEVERE: *~*~*~ Channel ManagedChannelImpl{logId=2961751, target=10.12.1.80:9859} was not shutdown properly!!! ~*~*~*
>     Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
> java.lang.RuntimeException: ManagedChannel allocation site
> 	at org.apache.ratis.thirdparty.io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference.<init>(ManagedChannelOrphanWrapper.java:93)
> 	at org.apache.ratis.thirdparty.io.grpc.internal.ManagedChannelOrphanWrapper.<init>(ManagedChannelOrphanWrapper.java:53)
> 	at org.apache.ratis.thirdparty.io.grpc.internal.ManagedChannelOrphanWrapper.<init>(ManagedChannelOrphanWrapper.java:44)
> 	at org.apache.ratis.thirdparty.io.grpc.internal.AbstractManagedChannelImplBuilder.build(AbstractManagedChannelImplBuilder.java:518)
> 	at org.apache.hadoop.ozone.container.replication.GrpcReplicationClient.<init>(GrpcReplicationClient.java:84)
> 	at org.apache.hadoop.ozone.container.replication.SimpleContainerDownloader.getContainerDataFromReplicas(SimpleContainerDownloader.java:79)
> 	at org.apache.hadoop.ozone.container.replication.DownloadAndImportReplicator.replicate(DownloadAndImportReplicator.java:112)
> 	at org.apache.hadoop.ozone.container.replication.ReplicationSupervisor$TaskRunner.run(ReplicationSupervisor.java:129)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 	at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Looks like a cosmetic issue, but I wonder if there's possibility for resource leakage if the thread is not shutdown properly. File this jira for the record.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org