You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by "xiangfu0 (via GitHub)" <gi...@apache.org> on 2025/05/07 07:10:56 UTC
[I] Add a new broker routing strategy for CONSUMING segments results consistence [pinot]
xiangfu0 opened a new issue, #15727:
URL: https://github.com/apache/pinot/issues/15727
For a realtime table with >=2 replicas, the broker routing may hit any CONSUMING segment, which might cause user side to see inconsistent results due the consuming speed.
I feel we should allow a definition from controller for the lead consuming server for a table partition, then the new routing strategy should always use this lead CONSUMING segment across all replicas and then always query this segment.
--
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-unsubscribe@pinot.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
Re: [I] Add a new broker routing strategy to handle Realtime table query results consistency issue [pinot]
Posted by "npawar (via GitHub)" <gi...@apache.org>.
npawar commented on issue #15727:
URL: https://github.com/apache/pinot/issues/15727#issuecomment-2908118108
@xiangfu0 what you need is already addressed by this i think? https://github.com/apache/pinot/pull/12276
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
Re: [I] Add a new broker routing strategy to handle Realtime table query results consistency issue [pinot]
Posted by "Jackie-Jiang (via GitHub)" <gi...@apache.org>.
Jackie-Jiang commented on issue #15727:
URL: https://github.com/apache/pinot/issues/15727#issuecomment-2860485583
Nice initiative!
Querying one single replica would cause hotspot, and for strict replica routing (e.g. upsert), the entire replica of the table becomes hotspot. I remember having another similar discussion, where we can associate a certain client id to a replica, so that queries from multiple clients can be distributed to multiple replicas.
This feature (#14572) can also be used to pick a certain replica to serve the query
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
Re: [I] Add a new broker routing strategy to handle Realtime table query results consistency issue [pinot]
Posted by "hpvd (via GitHub)" <gi...@apache.org>.
hpvd commented on issue #15727:
URL: https://github.com/apache/pinot/issues/15727#issuecomment-2857439064
+1 of this
just an example I experienced last week (even if not the standard usecase of pinot):
changed the password on a huge payment provider, but login was not possible with new passwordt.
Changed again with forget password function and 2nd new one doesn’t work either.
When thinking of eventual consistency I tried the first one, it works.
2min later the first one doesn’t work any more but the second...
Extremely annoying - will raise lots of support request :-(
Its the same when "only" doing user faced analytics, their will be people thinking system is not working...
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
Re: [I] Add a new broker routing strategy to handle Realtime table query results consistency issue [pinot]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #15727:
URL: https://github.com/apache/pinot/issues/15727#issuecomment-5769483523
This issue has been closed because it has been inactive for 180 days. If you believe this issue is still relevant, please feel free to reopen it or create a new issue. Thank you!
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
Re: [I] Add a new broker routing strategy to handle Realtime table query results consistency issue [pinot]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #15727: Add a new broker routing strategy to handle Realtime table query results consistency issue
URL: https://github.com/apache/pinot/issues/15727
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org
Re: [I] Add a new broker routing strategy to handle Realtime table query results consistency issue [pinot]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #15727:
URL: https://github.com/apache/pinot/issues/15727#issuecomment-5335834616
This issue has been automatically marked as stale because it has not had any activity in the last 150 days. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
--
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-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org