I poked around and look at the code for InstanceOperations.getSiteConfiguration() and InstanceOperations.setProperty(). I think this is a bug.
setProperty() ask the master to set the prop. getSiteConfiguration( ) reads the config from a random tablet servers. So if you call set and then get, then you are probably beating the zookeeper even to the tablet server. Can you open a bug? A simple fix may be to read the site config from the master. On Tue, Feb 12, 2013 at 9:10 PM, Jim Klucar <[email protected]> wrote: > I'm not sure if this is a MiniAccumulo or an InstanceOperations or a me > problem. If I do a InstanceOperations.setProperty followed by a > getSiteConfiguration, my property isn't there. Does it have to be a > pre-defined property? > > More concerning if I do a removeProperty of the property I'm setting, I'm > seeing this: > > org.apache.accumulo.core.client.AccumuloException: > org.apache.thrift.TApplicationException: Internal error processing > removeSystemProperty > at org.apache.accumulo.core.client.impl.MasterClient.execute > (MasterClient.java:123) > > org.apache.accumulo.core.client.admin.InstanceOperationsImpl.removeProperty > (InstanceOperationsImpl.java:86) > sun.reflect.NativeMethodAccessorImpl.invoke0 > (NativeMethodAccessorImpl.java:-2) > sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:57) > sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > > This was all on a 1.5-SNAPSHOT I made this evening.
