You could run ./hadoop classpath to verify that the classpath is correct.
On 13 June 2012 08:18, Gopinathan A wrote:
> Use ./hadoop jar /usr/local/hbase-0.92.1-security/hbase-0.92.1-security.jar
> rowcounter
>
> Thanks & Regards,
> Gopinathan A
>
>
> ***
udgets allow.
>
> Getting back to your initial problem...
> Hash the keys and I think then you'll be ok.
>
>
> HTH
>
> -Mike
>
> On Jun 12, 2012, at 9:37 AM, Simon Kelly wrote:
>
> > No, this isn't on EC2 and yes, its (supposed to be) production. P
master crashed. The full master log is
here: http://pastebin.com/JE1rLC0C
This is HBase 0.92.1 with Hadoop 1.0.1
Simon
On 12 June 2012 16:37, Simon Kelly wrote:
> No, this isn't on EC2 and yes, its (supposed to be) production. Please
> elaboration on your inferred sigh of dispair
No, this isn't on EC2 and yes, its (supposed to be) production. Please
elaboration on your inferred sigh of dispair
On 12 June 2012 15:48, Michael Segel wrote:
> Ok...
>
> Please tell me that this isn't a production system.
>
> Is this on EC2?
>
> On Jun 12
bution across your splits.
>
> I'm also a bit curious about why you're pre-splitting in the first place.
> I mean I understand why people do it, but its a short term fix and I
> wonder how much pain you feel.
>
> Of course YMMV based on your use case.
>
> Hash your key an
ique but not necessarily random and even in random samplings,
> you may not see an even distribution except over time.
>
>
> Sent from my iPhone
>
> On Jun 12, 2012, at 3:18 AM, "Simon Kelly" wrote:
>
> > Hi
> >
> > I'm getting some unexpected r
Hi Andre
Have a look at HbaseWD from Sematext: https://github.com/sematext/HBaseWD
The strategy there is to prefix monotonic row keys by a bin number. This
spreads the writes across N bins but still allows efficient scans assuming
N is not large (N scans are required).
-Simon
On May 25, 2012 11:
t;>
>> *#2) -XX:ParallelGCThreads=2 *
>> *
>> The second test is just for giggles to see if the CMS aspect is helping
>> you at all (or if you are ending up doing a stop-the-world more than you
>> want. If that is the case, try using the default GC )
>> *
>&
the service that calls hbase)
Any assistance would be greatly appreciated. I did have GC logging on so
have access to all that data too.
Best regards
Simon Kelly
*Cluster details*
*--*
Its running on 5 machines with the following specs:
- CPUs: 4 x 2.39 GHz
- RAM: 8 GB
