If so, we can actually only include fragment ids in Command::Throttle, and in global barrier worker when we handle the command, we then directly use inflight actor info maintained in the worker.
Furthermore, we have to include actor id in the throttle mutation because in streaming executor, we always check throttle config update by actor id. If so, we can actually change check by fragment id, and then in throttle mutation we only need to include the fragment id, and then we don't have to resolve the actor ids of fragments. I believe in many logic of altering streaming job config, (e.g. logic that use Throttle and ConnectorPropsChange mutation), we can change from check by actor id to check by fragment id to avoid having to resolve actor ids of fragment by shared actor info.
Originally posted by @wenym1 in #22932 (comment)