You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Eric Newton <er...@gmail.com> on 2013/05/21 17:02:29 UTC
hadoop-2.0 incompatibility
Ugh. While running the continuous ingest verify, yarn spit this out:
Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
expected
This is preventing the reduce step from completing.
-Eric
Re: hadoop-2.0 incompatibility
Posted by Eric Newton <er...@gmail.com>.
I'm testing a fix, but I'm not for holding up the release for this.
First, calling a method by reflection is quite a bit slower, so even if we
fix it, it might not be appropriate.
On Tue, May 21, 2013 at 11:49 AM, John Vines <vi...@apache.org> wrote:
> Is this something else we can resolve via reflection or are we back to
> square 1?
>
>
> On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com>
> wrote:
>
> > Ugh. While running the continuous ingest verify, yarn spit this out:
> >
> > Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
> > expected
> >
> > This is preventing the reduce step from completing.
> >
> > -Eric
> >
>
Re: hadoop-2.0 incompatibility
Posted by John Vines <vi...@apache.org>.
Is this something else we can resolve via reflection or are we back to
square 1?
On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com> wrote:
> Ugh. While running the continuous ingest verify, yarn spit this out:
>
> Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
> expected
>
> This is preventing the reduce step from completing.
>
> -Eric
>
Re: hadoop-2.0 incompatibility
Posted by Christopher <ct...@apache.org>.
I agree that 1.5.1 is a reasonable target, if it's fixed at all (we
don't have Counters in our input/output formats, so the problem would
be exclusive to tests/examples anyway). If hadoop compat is a 1.5
feature, this is a minor bug.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, May 21, 2013 at 11:55 AM, Keith Turner <ke...@deenlo.com> wrote:
> On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com> wrote:
>
>> Ugh. While running the continuous ingest verify, yarn spit this out:
>>
>> Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
>> expected
>>
>> This is preventing the reduce step from completing.
>>
>
> Could fix it in 1.5.1
>
> I am starting to think that hadoop compat was so important, it should have
> been mostly completed before the feature freeze.
>
>
>>
>> -Eric
>>
Re: hadoop-2.0 incompatibility
Posted by Adam Fuchs <af...@apache.org>.
Yes, that's correct. It looks like we only need to exercise the two builds
option if we find a need later on.
Adam
On Tue, May 21, 2013 at 12:02 PM, Christopher <ct...@apache.org> wrote:
> Sure, that's still an option, but I don't think this particular
> incompatibility makes it necessary, does it?
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Tue, May 21, 2013 at 12:00 PM, Adam Fuchs <af...@apache.org> wrote:
> > We still have the option of putting out a separate build for 1.5.0
> > compatibility with hadoop 2. Should we vote on that release separately?
> > Seems like it should be easy to add more binary packages that correspond
> to
> > the same source release, even after the initial vote.
> >
> > Adam
> >
> >
> >
> > On Tue, May 21, 2013 at 11:55 AM, Keith Turner <ke...@deenlo.com> wrote:
> >
> >> On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com>
> >> wrote:
> >>
> >> > Ugh. While running the continuous ingest verify, yarn spit this out:
> >> >
> >> > Error: Found interface org.apache.hadoop.mapreduce.Counter, but class
> was
> >> > expected
> >> >
> >> > This is preventing the reduce step from completing.
> >> >
> >>
> >> Could fix it in 1.5.1
> >>
> >> I am starting to think that hadoop compat was so important, it should
> have
> >> been mostly completed before the feature freeze.
> >>
> >>
> >> >
> >> > -Eric
> >> >
> >>
>
Re: hadoop-2.0 incompatibility
Posted by Christopher <ct...@apache.org>.
Sure, that's still an option, but I don't think this particular
incompatibility makes it necessary, does it?
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, May 21, 2013 at 12:00 PM, Adam Fuchs <af...@apache.org> wrote:
> We still have the option of putting out a separate build for 1.5.0
> compatibility with hadoop 2. Should we vote on that release separately?
> Seems like it should be easy to add more binary packages that correspond to
> the same source release, even after the initial vote.
>
> Adam
>
>
>
> On Tue, May 21, 2013 at 11:55 AM, Keith Turner <ke...@deenlo.com> wrote:
>
>> On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com>
>> wrote:
>>
>> > Ugh. While running the continuous ingest verify, yarn spit this out:
>> >
>> > Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
>> > expected
>> >
>> > This is preventing the reduce step from completing.
>> >
>>
>> Could fix it in 1.5.1
>>
>> I am starting to think that hadoop compat was so important, it should have
>> been mostly completed before the feature freeze.
>>
>>
>> >
>> > -Eric
>> >
>>
Re: hadoop-2.0 incompatibility
Posted by Adam Fuchs <af...@apache.org>.
We still have the option of putting out a separate build for 1.5.0
compatibility with hadoop 2. Should we vote on that release separately?
Seems like it should be easy to add more binary packages that correspond to
the same source release, even after the initial vote.
Adam
On Tue, May 21, 2013 at 11:55 AM, Keith Turner <ke...@deenlo.com> wrote:
> On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com>
> wrote:
>
> > Ugh. While running the continuous ingest verify, yarn spit this out:
> >
> > Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
> > expected
> >
> > This is preventing the reduce step from completing.
> >
>
> Could fix it in 1.5.1
>
> I am starting to think that hadoop compat was so important, it should have
> been mostly completed before the feature freeze.
>
>
> >
> > -Eric
> >
>
Re: hadoop-2.0 incompatibility
Posted by Keith Turner <ke...@deenlo.com>.
On Tue, May 21, 2013 at 11:02 AM, Eric Newton <er...@gmail.com> wrote:
> Ugh. While running the continuous ingest verify, yarn spit this out:
>
> Error: Found interface org.apache.hadoop.mapreduce.Counter, but class was
> expected
>
> This is preventing the reduce step from completing.
>
Could fix it in 1.5.1
I am starting to think that hadoop compat was so important, it should have
been mostly completed before the feature freeze.
>
> -Eric
>