You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "damondouglas (via GitHub)" <gi...@apache.org> on 2024/05/17 18:29:06 UTC
[I] [Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements [beam]
damondouglas opened a new issue, #31338:
URL: https://github.com/apache/beam/issues/31338
### What happened?
Java test `org.apache.beam.sdk.transforms.FlattenTest` fails on Prism with error `panic: nothing in progress and no refreshes with non zero pending elements`:
Steps to reproduce.
1) Run Prism server.
```
./gradlew :runners:prism:runServer
```
2) Execute `:runners:portability:java:ulrLoopbackValidatesRunnerTests` on Prism:
```
TEST=org.apache.beam.sdk.transforms.FlattenTest
./gradlew :runners:portability:java:ulrLoopbackValidatesRunnerTests -PjobEndpoint=localhost:8073 --tests="$TEST"
```
Parent tracker: #28187
### Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [X] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] 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-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements [beam]
Posted by "lostluck (via GitHub)" <gi...@apache.org>.
lostluck commented on issue #31338:
URL: https://github.com/apache/beam/issues/31338#issuecomment-2147419037
I'd put the test (and clarify that it's running on prism) in the title instead of the symptom. The panic is to avoid a forever hang when there is no way to make progress. It's never going to be unique to this test. You will see this much more.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements [beam]
Posted by "damondouglas (via GitHub)" <gi...@apache.org>.
damondouglas commented on issue #31338:
URL: https://github.com/apache/beam/issues/31338#issuecomment-2146300399
@lostluck so far I found that job being stuck, reported by the panic, may be due to the upstream watermark. In the following logs, I see a reporting of "insufficient upstream watermark" i.e. `inputW == upstreamW` in the bundleReady method. One hypothesis generating idea would be to collect which Java validates runner tests are leading to the panic to detect a potential pattern.
```
{"time":"2024-06-03T23:16:17.984115241Z","level":"DEBUG","msg":"bundleReady: insufficient upstream watermark","stage":"stage-001","watermark":{"upstream":9223372036854775,"input":9223372036854775}}
{"time":"2024-06-03T23:16:17.984145011Z","level":"DEBUG","msg":"Bundles: nothing in progress after advance","advanced":{"stage-001":{}},"refreshCount":1,"pendingElementCount":2}
{"time":"2024-06-03T23:16:17.984161971Z","level":"DEBUG","msg":"bundleReady: insufficient upstream watermark","stage":"stage-006","watermark":{"upstream":-9223372036854775,"input":-9223372036854775}}
{"time":"2024-06-03T23:16:17.984172671Z","level":"DEBUG","msg":"Bundles: nothing in progress and no refreshes","pendingElementCount":2}
panic: nothing in progress and no refreshes with non zero pending elements: 2
```
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements [beam]
Posted by "damondouglas (via GitHub)" <gi...@apache.org>.
damondouglas closed issue #31338: [Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements
URL: https://github.com/apache/beam/issues/31338
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][Prism]: panic: nothing in progress and no refreshes with non zero pending elements [beam]
Posted by "damondouglas (via GitHub)" <gi...@apache.org>.
damondouglas commented on issue #31338:
URL: https://github.com/apache/beam/issues/31338#issuecomment-2148544851
> I'd put the test (and clarify that it's running on prism) in the title instead of the symptom. The panic is to avoid a forever hang when there is no way to make progress. It's never going to be unique to this test. You will see this much more.
Multiple tests result in this panic. I just chose one so it is quick to get to this state.
--
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-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org