djaneluz opened a new issue, #21825:
URL: https://github.com/apache/beam/issues/21825
### What happened?
I'm using **RedisIO** to read/write values on cache and it was working fine
with version _2.38.0._
When I moved to version _2.39.0_ I started getting errors like:
`Execution of work for computation 'P13' for key
'<�֤#�͵.;]�NDC���^m��=�w<@癢P�u:k<��ުm�7����6�';� �z �<
z0��>2QN����9EX�-����k\����eL� �( ���a����;��φ' failed with
out-of-memory. Work will not be retried locally. Heap dump not written.`
With stacktrace:
`java.lang.OutOfMemoryError: unable to create native thread: possibly out of
memory or process/resource limits reached
at java.base/java.lang.Thread.start0(Native Method)
at java.base/java.lang.Thread.start(Thread.java:803)
at
java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:937)
at
java.base/java.util.concurrent.ThreadPoolExecutor.ensurePrestart(ThreadPoolExecutor.java:1583)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:346)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:562)
at
java.base/java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:779)
at
org.apache.beam.runners.dataflow.worker.repackaged.org.apache.beam.runners.core.OutputAndTimeBoundedSplittableProcessElementInvoker$ProcessContext.onClaimed(OutputAndTimeBoundedSplittableProcessElementInvoker.java:312)
at
org.apache.beam.runners.dataflow.worker.repackaged.org.apache.beam.sdk.fn.splittabledofn.RestrictionTrackers$RestrictionTrackerObserver.tryClaim(RestrictionTrackers.java:60)
at
org.apache.beam.sdk.io.redis.RedisIO$ReadFn.processElement(RedisIO.java:399)`
The error happens when calling `RedisIO.readKeyPatterns()`
The pipeline get stuck in the Step:
`.../ReadRedis/ParDo(Read)/ParMultiDo(Read)/ProcessKeyedElements.out0`
### Issue Priority
Priority: 0
### Issue Component
Component: io-java-redis
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
