suztomo edited a comment on pull request #14768: URL: https://github.com/apache/beam/pull/14768#issuecomment-840228795
When GrpcLoggingServiceTest or BeamFnLoggingServiceTest gets stuck, the thread dumps do not have "grpc-default-executor-XXX" threads: - thread dump for GrpcLoggingServiceTest case: https://gist.github.com/suztomo/64b36fd7c7e011666cbc8f99d1079ed7 - thread dump for BeamFnLoggingServiceTest case: https://gist.github.com/suztomo/7aceec57e36b82fccccce0abfe70c8a0 Interestingly, after the 5-second timeout the "grpc-default-executor-XXX" threads reappear in the log https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/17689/testReport/junit/org.apache.beam.runners.fnexecution.logging/GrpcLoggingServiceTest/testMultipleClientsFailingIsHandledGracefullyByServer/. ``` 21:25:16.872 [pool-123-thread-3] INFO o.a.b.r.f.l.GrpcLoggingServiceTest - Sent onError for client 3 21:25:21.797 [Test worker] DEBUG o.a.b.v.g.v.i.g.i.ServerImplBuilder - Unable to apply census stats ... 21:25:21.817 [grpc-default-executor-2] INFO o.a.b.r.f.logging.GrpcLoggingService - Beam Fn Logging client connected. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
