timer: make sure timer which has a max delay will be scheduled first (#57067)

[ti-chi-bot]

This is an automated cherry-pick of #57067

What problem does this PR solve?

Issue Number: close #57137

This issue is because a trigger action will be sent to the timer worker via the chan:

tidb/pkg/timer/runtime/runtime.go

Lines 285 to 300 in 6004c3e

	select {
	case <-rt.ctx.Done():
	return false
	case worker.ch <- req:
	rt.cache.setTimerProcStatus(timer.ID, procTriggering, eventID)
	default:
	if busyWorkers == nil {
	busyWorkers = make(map[string]struct{})
	}
	busyWorkers[timer.HookClass] = struct{}{}
	retryTimerIDs = append(retryTimerIDs, timer.ID)
	retryTimerKeys = append(retryTimerKeys, fmt.Sprintf("[%s] %s", timer.Namespace, timer.Key))
	}
	return true
	})

If the chan is full, it will fail and retry after a while. However, some tables always have lower priorities even if they are not triggered for a long time.

What changed and how does it work?

reorder timers by nextEventTime before sending them to workers to make sure the timer which has a max delay will be handled first to avoid starvation

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.

ttl: fix some times TTL job can not be scheduled when there are a lot of TTL tables.

[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 assign zhouqiang-cl for approval. 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/unit-test	63ab448	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev_2	63ab448	link	true	/test check-dev2
idc-jenkins-ci-tidb/mysql-test	63ab448	link	true	/test mysql-test
idc-jenkins-ci-tidb/build	63ab448	link	true	/test build
idc-jenkins-ci-tidb/check_dev	63ab448	link	true	/test check-dev

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.