Hi Team I am using Kinesis consumer of real time table The server keeps logging

WARN [KinesisConsumer] Task aborted due to exception

and below stack trace

2022/01/20 10:55:36.685 WARN [KinesisConsumer] [pool-207-thread-1] Task aborted due to exception.
shaded.software.amazon.awssdk.core.exception.AbortedException: Thread was interrupted
        at shaded.software.amazon.awssdk.core.exception.AbortedException$BuilderImpl.build(AbortedException.java:84) ~[pinot-all-0.10.0-SNAPSHOT-jar-with-dependencies.jar:0.10.0-SNAPSHOT-44c4b65b990e4e05dbca973f3d7073c89dc3dc65]
        at shaded.software.amazon.awssdk.core.exception.AbortedException.create(AbortedException.java:38) ~[pinot-all-0.10.0-SNAPSHOT-jar-with-dependencies.jar:0.10.0-SNAPSHOT-44c4b65b990e4e05dbca973f3d7073c89dc3dc65]
        at shaded.software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.handleInterruptedException(ApiCallTimeoutTrackingStage.java:143) ~[pinot-all-0.10.0-SNAPSHOT-jar-with-dependencies.jar:0.10.0-SNAPSHOT-44c4b65b990e4e05dbca973f3d7073c89dc3dc65]
        at shaded.software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.translatePipelineException(ApiCallTimeoutTrackingStage.java:107) ~[pinot-all-0.10.0-SNAPSHOT-jar-with-dependencies.jar:0.10.0-SNAPSHOT-44c4b65b990e4e05dbca973f3d7073c89dc3dc65]
        at shaded.software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:62) ~[pinot-all-0.10.0-SNAPSHOT-jar-with-dependencies.jar:0.10.0-SNAPSHOT-44c4b65b990e4e05dbca973f3d7073c89dc3dc65]
        at shaded.software.a

Is this normal mode of operation of kinesis consumer? It seems the threads gets aborted if there is nothing new to consume from stream. On querying, the table real time is returning the expected data and number of records, but server continuously logs this exception

I suppose @Neha Pawar and @Kartik Khare might know ^^

Hi, Yes this is normal. We have a fetchTimeout and once that timeout reaches the following exception gets logged and all the records received till that time are stored in Pinot. Nothing to worry about. I am working on removing stacktrace from this particular exception for now. Will be available in next patch.

Thanks for fixing this!