[PR] Use higher fetch timeout for Kinesis [pinot]

[via GitHub]

KKcorps opened a new pull request, #12214:
URL: https://github.com/apache/pinot/pull/12214

   Currently, we run into a scenario where KinesisConsumer gets stuck due to 
timeouts.
   
   The scenario is explained in the attached diagram
   
   ![Getting Started_ Boards (1) 
(1)](https://github.com/apache/pinot/assets/5559703/470a74c8-bef2-40d8-8dc9-b3b88930bc67)
   
   
   The temporary solution is to increase the timeout of kinesis. A more 
permanent solution would be to modify the fetchRecords method to accept a 
`emitter` function that can be called from a forever running while loop to push 
the data.
   


-- 
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: commits-unsubscr...@pinot.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org