Hi @capchriscap ,
The issue seems to be similar to this one, but it had been fixed in 1.3.0.
Are you using a partitionKey for the data written to Kinesis ?
Have you checked that you’re not reaching Kinesis quotas ?
Can theses issues be caused by some garbage collection issues or something similar? Up to 60-80% CPU load, the enrichers work smoothly but between 80-100% CPU load, the performance seem to be reduced (for some enrichers)
It’s hard to make guesses. Would you be able to run the enrichers with the JMX port open on the JVM, so that when an enricher gets stuck you can use a profiler (e.g. visualvm). To do that you can add -Dcom.sun.management.jmxremote.port=5555 -Dcom.sun.management.jmxremote.rmi.port=5555 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=127.0.0.1 to the JAVA_OPTS.