*: last bound source is prior to other source when pick for bound (#1373)

[ti-srebot]

cherry-pick #1373 to release-2.0
You can switch your code base to this Pull Request by using git-extras:

# In dm repo:
git pr https://github.com/pingcap/dm/pull/1397

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/dm.git pr/1397:release-2.0-673fb1b7069b

---

What problem does this PR solve?

similar to #1044

when DM cluster restarts, worker is not likely keepalive when master goes to below logic, because etcd is in masters

dm/dm/master/scheduler/scheduler.go

Lines 924 to 936 in 49223f3

	// set the stage as Free if it's keep alive.
	if _, ok := kam[name]; ok {
	w.ToFree()
	// set the stage as Bound and record the bound relationship if exists.
	if bound, ok := sbm[name]; ok {
	boundsToTrigger = append(boundsToTrigger, bound)
	err2 = s.updateStatusForBound(w, bound)
	if err2 != nil {
	return 0, err2
	}
	delete(sbm, name)
	}
	}

so worker is likely bounded to another source rather than its last source.

What is changed and how it works?

we always save a lastBound when do bounding, and not delete it. so when tryBoundForWorker, we could prefer selecting the last bound source for worker.

Also, if user didn't deploy more workers than sources, the bound relationship will not change (I hope)

Check List

Tests

• Unit test
• Integration test

Code changes

• Has persistent data change

Side effects

Related changes

• Need to cherry-pick to the release branch

[lichunzhu]

LGTM