You can overcome this limitation by using the dfs.permissions.superusergroup setting in hdfs-site.xml. Just set it to a group that Accumulo is part of (any anyone else you want to have access). I usually use the "hadoop" group. The default value is "supergroup".
On Tue, Jul 10, 2012 at 11:53 PM, Eric Newton <[email protected]> wrote: > Well, separating users is always a better security option, but you > just lose out on this monitoring option. > > I've just grown used to seeing it red. I can always click-through and > see the monitoring page for HDFS. > > > On Tue, Jul 10, 2012 at 11:10 PM, David Medinets > <[email protected]> wrote: > > You're right. I have 'hadoop', 'zookeeper' and 'accumulo' users. I > > should be running the accumulo processes as the hadoop user? > > > > On Tue, Jul 10, 2012 at 10:58 PM, Eric Newton <[email protected]> > wrote: > >> You are running accumulo with a different user than the HDFS "root" > >> user. The API restricts the status information if you aren't running > >> as that user. > >> > >> I'm trying to avoid turning Accumulo into a monitoring program, so > >> that's the best we can do as the ecosystem improves the security > >> model. > >> > >> -Eric > >> > >> On Tue, Jul 10, 2012 at 10:52 PM, David Medinets > >> <[email protected]> wrote: > >>> I am running Accumulo on a Linode server. I can run the shell from the > >>> ubuntu command line. It seems to work fine. All of the configuration > >>> uses localhost. The Accumulo monitor page is available at > >>> http://accumulo.affy.com:50095. If you visit, you'll see that the > >>> NameNode section shows "Permission Denied" and the "Accumulo Master" > >>> section is empty. Do you know what I could have configured > >>> incorrectly? >
