search

varun2784 / weed-fs

Automatically exported from code.google.com/p/weed-fs
0 stars 0 forks source link

'Now writable volumes avalable' error when master and volume nodes are on separate servers #16

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. sudo ./weed master (on fs1.example.com)

2. sudo ./weed volume -dir="/home/ubuntu/example" -max=1  
-mserver="fs1.example.com:9333" -port=8080  -publicUrl="fs2.example.com:8080" 
(on fs2.example.com)

3. curl http://fs1.example.com:9333/dir/assign

What is the expected output? What do you see instead?
{"error":"No writable volumes avalable!"}

What version of the product are you using? On what operating system?
weed-fs 0.27 Ubuntu 12.04.1 LTS running on Small instances on Amazon AWS

Please provide any additional information below.
'Now writable volumes avalable' error when master and volume nodes are on 
separate servers. But they work fine if the master and volume nodes are on the 
same server (using localhost like the examples).

Original issue reported on code.google.com by va...@semantics3.com on 28 Feb 2013 at 1:21

GoogleCodeExporter commented 8 years ago 
(Can't seem to edit my above issues :( )

ubuntu@ip-10-80-xxx-yyy:~$ sudo ./weed master
2013/02/28 13:16:05 Loading file id sequence 40000 => 50000
2013/02/28 13:16:05 Volume Size Limit is 32768 MB
2013/02/28 13:16:05 Start Weed Master 0.27 at port 9333

When a volume is added, following message appears.

topo adds child DefaultDataCenter
topo:DefaultDataCenter adds child DefaultRack
topo:DefaultDataCenter:DefaultRack adds child localhost:8080

Following error appears when trying to do curl 
http://fs1.example.com:9333/dir/assign

2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
2013/02/28 13:16:26 post to http://localhost:8080/admin/assign_volume dial tcp 
127.0.0.1:8080: connection refused
Failed to assign 1 to [topo:DefaultDataCenter:DefaultRack:localhost:8080]
No more writable volumes!

Original comment by va...@semantics3.com on 28 Feb 2013 at 1:26

GoogleCodeExporter commented 8 years ago 
Can you please try to use parameter "-ip=fs2.example.com"?

Original comment by chris...@gmail.com on 28 Feb 2013 at 7:01