accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2139) Create list of features which need manual verification
Date Mon, 06 Jan 2014 22:49:50 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863569#comment-13863569
] 

Josh Elser commented on ACCUMULO-2139:
--------------------------------------

Cool! Thanks for the input, [~mackrorysd].

bq. currently Bigtop needs a "release" before it will build everything for you

Is this really just some Maven GAV that can be pulled through Maven or Ivy, or something else?
Ultimately, I think you hit the nail on the head with this note. While it would *also* be
nice for us to catch changes upstream in ZooKeeper or Hadoop (or even help them find bugs!),
I think that's a next step. Step one is really integration testing on semi-stable versions
of Hadoop so we can identify if (when) we screwed up.

Another thought here is that we could leverage something like Yarn through HOYA to automate
the cluster deployment. It took me a while to realize this, but I think there are a few perks.

# It aligns with (my) goal of treating Hadoop and ZooKeeper as provided
# You can define cluster specifications (2 masters, 8tservers and 64 tracers)
# It would run agnostic of *actual* resources available.

I think that last point is actually a pretty cool one. As long as your have memory on the
NodeManagers to actually service the requests for your cluster (you have enough resources
to start each process), the number of nodes is irrelevant. While this may not be satisfactory
for some of our tests (such as local mappers), but it still allows anyone to run the tests
(we could mark tests that don't have the resources as "incomplete" or "not-applicable" given
the resources).

> Create list of features which need manual verification
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2139
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2139
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Keith Turner
>             Fix For: 1.6.0
>
>
> If an issue like ACCUMULO-2036 can not be tested automatically, then maybe it should
be added to a list of things that must be verified before release.   Where should this list
go and what else should be on it?  
> Upgrade seems like another candidate for the list.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message