That did the trick. Thanks!
On 08/06/2012 06:31 AM, Eric Newton wrote:
In the zkCli.sh utility, you would add the appropriate auths like this: > addauth digest accumulo:passwd Where passwd is the value configured for instance.secret. -Eric On Sun, Aug 5, 2012 at 10:58 PM, Josh Elser<[email protected]> wrote:In regards to ACCUMULO-716, I'm having some issues "gracefully" recovering from a corrupt WAL file (read-as, I don't want to blow away ZK and reinitialize). I moved the bad file in HDFS out of ${instance.dfs.dir}/wal and then attempted to update zookeeper to remove the entry for that bad file, e.g. /accumulo/${instance.id}/root_**tablet/walogs/bad-file. I couldn't get around the lack of authorization to delete the file via zkCli nor could I replicate the deletion logic piecing together Accumulo code. Is there a utility I missed somewhere that launches a ZK shell with the correct credentials with which I could actually manipulate the protected data? If memory serves me, the ZK authorization I was missing is related to the root username/password for the instance. Is this actually the case or did I dream that up? If so, something like `addauth digest root:mypassword`? Thanks!
