maytasm commented on PR #12944: URL: https://github.com/apache/druid/pull/12944#issuecomment-2784932317
@rohangarg @abhishekagarwal87 @clintropolis I hate to add very specific checks but another case we ran into is a user issuing a timeseries query with none granularity type. The time range of the query is only 1 week but ended up OOM a lot of the historical nodes. The none granularity is arguably a user error (bad query) but we should still make sure the impact isn't wide spread temporary cluster outage. Should we either add another check to prevent none granularity? (is there any real use case where none granularity would make sense?) or as @rohangarg earlier suggested, cap the number of time-grains possible to create? -- 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]
