最新版的编译后，在dashboard里切换proxy的状态，没有效果 about codis HOT 15 CLOSED

can you send proxy's log and dashboard's log to me ? thanks
[email protected]

from codis.

ok，已经发送了，日志里时间可能不对，测试机没有调过机器时间

from codis.

looks good in logs, can you reproduce this problem ?

from codis.

i'll check it

from codis.

I excecute this command below:
[root@node3 codis]# bin/codis-config proxy offline proxy_1
2014/12/30 01:42:20 main.go:135: [info] living node created: /zk/codis/db_test/living-codis-config/node3-10874
2014/12/30 01:58:04 proxy.go:167: [info] mark_offline, check proxy status: proxy_1 &{proxy_1 node3:19000 0 mark_offline node3:11000}
2014/12/30 01:58:09 proxy.go:167: [info] mark_offline, check proxy status: proxy_1 &{proxy_1 node3:19000 0 mark_offline node3:11000}
2014/12/30 02:06:11 proxy.go:167: [info] mark_offline, check proxy status: proxy_1 &{proxy_1 node3:19000 0 mark_offline node3:11000}

The comand still runing,no exit.

The status of proxy :

from codis.

please check your zk: /zk/codis/db_test/LOCK , is there any remainig lock?

from codis.

bug confirmed

from codis.

fixed, please checkout the newest version, and execute make again, before starting dashboard.

from codis.

yes,zookeeper has remaind the lock;
[zk: localhost:2181(CONNECTED) 2] ls /zk/codis/db_test/LOCK
[lock-0000000000]
thanks for you fixed.

from codis.

did it work?

from codis.

在dashboard里切换proxy的状态现在是可以的，但是手动执行bin/codis-config proxy offline proxy_1，命令一直没有退出

from codis.

see ls /zk/codis/db_test/LOCK
then get /zk/codis/db_test/LOCK/xxx

from codis.

@wu0407 ping

from codis.

pong ！
NOW,the comand is running ok,but proxy exit,in the last version.

[root@node3 codis]# bin/codis-config proxy offline proxy_1
2015/01/09 02:17:59 main.go:135: [info] living node created: /zk/codis/db_test/living-codis-config/node3-22407
2015/01/09 02:17:59 proxy.go:167: [info] mark_offline, check proxy status: proxy_1 zk: node does not exist
2015/01/09 02:17:59 proxy.go:169: [info] shutdown proxy successful
[2]+ Exit 255 bin/codis-proxy -L /tmp/proxy-codis.log --cpu=2 --addr=0.0.0.0:19000 --http-addr=0.0.0.0:11000

from codis.

It's ok. The behaviour of "set proxy offline" is shutdown proxy.
we may need to reconsider the name of "offline"

from codis.