Abacn opened a new issue, #35126:
URL: https://github.com/apache/beam/issues/35126
### What happened?
Seen this several times:
```
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.StatusRuntimeException:
CANCELLED: Failed to read message.
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.Status.asRuntimeException(Status.java:532)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:481)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:564)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ClientCallImpl.access$100(ClientCallImpl.java:72)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:729)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:710)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NullPointerException
at
org.apache.beam.fn.harness.status.BeamFnStatusClient.getMemoryUsage(BeamFnStatusClient.java:164)
at
org.apache.beam.fn.harness.status.BeamFnStatusClient$InboundObserver.onNext(BeamFnStatusClient.java:283)
at
org.apache.beam.fn.harness.status.BeamFnStatusClient$InboundObserver.onNext(BeamFnStatusClient.java:279)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onMessage(ClientCalls.java:468)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInternal(ClientCallImpl.java:657)
at
org.apache.beam.vendor.grpc.v1p69p0.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInContext(ClientCallImpl.java:644)
... 5 more
```
It points to here:
https://github.com/apache/beam/blob/ab191181d9d143f28fe5b598144a6553ff4b0489/sdks/java/harness/src/main/java/org/apache/beam/fn/harness/status/BeamFnStatusClient.java#L164
it appears `memoryMonitor` is null. However, it has been setup in
constructor. Not sure how this is possible
The error is transient. Happens for some seconds at pipeline start up on
worker but the pipeline can evantually run
### Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Infrastructure
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
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.
To unsubscribe, e-mail: github-unsubscr...@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
