Jackie-Jiang opened a new pull request, #14334: URL: https://github.com/apache/pinot/pull/14334
In #11380 we introduced the mechanism to handle the case when a table is deleted then immediately recreated. Even though it can prevent adding segment to the old table data manager, it still has the following caveats: - If an EV is recreated within the check interval (1 second by default), it is still possible that the old table data manager remains, which will throw exception on the new segment loading - Current approach requires constant ZK pulling to verify if EV still exists, which can add extra load to ZK This PR introduced a cache for deleted tables, and remove the table data manager immediately without waiting for EV to disappear when server receives the delete table message. When a new segment needs to be loaded, check the table config creation time to ensure the table is re-created after old table is deleted. -- 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
