swarm manager restarted, which leds to service‘s last vip become service endpoint ip

[xjh1994]

Description

One day, my host with swarm manager restarted. Then I restart my docker when the system is ready.
After that, my service connection became unstable. 25% requests connect timed out.

After investigation, I found the network problem.

Run docker network inspect overlay10 -v

Or run nslookup tasks.serviceName

Describe the results you expected:
I want to know how to solve this.

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client:
 Version:           18.09.7
 API version:       1.39
 Go version:        go1.10.4
 Git commit:        2d0083d
 Built:             Fri Aug 16 14:19:38 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.09.7
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       2d0083d
  Built:            Thu Aug 15 15:12:41 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Output of docker info:

Containers: 37
 Running: 31
 Paused: 0
 Stopped: 6
Images: 27
Server Version: 18.09.7
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
 NodeID: xuh3mf9m54jzt15aqioecoeem
 Is Manager: true
 ClusterID: ancit9o5mi8ua42a76toa6nl9
 Managers: 1
 Nodes: 3
 Default Address Pool: 10.0.0.0/8  
 SubnetSize: 24
 Orchestration:
  Task History Retention Limit: 0
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 10
 Dispatcher:
  Heartbeat Period: 30 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: 10.9.9.157
 Manager Addresses:
  10.9.9.157:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 
runc version: N/A
init version: v0.18.0 (expected: fec3683b971d9c3ef73f284f176672c44b448662)
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-131-generic
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 31.42GiB
Name: etyyout1
ID: UPKC:M4G5:7GNI:DO3D:JWFH:JLWV:TXMH:EQIL:SFV5:2JIN:KFZW:AAPS
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Registry Mirrors:
 https://xma5o45r.mirror.aliyuncs.com/
Live Restore Enabled: false

WARNING: API is accessible on http://0.0.0.0:2375 without encryption.
         Access to the remote API is equivalent to root access on the host. Refer
         to the 'Docker daemon attack surface' section in the documentation for
         more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):

[thaJeztah]

@dperny PTAL

[xjh1994]

@thaJeztah @dperny Please let me know if you have any progress. Thanks!

[xjh1994]

And I found this in docker's log:
rmServiceBinding 6b2b065c02c558f5c99eb9b05381866b396a859c51f8ae4541138553902c464d possible transient state ok:false entries:0 set:false