On Wed, Feb 13, 2013 at 1:30 PM, John Vines <[EMAIL PROTECTED]> wrote:
> I don't think your property is coming back because you're using
> getSiteConfiguration(). I believe that just spits back the configuration
> from the xml files. getSystemConfiguration() will return data as it is in
I totally missed that. You do need to call getSystemConfiguration().
I just went and looked at the code to be sure. Looking at the code,
I think you can still run into the issue I mentioned where you read
from a tablet server before the zookeeper event gets there.
getSystemConfiguration() also goes to random tablet server to read the
config. And following that through, it reads the config from a
ZooCache on the tablet server.
We really need javadoc for InstanceOperations.getSystemConfiguration()
> Zookeeper, which is where that property will be. I had no problems using
> the shell to set a non-existant property (with an allowable prefix), read
> it back, and then delete it.
> As for the error, that's a bit new to me. Check to make sure there's
> nothing in the master and tserver logs with it.
> 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.thrift.TApplicationException: Internal error processing
>> at org.apache.accumulo.core.client.impl.MasterClient.execute
>> This was all on a 1.5-SNAPSHOT I made this evening.