Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TaskListPartitionConfig message to proto #6358

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

Shaddoll
Copy link
Member

@Shaddoll Shaddoll commented Oct 14, 2024

Detailed Description
Introduce a new type TaskListPartitionConfig to protobuf and add the new type as a new field to the following proto messages:

  • AddActivityTaskResponse
  • AddDecisionTaskResponse
  • PollForActivityTaskResponse
  • PollForDecisionTaskResponse

Impact Analysis

  • Backward Compatibility: It's backward compatible
  • Forward Compatibility: It's forward compatible

Testing Plan

  • Unit Tests: Yes
  • Persistence Tests: No.
  • Integration Tests: Yes
  • Compatibility Tests: No.

Rollout Plan

  • What is the rollout plan? No special rollout plan.
  • Does the order of deployment matter? No.
  • Is it safe to rollback? Does the order of rollback matter? It's safe to rollback.
  • Is there a kill switch to mitigate the impact immediately? No.

Thrift is not updated because the AddXXXTask methods return void. Besides, we're going to deprecate thrift and tchannel. So the decision is to add less feature support for thrift.

Copy link

codecov bot commented Oct 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.50%. Comparing base (a32159c) to head (d4b6655).
Report is 14 commits behind head on master.

Additional details and impacted files
Files with missing lines Coverage Δ
client/matching/client.go 90.55% <100.00%> (ø)
common/types/mapper/proto/matching.go 95.81% <100.00%> (+0.46%) ⬆️
common/types/matching.go 0.00% <ø> (ø)
...xecution/mutable_state_builder_methods_activity.go 81.29% <100.00%> (ø)
service/history/task/timer_active_task_executor.go 72.64% <100.00%> (+0.05%) ⬆️
...ervice/history/task/transfer_task_executor_base.go 80.80% <100.00%> (+0.15%) ⬆️
service/matching/handler/handler.go 100.00% <100.00%> (ø)
service/matching/tasklist/forwarder.go 95.51% <100.00%> (ø)

... and 5 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a32159c...d4b6655. Read the comment docs.

@@ -290,7 +290,7 @@ func (e *mutableStateBuilder) tryDispatchActivityTask(
metrics.WorkflowTypeTag(e.GetWorkflowType().Name),
metrics.TaskListTag(ai.TaskList))
taggedScope.IncCounter(metrics.DecisionTypeScheduleActivityDispatchCounter)
err := e.shard.GetService().GetMatchingClient().AddActivityTask(ctx, &types.AddActivityTaskRequest{
_, err := e.shard.GetService().GetMatchingClient().AddActivityTask(ctx, &types.AddActivityTaskRequest{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At which layer we will be caching these results and make use of it? If it's going to be done by a matching client wrapper then we probably don't need to change matching.Client interface and the callers wouldn't change. I may be missing something (later review)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's done in matching.Client. Since I've made the change, let's keep it. It's always better to have an empty response than void

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed offline. We may actually need this response to record the identity of Started tasks for a feature that reduces amount of transfer tasks.

@Shaddoll Shaddoll merged commit ef546af into cadence-workflow:master Oct 18, 2024
21 checks passed
@Shaddoll Shaddoll deleted the config branch October 18, 2024 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants