What steps will reproduce the problem?
1.Using the voldemort-admin-tool.sh from a 0.94 build ...
2.Do a --delete-store <store> on a bdb persistence store
3.Then do a --add-stores <stores.xml with the same store in it>
The store should be added, but instead the following exception is thrown:
voldemort.store.StoreOperationFailureException: Store '<storename>' already
exists on this server
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at voldemort.utils.ReflectUtils.callConstructor(ReflectUtils.java:116)
at voldemort.utils.ReflectUtils.callConstructor(ReflectUtils.java:103)
at voldemort.store.ErrorCodeMapper.getError(ErrorCodeMapper.java:70)
at voldemort.client.protocol.admin.AdminClient.throwException(AdminClient.java:1153)
at voldemort.client.protocol.admin.AdminClient.addStore(AdminClient.java:1493)
at voldemort.client.protocol.admin.AdminClient.addStore(AdminClient.java:1462)
at voldemort.VoldemortAdminTool.executeAddStores(VoldemortAdminTool.java:855)
at voldemort.VoldemortAdminTool.main(VoldemortAdminTool.java:334)
Store '<storename>' already exists on this server
Even after waiting a few minutes the store can still not be added. Was
resolved by bouncing the cluster and then adding the store after the bounce.
Running voldemort 0.94 on Solaris 10 Generic 142910-17 i386
Brendan
Original issue reported on code.google.com by dremlok on 10 Sep 2011 at 5:10
Original issue reported on code.google.com by
dremlok
on 10 Sep 2011 at 5:10