Question
3
Replies
543
Views
Sun Life Financial Company
Posted: August 23, 2019
Last activity: August 25, 2019
Closed
org.apache.kafka.common.errors.InterruptException in logs
Hi,
We are seeing lot of kafka exceptions in the log even though we are not using Kafka broker. Does it affect the system? How can it be suppressed?
BrokerSession[brokerId=1047,broker=Broker[endpoints=PLAINTEXT://159.208.196.160:1090,jmxPort=1092,rack=null,version=4],startTime=1566404266237,lastSeen=1566576587280,prpcNode=1c8d9f67b38cf47d7e997388979e6f60]BrokerSession[brokerId=1046,broker=Broker[endpoints=PLAINTEXT://159.208.196.159:1190,jmxPort=1192,rack=null,version=4],startTime=1566532851976,lastSeen=1566576578292,prpcNode=df8e69d3ba0e660dac458184e4f12564]BrokerSession[brokerId=1045,broker=Broker[endpoints=PLAINTEXT://159.208.196.159:1090,jmxPort=1092,rack=null,version=4],startTime=1566418645832,lastSeen=1566576580343,prpcNode=47bd5bcb5d4cfd54214b202b6ff24d2a]BrokerSession[brokerId=1042,broker=Broker[endpoints=PLAINTEXT://159.208.196.18:7010,jmxPort=7030,rack=null,version=4],startTime=1566317575507,lastSeen=1566576584022,prpcNode=aadfc5717fb3d7eade65be28f187b33f]BrokerSession[brokerId=1044,broker=Broker[endpoints=PLAINTEXT://159.208.196.18:8010,jmxPort=8030,rack=null,version=4],startTime=1566505764889,lastSeen=1566576582165,prpcNode=22fbb468ae8fae964110a730a819bdde]]org.apache.kafka.common.errors.InterruptException: java.lang.InterruptedExceptionat org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.maybeThrowInterruptException(ConsumerNetworkClient.java:428) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:248) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:208) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:199) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.awaitMetadataUpdate(ConsumerNetworkClient.java:134) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.Fetcher.retrieveOffsetsByTimes(Fetcher.java:470) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.Fetcher.beginningOrEndOffset(Fetcher.java:500) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.internals.Fetcher.endOffsets(Fetcher.java:485) ~[kafka-clients-0.11.0.3.jar:?]at org.apache.kafka.clients.consumer.KafkaConsumer.endOffsets(KafkaConsumer.java:1536) ~[kafka-clients-0.11.0.3.jar:?]at com.pega.dsm.dnode.impl.dataset.kafka.features.KafkaResumableFeature$KafkaLagDetector.compute(KafkaResumableFeature.java:184) ~[d-node-8.2.2-354.jar:?]at com.pega.dsm.dnode.impl.dataset.kafka.features.KafkaResumableFeature$KafkaLagDetector.compute(KafkaResumableFeature.java:153) ~[d-node-8.2.2-354.jar:?]at com.pega.dsm.dnode.impl.dataflow.asyncexecutor.QueueProcessorDataSetOperationsImpl.getLag(QueueProcessorDataSetOperationsImpl.java:266) ~[d-node-8.2.2-354.jar:?]at com.pega.platform.executor.queueprocessor.internal.QueueProcessorManagementOperationsImpl$LagCalculator.execute(QueueProcessorManagementOperationsImpl.java:279) ~[pega-executor.jar:?]at com.pega.platform.executor.queueprocessor.internal.BatchTask.lambda$executeInBorrowedRequestor$0(BatchTask.java:69) ~[pega-executor.jar:?]at com.pega.platform.executor.queueprocessor.internal.BatchTask$$Lambda$2017.0000000068732A00.run(Unknown Source) ~[?:?]at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1371) ~[prprivate.jar:?]at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1114) ~[prprivate.jar:?]at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:995) ~[prprivate.jar:?]at com.pega.pegarules.session.internal.PRSessionProviderImplForModules.doWithRequestorLocked(PRSessionProviderImplForModules.java:55) ~[prprivate.jar:?]at com.pega.platform.executor.queueprocessor.internal.BatchTask.executeInBorrowedRequestor(BatchTask.java:65) ~[pega-executor.jar:?]at com.pega.platform.executor.queueprocessor.internal.BatchTask.run(BatchTask.java:40) ~[pega-executor.jar:?]at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522) ~[?:1.8.0]at java.util.concurrent.FutureTask.run(FutureTask.java:277) ~[?:1.8.0]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160) [?:1.8.0]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:1.8.0]at java.lang.Thread.run(Thread.java:811) [?:2.9 (07-31-2018)]Caused by: java.lang.InterruptedException... 26 more
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 1 year ago
@KevinZheng_GCS It's not set. And this is the development environment and has one node only. Won't setting up a node type to "WebUser" suppress BackgroundProcessing queue processors (since there is only one node)?
Posted: 1 year ago
It would. You can set -DNodeType=WebUser,BackgroundProcessing,Stream. In Pega Infinity, Stream is required for queue processing. What is your exact version (including patch version)? If this is happening consistently, please attach the entire log file.
Pega OOTB uses kafka (hosted on stream nodes, i.e., nodetype of Stream) for queue processing in pega 8.x (you are running 8.2.2?), see this link
https://community.pega.com/knowledgebase/queue-processor-faq.
We recommend specific node type for different nodes (i.e., for Foreground node, use -DNodeType=WebUser).
What exactly is your NodeType? Are you using 'Universal' node type?