Jackie-Jiang commented on issue #15675: URL: https://github.com/apache/pinot/issues/15675#issuecomment-2864564570
> We want to solve this problem for 2 cases: 1. SegmentRefresh 2. Server Restarts. Is the idea here to fork out the queries to additional servers but not use the result from these servers when the query option is passed? That way the page-cache on these servers get warmed up? How can we detect server restarts and how can we control consistent push segment refreshes to happen only on certain replicas? > > Btw, the solution outlined by Praveen is already deployed at LinkedIn and we've seen good results. Praveen has shared the results above. Yes, that is the idea. The goal is to make this easier to use and maintain for OSS users. Maintaining a separate offline-flow outside of Pinto would be too complicated for general users. I believe it is also an overhead for LinkedIn. This is not a blocker, but IMO a good improvement to your existing solution. -- 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
