sylph-eu opened a new pull request, #10746: URL: https://github.com/apache/pinot/pull/10746
**Context** Upon registering (pushing) metadata for offline segment the latter is unconditionally assigned to servers defined by `tenants.server` property, without considering `tierConfigs`. Only on rebalance (triggered by SegmentRelocator job) it will be "moved" to a proper tenant/tier. This behavior is not really convenient when table is refilled regularly as segments will initially end up in default "warm" tier, while preferably they shall be properly distributed from the very start. This change, controlled by a flag, fixes this behaviour and allows the segment to reside in a proper tenant/tier upon assignment. **Changes** 1. Introduce new controller setting `controller.segment.enableTieredAssignment` that enables direct tenant/tier assignment. 2. Change interface of `SegmentAssigner.assignSegment` method to become similar to `rebalanceTable` one. Only implementation for OFFLINE segments has been customized. REALTIME segments are assigned as before. 3. Implemented a couple of unit tests to validate the behaviour. cc: @klsince -- 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
