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

*: move config file option oom-action to sysvar #34644

Merged
merged 2 commits into from
May 18, 2022

Conversation

ramanich1
Copy link
Collaborator

What problem does this PR solve?

Issue Number: ref #33769

Problem Summary:

The option oom-action has historically been a config option. But based on requirements from cloud & PM it should instead be a sysvar.

What is changed and how it works?

Check List

Tests

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

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility
    This might be a bit confusing during upgrade for users who have previously set oom-action(most users haven't). It needs to be documented in the release notes that it has been replaced with the system variable tidb_mem_oom_action.

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.

The TiDB configuration file option `oom-action` has been replaced by the system variable `tidb_mem_oom_action`. This change makes it easier to modify this setting on a cluster wide basis.

@ramanich1 ramanich1 requested a review from a team as a code owner May 13, 2022 19:09
@ti-chi-bot
Copy link
Member

ti-chi-bot commented May 13, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • morgo
  • tangenta

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label May 13, 2022
@sre-bot
Copy link
Contributor

sre-bot commented May 13, 2022

CLA assistant check
All committers have signed the CLA.

@ti-chi-bot ti-chi-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 13, 2022
@sre-bot
Copy link
Contributor

sre-bot commented May 13, 2022

Please follow PR Title Format:

  • pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

  • *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

@morgo morgo changed the title move config file option oom-action to sysvar *: move config file option oom-action to sysvar May 13, 2022
@morgo
Copy link
Contributor

morgo commented May 13, 2022

/run-check_title

@morgo
Copy link
Contributor

morgo commented May 13, 2022

Check_dev looks like simple linter issues:

[2022-05-13T19:13:01.230Z] linting
[2022-05-13T19:13:01.230Z]   ✘  https://revive.run/r#exported  comment on exported const OOMActionCancel should be of the form "OOMActionCancel ..."  
[2022-05-13T19:13:01.230Z]   sessionctx/variable/variable.go:78:2
[2022-05-13T19:13:01.230Z] 
[2022-05-13T19:13:01.230Z]   ✘  https://revive.run/r#exported  exported const OOMActionLog should have comment (or a comment on this block) or be unexported  
[2022-05-13T19:13:01.230Z]   sessionctx/variable/variable.go:80:2
[2022-05-13T19:13:01.230Z] 
[2022-05-13T19:13:01.230Z] ✘ 2 problems (2 errors, 0 warnings)
[2022-05-13T19:13:01.230Z] 
[2022-05-13T19:13:01.230Z] Errors:
[2022-05-13T19:13:01.230Z]   2  exported  

It looks like there is a test broken as well:

2022-05-13T19:17:20.821Z] ----------------------------------------------------------------------

[2022-05-13T19:17:20.821Z] FAIL: session_legacy_test.go:3123: testSessionSerialSuite.TestCoprocessorOOMAction

[2022-05-13T19:17:20.821Z] 

[2022-05-13T19:17:20.821Z] enable OOM, testcase: keep Order

[2022-05-13T19:17:20.821Z] disable OOM, testcase: keep Order

[2022-05-13T19:17:20.821Z] session_legacy_test.go:3196:

[2022-05-13T19:17:20.821Z]     disableOOM(tk, testcase.name, testcase.sql)

[2022-05-13T19:17:20.821Z] session_legacy_test.go:3184:

[2022-05-13T19:17:20.821Z]     c.Assert(err, NotNil)

[2022-05-13T19:17:20.821Z] ... value = nil

[2022-05-13T19:17:20.821Z] 

@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 13, 2022
@ti-chi-bot ti-chi-bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 16, 2022
@sre-bot
Copy link
Contributor

sre-bot commented May 16, 2022

@ti-chi-bot ti-chi-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels May 16, 2022
@morgo morgo self-requested a review May 16, 2022 19:57
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 17, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels May 17, 2022
@tangenta
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 9db3590badd97e5229c19f9bcc9331b05ce3550f

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 17, 2022
@bb7133 bb7133 added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 17, 2022
@morgo morgo mentioned this pull request May 17, 2022
12 tasks
@bb7133
Copy link
Member

bb7133 commented May 18, 2022

/unhold

@ti-chi-bot ti-chi-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 18, 2022
@bb7133
Copy link
Member

bb7133 commented May 18, 2022

/merge

@tangenta
Copy link
Contributor

Reopen it to wake "license/cla" up.

@tangenta tangenta closed this May 18, 2022
@tangenta tangenta reopened this May 18, 2022
@bb7133
Copy link
Member

bb7133 commented May 18, 2022

/merge

@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 18, 2022
@ti-chi-bot ti-chi-bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed status/can-merge Indicates a PR has been approved by a committer. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 18, 2022
@ti-chi-bot ti-chi-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels May 18, 2022
@morgo
Copy link
Contributor

morgo commented May 18, 2022

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: e2e97ec

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 18, 2022
@ti-chi-bot ti-chi-bot merged commit a961485 into pingcap:master May 18, 2022
@sre-bot
Copy link
Contributor

sre-bot commented May 18, 2022

TiDB MergeCI notify

🔴 Bad News! New failing [1] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name Result Duration Compare with Parent commit
idc-jenkins-ci/integration-cdc-test 🟥 failed 1, success 33, total 34 22 min New failing
idc-jenkins-ci-tidb/integration-common-test ✅ all 11 tests passed 10 min Fixed
idc-jenkins-ci-tidb/common-test 🟢 all 12 tests passed 5 min 12 sec Existing passed
idc-jenkins-ci-tidb/integration-ddl-test 🟢 all 6 tests passed 5 min 2 sec Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2 🟢 all 28 tests passed 5 min 2 sec Existing passed
idc-jenkins-ci-tidb/tics-test 🟢 all 1 tests passed 4 min 51 sec Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1 🟢 all 26 tests passed 4 min 22 sec Existing passed
idc-jenkins-ci-tidb/mybatis-test 🟢 all 1 tests passed 3 min 32 sec Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test 🟢 all 1 tests passed 2 min 53 sec Existing passed
idc-jenkins-ci-tidb/plugin-test 🟢 build success, plugin test success 4min Existing passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants