Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo, mail # user - Accumulo On MapR


Copy link to this message
-
Re: Accumulo On MapR
Jason Trost 2012-03-26, 12:02
Todd,

Did you gather any performance numbers?  If so, how did it compare to HDFS?
 And are there any plans to try it on a larger cluster (I'm assuming you
were working with one VM).

Thanks,

--Jason

On Mon, Mar 26, 2012 at 12:11 AM, Todd Stavish <[EMAIL PROTECTED]>wrote:

> Final update, I tested 1.4.0rc5 against MapR v1.2.3. Everything works
> well. The only necessary install steps are the port mapping ones. Very
> clean.
>
> -Todd
>
>
> On Tue, Mar 20, 2012 at 9:39 PM, Todd Stavish <[EMAIL PROTECTED]>
> wrote:
> > Here are the complete instructions for running Accumulo on MapR M5 VM ->
> >
> > http://t.co/RJJ8Ht4B
> >
> > Thanks for all of the help,
> > -Todd
> >
> >
> >
> >
> > On Tue, Mar 20, 2012 at 1:10 PM, Todd Stavish <[EMAIL PROTECTED]>
> wrote:
> >>> I looked at the code and its just simply cast to a
> >>> DistributedFileSystem inorder to check if HDFS is in safe mode.  It
> >>> should do an instanceof operation and then do the case.  Would you
> >>> mind opening a ticket about this?
> >>
> >> Thanks Keith. Done.
> >>
> >> https://issues.apache.org/jira/browse/ACCUMULO-476
> >>
> >>
> >>
> >>>
> >>>>
> >>>>
> >>>> On Fri, Mar 16, 2012 at 9:19 AM, Eric Newton <[EMAIL PROTECTED]>
> wrote:
> >>>>> The monitor and gc do run in their own processes, which is kinda
> hinted at
> >>>>> the JVM memory sizes in conf/accumulo-env.sh
> >>>>>
> >>>>> The monitor may not be working because your jvm/os security profile
> is
> >>>>> different from those we've seen to date.
> >>>>> Replace conf/monitor.security.policy with:
> >>>>>
> >>>>>  grant{
> >>>>>   permission java.security.AllPermission;
> >>>>> };
> >>>>>
> >>>>> Or just chase down all the security violations you are getting in
> your
> >>>>> jvm/OS.  A quick look at the monitor logs and they seem ok.
> >>>>>
> >>>>> Your tserver isn't starting because some other process is listening
> on the
> >>>>> port.  The monitor can't talk to the master because it's waiting for
> some
> >>>>> tablet servers to show up.  The monitor may not display until it
> talks to
> >>>>> the master.  Good news: the logger started up fine.
> >>>>>
> >>>>> Do this:
> >>>>>
> >>>>> echo localhost > conf/gc
> >>>>>
> >>>>> That will get the gc to start up.
> >>>>>
> >>>>> Then this:
> >>>>>
> >>>>> # kill everything accumulo related
> >>>>> pkill -9 -f accumulo.start
> >>>>>
> >>>>> # start everything again
> >>>>> ./bin/start-all.sh
> >>>>>
> >>>>> Most of these issues, as well as some example configs for specific
> memory
> >>>>> sizes are fixed in the accumule-1.4.0 release candidate.
> >>>>>
> >>>>> -Eric
> >>>>>
> >>>>>
> >>>>> On Fri, Mar 16, 2012 at 12:00 PM, Todd Stavish <
> [EMAIL PROTECTED]>
> >>>>> wrote:
> >>>>>>
> >>>>>> accumulo init seemed to work. Full disclosure, I am running accumlo
> in
> >>>>>> the MapR M5 vm. I cranked down the memory allocations in
> >>>>>> accumulo-env.sh to compensate (maybe too much?). I'm not seeing all
> of
> >>>>>> the process launch. Does the monitor and GC run in their own
> >>>>>> processes? Neither the monitoring web page nor accumulo shell are
> >>>>>> working. Accumulo shell output below, in addition, ... running
> >>>>>> processes, logs, and confs attached.
> >>>>>>
> >>>>>> Running the whole MapR/Accumulo stack all in a single VM is flirting
> >>>>>> with oxymoron. My goal was just to go through the install sequence
> and
> >>>>>> run a few samples. If there is little hope in getting this to work
> in
> >>>>>> a vm, please let me now.
> >>>>>>
> >>>>>>
> >>>>>> mapr@mapr-desktop:/opt/accumulo-1.3.5-incubating/bin$ ./accumulo
> shell
> >>>>>> Enter current password for 'mapr'@'myinstance': *******
> >>>>>> 16 08:41:15,971 [impl.ServerClient] WARN : Failed to find an
> available
> >>>>>> server in the list of servers: [mapr-desktop:9999:9999 (120000)]
> >>>>>> 16 08:41:15,974 [shell.Shell] ERROR:
> >>>>>> org.apache.accumulo.core.client.AccumuloException:
> >>>>>> org.apache.thrift.transport.TTransportException: Failed to connect