You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Sean Busbey <bu...@cloudera.com> on 2014/03/14 19:43:55 UTC

Pushing out unassigned issues to 1.6.1

Unless someone objects, I'd like to push out most of the outstanding issues
for 1.6.0 that aren't assigned to anyone.

Most of these currently have priority Major. If someone thinks the problem
is severe enough to not push out, please assign yourself or escalate the
priority.

* ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
* ACCUMULO-1218 document the recovery from a failed zookeeper
* ACCUMULO-1515 Minimize README
* ACCUMULO-1491 Stop packaging html pages with the monitor
* ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
* ACCUMULO-2453 NoClassDefFound building against Hadoop1 in ShellServerTest
* ACCUMULO-2460 Experimental properties no longer hidden from
DefaultConfiguration

None of these impact the public API and most of them are clean up of test
or docs. So I think they can wait for a follow up release.

-- 
Sean

Re: Pushing out unassigned issues to 1.6.1

Posted by Sean Busbey <bu...@cloudera.com>.
Based on this thread and chatting with John, I went ahead and pushed out

* ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
* ACCUMULO-1218 document the recovery from a failed zookeeper
* ACCUMULO-1515 Minimize README
* ACCUMULO-1491 Stop packaging html pages with the monitor
* ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
* ACCUMULO-2453 NoClassDefFound building against Hadoop1 in ShellServerTest

And I changed the priority of ACCUMULO-2396 (create 1.6.0 release notes
content) to Blocker.

Anyone who is assigned an issue that isn't critical or blocker, please
consider pushing out to 1.6.1 or 1.7.0 or increasing the priority to
reflect its importance. If you already have patches in 1.6.0-SNAPSHOT
related to your open jira, consider moving the remaining work to a follow
on ticket.

-Sean

On Fri, Mar 14, 2014 at 3:31 PM, Eric Newton <er...@gmail.com> wrote:

> This time in english:
>
> In fact, if it's not marked critical or blocker I don't think we should
> worry about it.
>
>
>
>
> On Fri, Mar 14, 2014 at 4:29 PM, Eric Newton <er...@gmail.com>
> wrote:
>
> > Intermittent IT failures should not hold up the release.  In fact, if
> it's
> > not marked critical or blocker I don't even thing we should even worry
> > about it.
> >
> > I worked on ACCUMULO-2459, but I really need ctubbsii's input on this.
>  If
> > someone else knows what needs to be done, go for it.
> >
> > I would be comfortable with 1.6.0 as-is.
> >
> > Perfect is the enemy...
> >
> > -Eric
> >
> >
> > On Fri, Mar 14, 2014 at 3:32 PM, Sean Busbey <busbey+lists@cloudera.com
> >wrote:
> >
> >> Those are the biggies I was thinking of. I'm not sure about the recent
> IT
> >> failures opened by Eric N.
> >>
> >> * ACCUMULO-118 accumulo could work across HDFS instances, which would
> help
> >> it to scale past a single namenode
> >>
> >> needs to get closed out (but it's just waiting for ACCUMULO-2061 I
> think)
> >>
> >> * ACCUMULO-2459 accumulo-init RPM conflicts with accumulo-core RPM on
> >> /etc/accumulo
> >>
> >> Maybe this packaging concern?
> >>
> >> -Sean
> >>
> >>
> >> On Fri, Mar 14, 2014 at 2:14 PM, Keith Turner <ke...@deenlo.com> wrote:
> >>
> >> > Sounds good.   I will take a look at 2460.  I think more could be
> >> pushed to
> >> > 1.6.1 or 1.7.0.  What are the issues that mus be done for 1.6.0?
>  Below
> >> are
> >> > some that seem critical.
> >> >
> >> > ACCUMULO-2148 - verify upgrade works
> >> > ACCUMULO-2061 - deprecate instance.dfs.uri
> >> > ACCUMULO-2396 - create 1.6.0 release notes
> >> >
> >> > What about the documentation ones?
> >> >
> >> >
> >> > On Fri, Mar 14, 2014 at 2:43 PM, Sean Busbey <
> busbey+lists@cloudera.com
> >> > >wrote:
> >> >
> >> > > Unless someone objects, I'd like to push out most of the outstanding
> >> > issues
> >> > > for 1.6.0 that aren't assigned to anyone.
> >> > >
> >> > > Most of these currently have priority Major. If someone thinks the
> >> > problem
> >> > > is severe enough to not push out, please assign yourself or escalate
> >> the
> >> > > priority.
> >> > >
> >> > > * ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
> >> > > * ACCUMULO-1218 document the recovery from a failed zookeeper
> >> > > * ACCUMULO-1515 Minimize README
> >> > > * ACCUMULO-1491 Stop packaging html pages with the monitor
> >> > > * ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
> >> > > * ACCUMULO-2453 NoClassDefFound building against Hadoop1 in
> >> > ShellServerTest
> >> > > * ACCUMULO-2460 Experimental properties no longer hidden from
> >> > > DefaultConfiguration
> >> > >
> >> > > None of these impact the public API and most of them are clean up of
> >> test
> >> > > or docs. So I think they can wait for a follow up release.
> >> > >
> >> > > --
> >> > > Sean
> >> > >
> >> >
> >>
> >
> >
>

Re: Pushing out unassigned issues to 1.6.1

Posted by Eric Newton <er...@gmail.com>.
This time in english:

In fact, if it's not marked critical or blocker I don't think we should
worry about it.




On Fri, Mar 14, 2014 at 4:29 PM, Eric Newton <er...@gmail.com> wrote:

> Intermittent IT failures should not hold up the release.  In fact, if it's
> not marked critical or blocker I don't even thing we should even worry
> about it.
>
> I worked on ACCUMULO-2459, but I really need ctubbsii's input on this.  If
> someone else knows what needs to be done, go for it.
>
> I would be comfortable with 1.6.0 as-is.
>
> Perfect is the enemy...
>
> -Eric
>
>
> On Fri, Mar 14, 2014 at 3:32 PM, Sean Busbey <bu...@cloudera.com>wrote:
>
>> Those are the biggies I was thinking of. I'm not sure about the recent IT
>> failures opened by Eric N.
>>
>> * ACCUMULO-118 accumulo could work across HDFS instances, which would help
>> it to scale past a single namenode
>>
>> needs to get closed out (but it's just waiting for ACCUMULO-2061 I think)
>>
>> * ACCUMULO-2459 accumulo-init RPM conflicts with accumulo-core RPM on
>> /etc/accumulo
>>
>> Maybe this packaging concern?
>>
>> -Sean
>>
>>
>> On Fri, Mar 14, 2014 at 2:14 PM, Keith Turner <ke...@deenlo.com> wrote:
>>
>> > Sounds good.   I will take a look at 2460.  I think more could be
>> pushed to
>> > 1.6.1 or 1.7.0.  What are the issues that mus be done for 1.6.0?  Below
>> are
>> > some that seem critical.
>> >
>> > ACCUMULO-2148 - verify upgrade works
>> > ACCUMULO-2061 - deprecate instance.dfs.uri
>> > ACCUMULO-2396 - create 1.6.0 release notes
>> >
>> > What about the documentation ones?
>> >
>> >
>> > On Fri, Mar 14, 2014 at 2:43 PM, Sean Busbey <busbey+lists@cloudera.com
>> > >wrote:
>> >
>> > > Unless someone objects, I'd like to push out most of the outstanding
>> > issues
>> > > for 1.6.0 that aren't assigned to anyone.
>> > >
>> > > Most of these currently have priority Major. If someone thinks the
>> > problem
>> > > is severe enough to not push out, please assign yourself or escalate
>> the
>> > > priority.
>> > >
>> > > * ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
>> > > * ACCUMULO-1218 document the recovery from a failed zookeeper
>> > > * ACCUMULO-1515 Minimize README
>> > > * ACCUMULO-1491 Stop packaging html pages with the monitor
>> > > * ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
>> > > * ACCUMULO-2453 NoClassDefFound building against Hadoop1 in
>> > ShellServerTest
>> > > * ACCUMULO-2460 Experimental properties no longer hidden from
>> > > DefaultConfiguration
>> > >
>> > > None of these impact the public API and most of them are clean up of
>> test
>> > > or docs. So I think they can wait for a follow up release.
>> > >
>> > > --
>> > > Sean
>> > >
>> >
>>
>
>

Re: Pushing out unassigned issues to 1.6.1

Posted by Eric Newton <er...@gmail.com>.
Intermittent IT failures should not hold up the release.  In fact, if it's
not marked critical or blocker I don't even thing we should even worry
about it.

I worked on ACCUMULO-2459, but I really need ctubbsii's input on this.  If
someone else knows what needs to be done, go for it.

I would be comfortable with 1.6.0 as-is.

Perfect is the enemy...

-Eric


On Fri, Mar 14, 2014 at 3:32 PM, Sean Busbey <bu...@cloudera.com>wrote:

> Those are the biggies I was thinking of. I'm not sure about the recent IT
> failures opened by Eric N.
>
> * ACCUMULO-118 accumulo could work across HDFS instances, which would help
> it to scale past a single namenode
>
> needs to get closed out (but it's just waiting for ACCUMULO-2061 I think)
>
> * ACCUMULO-2459 accumulo-init RPM conflicts with accumulo-core RPM on
> /etc/accumulo
>
> Maybe this packaging concern?
>
> -Sean
>
>
> On Fri, Mar 14, 2014 at 2:14 PM, Keith Turner <ke...@deenlo.com> wrote:
>
> > Sounds good.   I will take a look at 2460.  I think more could be pushed
> to
> > 1.6.1 or 1.7.0.  What are the issues that mus be done for 1.6.0?  Below
> are
> > some that seem critical.
> >
> > ACCUMULO-2148 - verify upgrade works
> > ACCUMULO-2061 - deprecate instance.dfs.uri
> > ACCUMULO-2396 - create 1.6.0 release notes
> >
> > What about the documentation ones?
> >
> >
> > On Fri, Mar 14, 2014 at 2:43 PM, Sean Busbey <busbey+lists@cloudera.com
> > >wrote:
> >
> > > Unless someone objects, I'd like to push out most of the outstanding
> > issues
> > > for 1.6.0 that aren't assigned to anyone.
> > >
> > > Most of these currently have priority Major. If someone thinks the
> > problem
> > > is severe enough to not push out, please assign yourself or escalate
> the
> > > priority.
> > >
> > > * ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
> > > * ACCUMULO-1218 document the recovery from a failed zookeeper
> > > * ACCUMULO-1515 Minimize README
> > > * ACCUMULO-1491 Stop packaging html pages with the monitor
> > > * ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
> > > * ACCUMULO-2453 NoClassDefFound building against Hadoop1 in
> > ShellServerTest
> > > * ACCUMULO-2460 Experimental properties no longer hidden from
> > > DefaultConfiguration
> > >
> > > None of these impact the public API and most of them are clean up of
> test
> > > or docs. So I think they can wait for a follow up release.
> > >
> > > --
> > > Sean
> > >
> >
>

Re: Pushing out unassigned issues to 1.6.1

Posted by Sean Busbey <bu...@cloudera.com>.
Those are the biggies I was thinking of. I'm not sure about the recent IT
failures opened by Eric N.

* ACCUMULO-118 accumulo could work across HDFS instances, which would help
it to scale past a single namenode

needs to get closed out (but it's just waiting for ACCUMULO-2061 I think)

* ACCUMULO-2459 accumulo-init RPM conflicts with accumulo-core RPM on
/etc/accumulo

Maybe this packaging concern?

-Sean


On Fri, Mar 14, 2014 at 2:14 PM, Keith Turner <ke...@deenlo.com> wrote:

> Sounds good.   I will take a look at 2460.  I think more could be pushed to
> 1.6.1 or 1.7.0.  What are the issues that mus be done for 1.6.0?  Below are
> some that seem critical.
>
> ACCUMULO-2148 - verify upgrade works
> ACCUMULO-2061 - deprecate instance.dfs.uri
> ACCUMULO-2396 - create 1.6.0 release notes
>
> What about the documentation ones?
>
>
> On Fri, Mar 14, 2014 at 2:43 PM, Sean Busbey <busbey+lists@cloudera.com
> >wrote:
>
> > Unless someone objects, I'd like to push out most of the outstanding
> issues
> > for 1.6.0 that aren't assigned to anyone.
> >
> > Most of these currently have priority Major. If someone thinks the
> problem
> > is severe enough to not push out, please assign yourself or escalate the
> > priority.
> >
> > * ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
> > * ACCUMULO-1218 document the recovery from a failed zookeeper
> > * ACCUMULO-1515 Minimize README
> > * ACCUMULO-1491 Stop packaging html pages with the monitor
> > * ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
> > * ACCUMULO-2453 NoClassDefFound building against Hadoop1 in
> ShellServerTest
> > * ACCUMULO-2460 Experimental properties no longer hidden from
> > DefaultConfiguration
> >
> > None of these impact the public API and most of them are clean up of test
> > or docs. So I think they can wait for a follow up release.
> >
> > --
> > Sean
> >
>

Re: Pushing out unassigned issues to 1.6.1

Posted by Keith Turner <ke...@deenlo.com>.
Sounds good.   I will take a look at 2460.  I think more could be pushed to
1.6.1 or 1.7.0.  What are the issues that mus be done for 1.6.0?  Below are
some that seem critical.

ACCUMULO-2148 - verify upgrade works
ACCUMULO-2061 - deprecate instance.dfs.uri
ACCUMULO-2396 - create 1.6.0 release notes

What about the documentation ones?


On Fri, Mar 14, 2014 at 2:43 PM, Sean Busbey <bu...@cloudera.com>wrote:

> Unless someone objects, I'd like to push out most of the outstanding issues
> for 1.6.0 that aren't assigned to anyone.
>
> Most of these currently have priority Major. If someone thinks the problem
> is severe enough to not push out, please assign yourself or escalate the
> priority.
>
> * ACCUMULO-2095 Shard randomwalk test fails w/ multiple namnodes
> * ACCUMULO-1218 document the recovery from a failed zookeeper
> * ACCUMULO-1515 Minimize README
> * ACCUMULO-1491 Stop packaging html pages with the monitor
> * ACCUMULO-2308 LargeRowIT occasionally fails with too few splits
> * ACCUMULO-2453 NoClassDefFound building against Hadoop1 in ShellServerTest
> * ACCUMULO-2460 Experimental properties no longer hidden from
> DefaultConfiguration
>
> None of these impact the public API and most of them are clean up of test
> or docs. So I think they can wait for a follow up release.
>
> --
> Sean
>