Hide Forgot
REVIEW: http://review.gluster.org/6005 (cli: add node uuid in rebalance and remove brick status xml output) posted (#1) for review on master by Bala FA (barumuga)
REVIEW: http://review.gluster.org/6005 (cli: add node uuid in rebalance and remove brick status xml output) posted (#2) for review on master by Bala FA (barumuga)
REVIEW: http://review.gluster.org/6032 (cli: add node uuid in rebalance and remove brick status xml output) posted (#1) for review on release-3.4 by Bala FA (barumuga)
COMMIT: http://review.gluster.org/6005 committed in master by Anand Avati (avati) ------ commit d9db4a8ff300012eee87f31d73e303862d2de9b6 Author: Bala.FA <barumuga> Date: Thu Sep 26 08:09:35 2013 +0530 cli: add node uuid in rebalance and remove brick status xml output This patch adds node uuid in rebalance/remove-brick status xml output. Output XML will look like <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <cliOutput> <opRet>0</opRet> <opErrno>0</opErrno> <opErrstr/> <volRebalance> <op>3</op> <nodeCount>1</nodeCount> <node> <nodeName>localhost</nodeName> ==>> <id>883626f8-4d29-4d02-8c5d-c9f48c5b2445</id> <files>0</files> <size>0</size> <lookups>0</lookups> <failures>0</failures> <status>3</status> <statusStr>completed</statusStr> </node> <aggregate> <files>0</files> <size>0</size> <lookups>0</lookups> <failures>0</failures> <status>3</status> <statusStr>completed</statusStr> </aggregate> </volRebalance> </cliOutput> Change-Id: I5a1d4f9043b33b9e88150647a243ddb16154e843 BUG: 1012296 Signed-off-by: Bala.FA <barumuga> Reviewed-on: http://review.gluster.org/6005 Reviewed-by: Kaushal M <kaushal> Tested-by: Gluster Build System <jenkins.com>
COMMIT: http://review.gluster.org/6032 committed in release-3.4 by Vijay Bellur (vbellur) ------ commit 437d51f42813299435c297e9c0a1312dcaf0a6f4 Author: Bala.FA <barumuga> Date: Thu Sep 26 08:09:35 2013 +0530 cli: add node uuid in rebalance and remove brick status xml output This patch adds node uuid in rebalance/remove-brick status xml output. Output XML will look like <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <cliOutput> <opRet>0</opRet> <opErrno>0</opErrno> <opErrstr/> <volRebalance> <op>3</op> <nodeCount>1</nodeCount> <node> <nodeName>localhost</nodeName> ==>> <id>883626f8-4d29-4d02-8c5d-c9f48c5b2445</id> <files>0</files> <size>0</size> <lookups>0</lookups> <failures>0</failures> <status>3</status> <statusStr>completed</statusStr> </node> <aggregate> <files>0</files> <size>0</size> <lookups>0</lookups> <failures>0</failures> <status>3</status> <statusStr>completed</statusStr> </aggregate> </volRebalance> </cliOutput> Change-Id: Ie2eb6e8d024605326d1a710b7c40ee30139f0f22 BUG: 1012296 Signed-off-by: Bala.FA <barumuga> Reviewed-on: http://review.gluster.org/6032 Reviewed-by: Kaushal M <kaushal> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
COMMIT: http://review.gluster.org/6331 committed in release-3.4 by Anand Avati (avati) ------ commit e412da34e927737efae711740191c59749214e9a Author: Bala.FA <barumuga> Date: Thu Nov 21 17:16:39 2013 +0530 cli: use proper copy to set node-name Previously node-name is set to point to node-uuid which could cause memory leak. This is fixed by having memory copy of node-uuid. BUG: 1012296 Change-Id: I4a7123771e2d8c31c5db4f78d022a9f4fbfc2667 Signed-off-by: Bala.FA <barumuga> Reviewed-on: http://review.gluster.org/6331 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
COMMIT: http://review.gluster.org/6330 committed in master by Anand Avati (avati) ------ commit 8690388bc7b3fe92c5dfc43a7173d5f05137e9cd Author: Bala.FA <barumuga> Date: Thu Nov 21 17:16:39 2013 +0530 cli: use proper copy to set node-name Previously node-name is set to point to node-uuid which could cause memory leak. This is fixed by having memory copy of node-uuid. BUG: 1012296 Change-Id: I3b638ec289d5b167c6e752ef1ba41f41efacb9da Signed-off-by: Bala.FA <barumuga> Reviewed-on: http://review.gluster.org/6330 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user