bharadwajrembar opened a new issue #11422: URL: https://github.com/apache/druid/issues/11422
We are running Druid 0.19.1. The scenario arises when we fire a Scan query to read all rows for a given day (typically around 1mill records, takes around 10-15 min to complete) from the datasource. We observe that if there are N records for that given day, sometimes it will read <N records and throws no errors/timeouts resulting in a mismatch of data. We believe Druid is closing the connection gracefully. Is there a definite way to find out the same? We have set a very high query timeout on all of our components as well (around 60min). -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
