br: no domain to run log command (#52127)

[ti-chi-bot]

This is an automated cherry-pick of #52127

What problem does this PR solve?

Issue Number: close #52088

Problem Summary:
no need to start domain for br log operation

What changed and how does it work?

don't run domain when use log start/stop... command.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from leavrth, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev_2	760b68c	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	760b68c	link	true	/test check-dev
idc-jenkins-ci-tidb/build	760b68c	link	true	/test build
idc-jenkins-ci-tidb/unit-test	760b68c	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	760b68c	link	true	/test mysql-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[Leavrth]

we need to use the sessionctx to check whether the ddl ingest job exists.