.com/2009/06/hbase-setup-0193.html
> http://rajeev1982.blogspot.com/2009/06/hbase-setup-0193.html
>
> If you still have problem, let me know...
>
--
View this message in context:
http://old.nabble.com/Zoo-keeper-exception-in-the-middle-of-MR-tp30396344p30470210.html
Sent from the HB
I think you can refer the following link...
http://rajeev1982.blogspot.com/2009/06/hbase-setup-0193.html
http://rajeev1982.blogspot.com/2009/06/hbase-setup-0193.html
If you still have problem, let me know...
--
View this message in context:
http://old.nabble.com/Zoo-keeper-exception-in-the
ster of small computers now. Cluster contains 2
> >>>> machines,
> >>>> each of 2GB ram, dual core. but i've increased the hadoop and hbase
> >>>> heapsize
> >>>> to 1.5 gb. will this create any problem ? (other than slowing down
> t
gt;> that
>>>> i've given above)
>>>>
>>>>
>>>> Ted Dunning-2 wrote:
>>>> >
>>>> > lt looks like your task took a long time to complete (> 10 minutes)
>>>> and
>>>
>>> > some off-line data structure for a long time. Can you force your
>>> mappers
>>> > to
>>> > update a Hadoop counter as they go along? That might be all that is
>>> > needed.
>>> >
>>> > On Tue, Dec 7, 2010 a
or mapper
> >> builds
> >> > some off-line data structure for a long time. Can you force your
> >> mappers
> >> > to
> >> > update a Hadoop counter as they go along? That might be all that is
> >> > needed.
> >> >
> >> > On Tue, Dec
uilds
>> > some off-line data structure for a long time. Can you force your
>> mappers
>> > to
>> > update a Hadoop counter as they go along? That might be all that is
>> > needed.
>> >
>> > On Tue, Dec 7, 2010 at 5:37 AM, rajgopalv wrote:
>>
to
> > update a Hadoop counter as they go along? That might be all that is
> > needed.
> >
> > On Tue, Dec 7, 2010 at 5:37 AM, rajgopalv wrote:
> >
> >> Task attempt_201012071646_0001_m_000025_0 failed to report status for
> 600
> >> seconds.
o
> update a Hadoop counter as they go along? That might be all that is
> needed.
>
> On Tue, Dec 7, 2010 at 5:37 AM, rajgopalv wrote:
>
>> Task attempt_201012071646_0001_m_25_0 failed to report status for 600
>> seconds. Killing!
>>
>
>
--
View th
lt looks like your task took a long time to complete (> 10 minutes) and
didn't produce any output or report any status to Hadoop during this time.
This often happens during indexing tasks where a reducer or mapper builds
some off-line data structure for a long time. Can you force your mappers to
-keeper-exception-in-the-middle-of-MR-tp30396344p30396344.html
Sent from the HBase User mailing list archive at Nabble.com.
11 matches
Mail list logo
