Yes, there is a special system user which is used internally for the
!METADATA writes, as well as internal system calls, such as the scans the
Master does to keep consistency of the metadata table.
As for zookeeper, we also have ACLs in place to prevent external sources
from tampering or reading t
Thanks Eric, Corey got it to work easily with just the WRITE permission granted
to root.
So if root does not have write permission to METADATA, then how does the
accumulo server write to the METADATA table. Is there a server specific user
that is not visible to us?
Also, one thing we tried to
Offline the table. It may take some time for it to settle down. Start any
failed tservers.
Shutdown the accumulo garbage collector:
$ pkill -f =gc
Grant the root user the write permissions the !METADATA table:
shell> grant -u root -t !METADATA Table.WRITE
Find your table id:
shell> table
We have a sharded-event table that failed miserably when we accidentally tried
to merge all of the tablets together. When starting accumulo, the monitor page
says the event table (once having 43k tablets) now has 5 tablets and 1.05B
rows. There are 14.5k unassigned tablets, The tablet servers ea
