[
https://issues.apache.org/jira/browse/KAFKA-16869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851341#comment-17851341
]
Muralidhar Basani commented on KAFKA-16869:
-------------------------------------------
Is it ok if I pick up this ?
With the reference of new StickyTaskAssignor and old HAAssignor, may be I can
try rewriting HAAssignor.
I see there are 5 mini tasks in overriding the assign method.
- assignActiveStatefulTasks
- assignStandbyReplicaTasks
- assignStatelessActiveTasks
- assignActiveTaskMovements
- assignStandbyTaskMovements
> Rewrite HighAvailabilityTaskAssignor to implement the new TaskAssignor
> interface
> --------------------------------------------------------------------------------
>
> Key: KAFKA-16869
> URL: https://issues.apache.org/jira/browse/KAFKA-16869
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Priority: Major
>
> We need to add a new HighAvailabilityTaskAssignor that implements the new
> TaskAssignor interface. Once we have that, we need to remember to also make
> these related changes:
> # Change the StreamsConfig.TASK_ASSIGNOR_CLASS_CONFIG default from null to
> the new HAAssignor
> # Check for this new HAAssignor type when evaluating the OptionalInt
> rack-aware assignment configs in the public AssignmentConfigs class. If these
> configs are Optional.empty() and the new HAAssignor is used, they should be
> overridden to the HAAssignor-specific default values. This code already
> exists but should be updated to check for the new HAAssignor class name
> instead of "null"
> # Until the old HAAssignor and old internal task assignor config can be
> removed completely, make sure the new HAAssignor is used by default when a
> TaskAssignor is selected in StreamsPartitionAssignor
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
