-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
lost volume server always after Volume xyz becomes unwritable #499
Comments
Volume server 10.1.14.22:8082 logs from the same time : |
Added a possible fix. |
We're rerunning our tests now and so far so good :) I'll report back later when the test completes |
closing. |
Hi
We're seeing very frequest volume server disconnects. I've tried running the master with different pulseSeconds. The latest attempt was master with pulseSeconds=60 and volumes with pulseSeconds=1 ( based on #408 )
As far as I can tell it always happens after volumes become unwritable:
I0523 20:52:43 12295 volume_layout.go:203] Volume 188233 becomes unwritable
I0523 20:52:43 12295 volume_layout.go:203] Volume 188232 becomes unwritable
I0523 20:52:43 12295 volume_layout.go:203] Volume 188234 becomes unwritable
I0523 20:52:43 12295 volume_layout.go:203] Volume 188235 becomes unwritable
I0523 20:52:43 12295 volume_layout.go:203] Volume 188236 becomes unwritable
I0523 20:52:44 12295 master_grpc_server.go:63] lost volume server 10.1.14.22:8082
I0523 20:52:44 12295 topology_event_handling.go:52] Removing Volume 1241 from the dead volume server 10.1.14.22:8082
I0523 20:52:44 12295 volume_layout.go:227] Volume 1241 has 0 replica, less than required 2
I0523 20:52:44 12295 topology_event_handling.go:52] Removing Volume 1541 from the dead volume server 10.1.14.22:8082
I0523 20:52:44 12295 volume_layout.go:227] Volume 1541 has 1 replica, less than required 2
.
.
I0523 20:53:59 12295 node.go:237] topo:DefaultDataCenter:DefaultRack removes 10.1.14.22:8082
.
.
I0523 20:54:00 12295 volume_growth.go:205] Created Volume 188240 on 10.1.14.27:8080
I0523 20:54:00 12295 volume_growth.go:205] Created Volume 188241 on topo:DefaultDataCenter:DefaultRack:10.1.14.24:8081
I0523 20:54:00 12295 volume_growth.go:205] Created Volume 188241 on topo:DefaultDataCenter:DefaultRack:10.1.14.23:8081
I0523 20:54:00 12295 volume_growth.go:205] Created Volume 188242 on topo:DefaultDataCenter:DefaultRack:10.1.14.23:8083
I0523 20:54:00 12295 volume_growth.go:205] Created Volume 188242 on topo:DefaultDataCenter:DefaultRack:10.1.14.27:8083
I0523 20:54:00 12295 node.go:223] topo:DefaultDataCenter:DefaultRack adds child 10.1.14.22:8082
I0523 20:54:00 12295 master_grpc_server.go:36] added volume server 10.1.14.22:8082
I0523 20:54:00 12295 node.go:223] topo:DefaultDataCenter:DefaultRack adds child 10.1.14.24:8083
I0523 20:54:00 12295 master_grpc_server.go:36] added volume server 10.1.14.24:8083
I0523 20:54:00 12295 volume_layout.go:203] Volume 187989 becomes unwritable
I0523 20:54:00 12295 volume_layout.go:203] Volume 187519 becomes unwritable
I0523 20:54:01 12295 node.go:223] topo:DefaultDataCenter:DefaultRack adds child 10.1.14.27:8080
I0523 20:54:01 12295 master_grpc_server.go:36] added volume server 10.1.14.27:8080
The text was updated successfully, but these errors were encountered: