Sound like it's even better to have multiple of 25M... Running with 50M now. Will see.
@Nick: For the test suite,I have been able to get one successful out of 4... Not impressive. I have restarted them with rerunFailingTestsCount=4. Will see if it makes a difference... 2015-06-25 18:57 GMT-04:00 Enis Söztutar <[email protected]>: > Slight correction, ITBLL needs numKeys to be a multiple of 1M. See the > javadoc and ascii art at the code. > > Enis > > On Thu, Jun 25, 2015 at 1:47 PM, Enis Söztutar <[email protected]> wrote: > > > ITBLL requires at least 1M per mapper. You can run with less number of > > mappers and numKeys = 1M. > > > > Enis > > > > On Thu, Jun 25, 2015 at 4:23 AM, Jean-Marc Spaggiari < > > [email protected]> wrote: > > > >> 2015-06-24 22:29 GMT-04:00 Enis Söztutar <[email protected]>: > >> > >> > > > >> > > Also, I tried to run IntegrationTestBigLinkedList and it fails: > >> > > 015-06-24 19:06:11,644 ERROR [main] > >> > > test.IntegrationTestBigLinkedList$Verify: Expected referenced count > >> does > >> > > not match with actual referenced count. expected referenced=1000000 > >> > > ,actual=0 > >> > > > >> > > >> > What are the command line arguments passed? Verify cannot find any > >> > references? > >> > > >> > >> I ran this: > >> bin/hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList > loop 3 > >> 100 10000 /tmp/loop 10 > >> > >> I can retry with any other if it helps. > >> > >> > >> > > >> > > >> > > > >> > > > >> > > And last I ran IntegrationTestLoadAndVerify but I have no idea how > to > >> > > interpret the result ;) > >> > > > org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify$Counters > >> > > REFERENCES_WRITTEN=19800000 > >> > > ROWS_WRITTEN=20000000 > >> > > > >> > > > org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify$Counters > >> > > REFERENCES_CHECKED=1036925998 > >> > > ROWS_WRITTEN=0 > >> > > > >> > > >> > This is a bit fishy. Again, what are the parameters passed? Did you > run > >> > with a clean cluster state? > >> > > >> > >> > >> Was always doing that before any test: > >> echo "disable 'IntegrationTestLoadAndVerify'; drop > >> 'IntegrationTestLoadAndVerify'" | bin/hbase shell > >> > >> And ran with this command: > >> bin/hbase org.apache.hadoop.hbase.test.IntegrationTestLoadAndVerify > >> loadAndVerify > >> > >> > >> > >> > > >> > For these two tests, I think there is at least 3 or so bugs already > >> fixed > >> > in theory. Our tests and my 1.2B row tests on a previous branch-1.1 > code > >> > base was ok. > >> > > >> > > >> > >> Also, any idea why non of the tests pass on my side? > >> I tried some of them individually and they passed: > >> ------------------------------------------------------- > >> T E S T S > >> ------------------------------------------------------- > >> Running org.apache.hadoop.hbase.master.TestClockSkewDetection > >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.69 > sec - > >> in org.apache.hadoop.hbase.master.TestClockSkewDetection > >> Results : > >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > >> > >> But it prevents me to run the entire test suite at once. I will give it > >> few > >> more tries today... > >> > >> JM > >> > >> > >> > >> > > >> > > > >> > > > >> > > So. It seems to be working on my cluster, but I have not been able > to > >> get > >> > > any successful test. Therefore I'm a bit reluctant to say +1 and > will > >> > only > >> > > say +/-0.... > >> > > > >> > > For pefs tests, I still need some more work on my clusters... So not > >> for > >> > > this release. > >> > > > >> > > JM > >> > > > >> > > 2015-06-24 16:25 GMT-04:00 Ted Yu <[email protected]>: > >> > > > >> > > > +1 > >> > > > > >> > > > Ran test suite against Java 1.8.0_45 > >> > > > Checked signature > >> > > > Practiced basic shell commands > >> > > > > >> > > > On Tue, Jun 23, 2015 at 4:25 PM, Nick Dimiduk < > [email protected]> > >> > > wrote: > >> > > > > >> > > > > I'm happy to announce the first release candidate of HBase 1.1.1 > >> > > > > (HBase-1.1.1RC0) is available for download at > >> > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.1RC0/ > >> > > > > > >> > > > > Maven artifacts are also available in the staging repository > >> > > > > > >> > > > >> https://repository.apache.org/content/repositories/orgapachehbase-1087/ > >> > > > > > >> > > > > Artifacts are signed with my code signing subkey > >> 0xAD9039071C3489BD, > >> > > > > available in the Apache keys directory > >> > > > > https://people.apache.org/keys/committer/ndimiduk.asc > >> > > > > > >> > > > > There's also a signed tag for this release at > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=af1934d826cab80f727e9a95c5b564f04da73259 > >> > > > > > >> > > > > HBase 1.1.1 is the first patch release in the HBase 1.1 line, > >> > > continuing > >> > > > on > >> > > > > the theme of bringing a stable, reliable database to the Hadoop > >> and > >> > > NoSQL > >> > > > > communities. This release includes over 100 bug fixes since the > >> 1.1.0 > >> > > > > release, including an assignment manager bug that can lead to > data > >> > loss > >> > > > in > >> > > > > rare cases. Users of 1.1.0 are strongly encouraged to update to > >> 1.1.1 > >> > > as > >> > > > > soon as possible. > >> > > > > > >> > > > > The full list of issues can be found at > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12332169 > >> > > > > > >> > > > > Please try out this candidate and vote +/-1 by midnight Pacific > >> time > >> > on > >> > > > > Sunday, 2015-06-28 as to whether we should release these > >> artifacts as > >> > > > HBase > >> > > > > 1.1.1. > >> > > > > > >> > > > > Thanks, > >> > > > > Nick > >> > > > > > >> > > > > >> > > > >> > > >> > > > > >
