shounakmk219 commented on PR #13544: URL: https://github.com/apache/pinot/pull/13544#issuecomment-2213018935
@siddharthteotia > Does the DB level quota get even distributed across all tables in that DB ? The db level quota is separate from table level quota. Each table has it's separate quota and individually or cumulatively it may exceed the db level quota. But queries will be blocked once the db level quota is reached. Its upto the db admin to ensure proper table level quotas are provided so that tables don’t end up contesting for the db quota share. > On a related note, how does the math work for updating / maintaining and enforcing quotas when there is both table level and DB level quota configured ? Is there a precedent ? As mentioned above these 2 quotas are separate. For any incoming query both the table quota and db quota is checked and the query will fail if anyone of them is exceeding. > Can we add a new table to an existing DB where that table level quota is exceeding the DB level quota ? Yes. We don't enforce the rule that sum of all table quotas under a db must not exceed db quota. Cluster/DB maintainer should take the call on what table quota should be and what db quota should be. Not necessary all tables may reach their quota at the same time. DB quota just ensures that at any point the particular db is not running more than x queries and does not affect other DBs in the cluster. -- 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
