seaweedfs: [bug:filer] Trying to connect to the old filler address

Trying to connect to the old filler address

I1230 08:30:44     1 meta_aggregator.go:190] subscribing remote 10.106.97.138:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.106.97.138:19090: connect: connection refused"

IP address 10.106.97.138:9090 not in cluster

> cluster.ps
the cluster has 8 filers
  * 10.103.39.184:9090 (8000GB 2.82 b7cd5263)
  * 10.106.97.170:9090 (8000GB 2.82 b7cd5263)
  * 10.106.97.173:9090 (8000GB 2.82 b7cd5263)
  * 10.106.97.221:9090 (8000GB 2.82 b7cd5263)
  * 10.103.39.160:9090 (8000GB 2.82 b7cd5263)
  * 10.103.39.190:9090 (8000GB 2.82 b7cd5263)
  * 10.103.39.151:9090 (8000GB 2.82 b7cd5263)
  * 10.106.97.152:9090 (8000GB 2.82 b7cd5263)

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 1
Comments: 16 (11 by maintainers)

Commits related to this issue

remove duplicated metadata subscription in filer https://github.com/chrislusf/seaweedfs/issues/2545 — committed to seaweedfs/seaweedfs by chrislusf 3 years ago
avoid connect to the old filler address https://github.com/chrislusf/seaweedfs/issues/2545 — committed to kmlebedev/seaweedfs by kmlebedev 2 years ago
Revert "remove duplicated metadata subscription in filer" This reverts commit 34742be0295998c2105a5ee50e3e77ef2397c403. Related to https://github.com/chrislusf/seaweedfs/issues/2545 — committed to seaweedfs/seaweedfs by chrislusf 2 years ago

Most upvoted comments

Not sure how easy it is to reproduce this. I added a possible fix to avoid duplicated subscription. Please help to verify whether it helps.

@chrislusf Fix did not help

filer version 2.86

I0118 09:56:50     1 meta_aggregator.go:203] subscribing remote 10.103.39.184:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.103.39.184:19090: connect: connection refused"
I0118 09:56:50     1 meta_aggregator.go:203] subscribing remote 10.106.97.196:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.106.97.196:19090: connect: connection refused"
I0118 09:56:45     1 meta_aggregator.go:203] subscribing remote 10.106.97.196:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.106.97.196:19090: connect: connection refused"
I0118 09:56:47     1 meta_aggregator.go:203] subscribing remote 10.103.39.184:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.103.39.184:19090: connect: connection refused"
I0118 09:56:47     1 meta_aggregator.go:203] subscribing remote 10.106.97.196:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.106.97.196:19090: connect: connection refused"
I0118 09:56:48     1 meta_aggregator.go:203] subscribing remote 10.103.39.184:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.103.39.184:19090: connect: I0118 09:56:52     1 meta_aggregator.go:203] subscribing remote 10.103.39.184:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.103.39.184:19090: connect: connection refused"
I0118 09:56:52     1 meta_aggregator.go:203] subscribing remote 10.106.97.196:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.106.97.196:19090: connect: connection refused"
I0118 09:56:54     1 meta_aggregator.go:203] subscribing remote 10.103.39.184:9090 meta change: subscribe: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 10.103.39.184:19090: connect: connection refused"

the cluster has 8 filers
  * 10.103.39.160:9090 (8000GB 2.86 05c3c3f5)
  * 10.103.39.151:9090 (8000GB 2.86 05c3c3f5)
  * 10.106.97.178:9090 (8000GB 2.86 05c3c3f5)
  * 10.106.97.173:9090 (8000GB 2.86 05c3c3f5)
  * 10.106.97.213:9090 (8000GB 2.86 05c3c3f5)
  * 10.106.97.152:9090 (8000GB 2.86 05c3c3f5)
  * 10.103.39.190:9090 (8000GB 2.86 05c3c3f5)
  * 10.103.39.172:9090 (8000GB 2.86 05c3c3f5)

kmlebedev on Jan 18, 2022