You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2022/11/10 18:06:59 UTC

[GitHub] [pinot] klsince commented on pull request #9774: Fix the null pointer exception for segment assignment strategy in reassigning tiers (Table rebalance)

klsince commented on PR #9774:
URL: https://github.com/apache/pinot/pull/9774#issuecomment-1310689036

   Thanks for digging into this issue, @GSharayu @snleee !
   
   > ... we can enforce that COMPLETED instance partition needs to be configured if Tier is used...
   > ... We can improve the rebalance behavior when we have the clear idea if we really need to configure tiers without COMPLETED tenant.
   
   I didn't know there is need to configure a COMPLETED tenant. I see tenants are usually named like DefaultTenant_OFFLINE or DefaultTenant_REALTIME for different table types, as well as in the local test I did. Is the `DefaultTenant_REALTIME` used as CONSUMING and COMPLETED tenants for RT table by default? Feel free to point me to docs about those if any.
   
   > 2. Move all COMPLETED segments to Tiers after rebalance
   
   IIUC, this seems what I was assuming to happen: to move COMPLETED segments to new tier if they matches the selection criteria. And leave CONSUMING and other non-matching COMPLETED segments to the default tenant configured for the REALTIME table (DefaultTenant_REALTIME by default). 


-- 
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