You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
version:2.65 linux amd64
Command: nohup weed server -ip=90.90.90.12 -dir=/mnt/vol/object_444/data_1 -s3 -s3.port=29000 -s3.allowEmptyFolder -volume.port=27000 -filer.port=28000 -volume.max=4294967295 &
I use cosbench to test performance of weed. When running the test , I quickly encountered two serious problems: 1) weed crashed
2) weed show no free volume left ,but --volume.max was set to 4294967295 . After restarting weed, the error disapperd, but a few minutes later ,it shows again. I used weed shell to list volumes, and found that the number of volume was increasing
Seems you need to wait a bit before throwing traffic. Seems there are many volumes and the volume server may take a longer time to start. The master did not receive the volumes information from the volume servers yet.
version:2.65 linux amd64
Command:
nohup weed server -ip=90.90.90.12 -dir=/mnt/vol/object_444/data_1 -s3 -s3.port=29000 -s3.allowEmptyFolder -volume.port=27000 -filer.port=28000 -volume.max=4294967295 &
I use cosbench to test performance of weed. When running the test , I quickly encountered two serious problems:
1) weed crashed
2) weed show no free volume left ,but --volume.max was set to 4294967295 . After restarting weed, the error disapperd, but a few minutes later ,it shows again. I used weed shell to list volumes, and found that the number of volume was increasing
Here is th weed log.
weed.log
The text was updated successfully, but these errors were encountered: