Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # user >> Premature EOF: no length prefix available


+
Jean-Marc Spaggiari 2013-05-02, 19:27
+
Ted Yu 2013-05-02, 19:40
+
Jean-Marc Spaggiari 2013-05-02, 19:57
+
Andrew Purtell 2013-05-02, 19:59
+
Jean-Marc Spaggiari 2013-05-02, 20:10
+
Andrew Purtell 2013-05-02, 20:18
+
Jean-Marc Spaggiari 2013-05-02, 20:23
+
Andrew Purtell 2013-05-02, 20:32
+
Loic Talon 2013-05-02, 20:53
+
Andrew Purtell 2013-05-02, 21:12
+
Loic Talon 2013-05-02, 21:21
+
Andrew Purtell 2013-05-02, 21:24
Copy link to this message
-
Re: Premature EOF: no length prefix available
Sorry, hit send too soon. I would recommend the following instance types:

    hi1.4xlarge: Expensive but it has a comfortable level of resources and
will perform
    hs1.8xlarge: This is what you might see in a typical data center Hadoop
deployment, also expensive
    m2.2xlarge/m2.4xlarge: Getting up to the amount of RAM you want for
caching in "big data" workloads
    m1.xlarge: Less CPU but more RAM than c1.xlarge, so safer
    c1.xlarge: Only if you really know what you are doing and need to be
cheap
    Anything lesser endowed: Never

You may find that, relative to AWS charges for a hi1.4xlarge, some other
hosting option for the equivalent would be more economical.
On Thu, May 2, 2013 at 2:12 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:

> > OS is Ubuntu 12.04 and instance type is c1.medium
>
> Eeek!
>
> You shouldn't use less than c1.xlarge for running Hadoop+HBase on EC2. A
> c1.medium has only 7 GB of RAM in total.
>
>
> On Thu, May 2, 2013 at 1:53 PM, Loic Talon <[EMAIL PROTECTED]> wrote:
>
>> Hi Andrew,
>> Thanks for those responses.
>>
>> The server has been deployed by Cloudera Manager.
>> OS is Ubuntu 12.04 and instance type is c1.medium.
>> Instance store are used, not EBS.
>>
>> It's possible that this problem is a memory problem ?
>> Because when region server hab been started I have in stdout.log :
>>
>> Thu May  2 17:01:10 UTC 2013
>> using /usr/lib/jvm/j2sdk1.6-oracle as JAVA_HOME
>> using 4 as CDH_VERSION
>> using  as HBASE_HOME
>> using /run/cloudera-scm-agent/process/381-hbase-REGIONSERVER as
>> HBASE_CONF_DIR
>> using /run/cloudera-scm-agent/process/381-hbase-REGIONSERVER as
>> HADOOP_CONF_DIR
>> using  as HADOOP_HOME
>>
>> But when I have the problem, I have in stdout.log :
>> Thu May  2 17:01:10 UTC 2013
>> using /usr/lib/jvm/j2sdk1.6-oracle as JAVA_HOME
>> using 4 as CDH_VERSION
>> using  as HBASE_HOME
>> using /run/cloudera-scm-agent/process/381-hbase-REGIONSERVER as
>> HBASE_CONF_DIR
>> using /run/cloudera-scm-agent/process/381-hbase-REGIONSERVER as
>> HADOOP_CONF_DIR
>> using  as HADOOP_HOME
>> #
>> # java.lang.OutOfMemoryError: Java heap space
>> # -XX:OnOutOfMemoryError="kill -9 %p"
>> #   Executing /bin/sh -c "kill -9 20140"...
>>
>> Thanks
>>
>> Loic
>>
>>
>>
>>
>>
>>
>>  Loïc TALON
>>
>>
>> [EMAIL PROTECTED] <http://teads.tv/>
>> Video Ads Solutions
>>
>>
>>
>> 2013/5/2 Andrew Purtell <[EMAIL PROTECTED]>
>>
>> > Every instance type except t1.micro has a certain number of instance
>> > storage (locally attached disk) volumes available, 1, 2, or 4 depending
>> on
>> > type.
>> >
>> > As you probably know, you can use or create AMIs backed by
>> instance-store,
>> > in which the OS image is constructed on locally attached disk by a
>> parallel
>> > fetch process from slices of the root volume image stored in S3, or
>> backed
>> > by EBS, in which case the OS image is an EBS volume and attached over
>> the
>> > network, like a SAN.
>> >
>> > If you launch an Amazon Linux instance store backed instance the first
>> > "ephemeral" local volume will be automatically attached on
>> > /media/ephemeral0. That's where that term comes from, it's a synonym for
>> > instance-store. (You can by the way tell CloudInit via directives sent
>> over
>> > instance data to mount all of them.)
>> >
>> > If you have an EBS backed instance the default is to NOT attach any of
>> > these volumes.
>> >
>> > If you are launching your instance with the Amazon Web console, in the
>> > volume configuration part you can set up instance-store aka "ephemeral"
>> > mounts whether it is instance-store backed or EBS backed.
>> >
>> > Sorry I can't get into more background on this. Hope it helps.
>> >
>> >
>> >
>> > On Thu, May 2, 2013 at 1:23 PM, Jean-Marc Spaggiari <
>> > [EMAIL PROTECTED]
>> > > wrote:
>> >
>> > > Hi Andrew,
>> > >
>> > > No, this AWS instance is configured with instance stores too.
>> > >
>> > > What do you mean by "ephemeral"?
>> > >
>> > > JM
>> > >
>> > > 2013/5/2 Andrew Purtell <[EMAIL PROTECTED]>

Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
+
Michael Segel 2013-05-02, 21:32
+
Andrew Purtell 2013-05-02, 21:47
+
Jean-Marc Spaggiari 2013-05-05, 11:34
+
Jean-Marc Spaggiari 2013-05-02, 21:15
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB