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
I found some minor mistakes of shell scripts in sandbox directory.
"$1"x == "master_slave" extra x is missed in master_slave
when adopting raft mode, sleep 5 seconds is not enough for the system to run. I encounted bfs_client put error when deploying raft mode by sleep 5-10 seconds.
I think it is not good to show process not found when running clear.sh. Killing the process should work without any error message. For the new guy like me to run deploy.sh and get the message process not found, I think there is something wrong with the deploy.sh. However, it works OK.
cd - will print current work directory when using start_bfs.sh. I also think this log is unnecessary. It doesn't give any useful information about the system. But the logs like nameserver 0 started ok at port xxx, chunkserver 0 started ok at port xxx should be added into the script, to make it more clear.
The text was updated successfully, but these errors were encountered:
lpstudy
added a commit
to lpstudy/bfs
that referenced
this issue
Jun 1, 2017
(baidu#897)
deploy.sh: extra x in "$1"x == "master_slave". Also add `-h` option which is common in linux shell scripts.
start_bfs.sh: bfs can not work well with raft mode enabled with only sleeping 5 seconds, add 'sleep 30' when using raft mode.
clear.sh: redirect the error log message like `process not found` to `/dev/null`. It does no good but confuses the users.
start_bfs.sh: `cd -` print the working directory which is useless. Add the server starting message like `start nameserver0 with pid xxx`
I found some minor mistakes of shell scripts in sandbox directory.
process not found
, I think there is something wrong with the deploy.sh. However, it works OK.cd -
will print current work directory when usingstart_bfs.sh
. I also think this log is unnecessary. It doesn't give any useful information about the system. But the logs likenameserver 0 started ok at port xxx, chunkserver 0 started ok at port xxx
should be added into the script, to make it more clear.The text was updated successfully, but these errors were encountered: