Re: [ANNOUNCE] New Committer: Balazs Meszaros

2018-10-12 Thread Balazs Meszaros
Thank you very much!

Balazs

On Fri, Oct 12, 2018 at 9:01 AM Peter Somogyi  wrote:

> Congratulations, Balázs!
>
> On Thu, Oct 11, 2018 at 9:49 PM Sean Busbey  wrote:
>
>> On behalf of the HBase PMC, I'm pleased to announce that Balazs
>> Meszaros has accepted our invitation to become an HBase committer.
>>
>> Thanks for all your hard work Balazs; we look forward to more
>> contributions!
>>
>> Please join me in extending congratulations to Balazs!
>>
>


Re: [VOTE] The first HBase 1.4.8 release candidate (RC0) is available

2018-10-03 Thread Balazs Meszaros
+1

- signatures, checksums: OK
- rat check: OK
- built from source (8u112): OK
- unit tests (8u112): OK
- ltt with 1M rows: OK
- web UI: OK
- shell and basic commands: OK

Thanks,
Balazs

On Wed, Oct 3, 2018 at 2:58 AM Andrew Purtell  wrote:

> The first HBase 1.4.8 release candidate (RC0) is available for download at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.8RC0/ and Maven
> artifacts are available in the temporary repository
> https://repository.apache.org/content/repositories/orgapachehbase-1233/
>
> The git tag corresponding to the candidate is '1.4.8RC0' (91118ce5f1).
>
> A detailed source and binary compatibility report for this release is
> available for your review at
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.8RC0/compat-check-report.html
> . There are no reported compatibility issues.
>
> A list of the 33 issues resolved in this release can be found at
> https://s.apache.org/xpxo .
>
> Please try out the candidate and vote +1/0/-1.
>
> The vote will be open for at least 72 hours. Unless objection I will try to
> close it Monday October 8, 2018 if we have sufficient votes.
>
> Prior to making this announcement I made the following preflight checks:
>
> RAT check passes (7u80)
> Unit test suite passes (7u80, 8u181)
> Opened the UI in a browser, poked around
> LTT load 1M rows with 100% verification and 20% updates (8u181)
> ITBLL 500M rows with serverKilling monkey (8u181)
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


[jira] [Created] (HBASE-21231) Add documentation for MajorCompactor

2018-09-25 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-21231:
---

 Summary: Add documentation for MajorCompactor
 Key: HBASE-21231
 URL: https://issues.apache.org/jira/browse/HBASE-21231
 Project: HBase
  Issue Type: Task
  Components: documentation
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


HBASE-19528 added a new MajorCompactor tool, but it lacks of documentation. 
Let's document it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] First release candidate for HBase 1.2.7 is available

2018-09-12 Thread Balazs Meszaros
+1

- signatures, checksums: OK
- rat check: OK
- built from source: OK
- unit tests: OK
- ltt with 1M rows: OK
- web UI: OK
- shell and basic commands: OK

Best regards,
Balazs

On Wed, Sep 12, 2018 at 1:04 AM Zach York 
wrote:

> +1 (non-binding)
>
>
> Checked sums and sigs: OK
> RAT check: OK
> Built from src: OK (8u92)
> Unit tests pass: OK (8u92)
>
> Thanks,
> Zach
>
> On Tue, Sep 11, 2018 at 9:06 AM Andrew Purtell 
> wrote:
>
> > +1
> >
> > Checked sums and signatures: ok
> > Checked compat report: ok, removed methods in Base64 are allowed by
> > consensus exception
> > RAT check: ok
> > Built from source: ok (7u80)
> > Unit tests pass: ok (8u172), note TestMutateRowsRecovery and
> > TestCompactionWithThroughputController failed when running the suite but
> > passed by themselves
> > 1M row LTT: ok (8u172)
> >
> >
> > On Fri, Sep 7, 2018 at 8:54 PM Sean Busbey  wrote:
> >
> > > The first release candidate for HBase 1.2.7 is available for download:
> > >
> > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.7RC0/
> > >
> > > Maven artifacts are also available in a staging repository at:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1232/
> > >
> > > Artifacts are signed with my key (0D80DB7C) published in our KEYS
> > > file at http://www.apache.org/dist/hbase/KEYS
> > >
> > > The RC corresponds to the signed tag 1.2.7RC0, which currently points
> > >  to commit ref
> > >
> > > ac57c51f7ad25e312b4275665d62b34a5945422f
> > >
> > > HBase 1.2.7 is the seventh maintenance release in the HBase 1.2 line,
> > > continuing on the theme of bringing a stable, reliable database to
> > > the Hadoop and NoSQL communities. This release includes over 250
> > > bug fixes done in the 15 months since 1.2.6.
> > >
> > > This release candidate contains the following incompatible changes,
> > > details in the release notes for the specific issue:
> > >
> > > * HBASE-20884 Replace usage of our Base64 implementation with java's
> > > * HBASE-18577 shaded client should not include non-relocated third
> party
> > >   dependencies
> > > * HBASE-18142 delete in HBase shell should not delete previous versions
> > >   of a cell
> > > * HBASE-18731 some protected methods of QuotaSettings have been marked
> > >   IA.Private and deprecated
> > > * HBASE-16459 HBase shell no longer recognizes the --format option
> > >
> > > The detailed source and binary compatibility report vs 1.2.6 has been
> > > published for your review, at:
> > >
> > > https://s.apache.org/hbase-1.2.7-rc0-compat-report
> > >
> > > The report shows some expected incompatibilities and one false
> positive.
> > > Details on HBASE-18276.
> > >
> > > Critical fixes include:
> > >
> > > * HBASE-18036 Data locality is not maintained after cluster restart
> > > * HBASE-18233 We shouldn't wait for readlock in doMiniBatchMutation in
> > >   case of deadlock
> > > * HBASE-9393  Region Server fails to properly close socket resulting in
> > >   many CLOSE_WAIT to Data Nodes
> > > * HBASE-19924 RPC throttling does not work for multi() with request
> > >   count rater.
> > > * HBASE-18192 Replication drops recovered queues on Region Server
> > >   shutdown
> > > * HBASE-18282 ReplicationLogCleaner can delete WALs not yet replicated
> > >   in case of a KeeperException
> > > * HBASE-19796 ReplicationSynUp tool is not replicating data if a WAL is
> > >   moved to splitting directory
> > > * HBASE-17648 HBase table-level synchronization fails between two
> > >   secured(kerberized) clusters
> > > * HBASE-18137 Replication gets stuck for empty WALs
> > > * HBASE-18577 shaded client should not include non-relocated third
> party
> > >   dependencies
> > > * HBASE-19900 Region level exceptions destroy the result of batch
> client
> > >   operations
> > > * HBASE-21007 Memory leak in HBase REST server
> > >
> > > The full list of fixes included in this release is available at:
> > >
> > > https://s.apache.org/hbase-1.2.7-jira-release-notes
> > >
> > > and in the CHANGES.txt file included in the distribution.
> > >
> > > Please try out this candidate and vote +1/-1 on whether we should
> > > release these artifacts as HBase 1.2.7.
> > >
> > > The VOTE will remain open for at least 72 hours. Given sufficient votes
> > > I would like to close it on September 12th, 2018.
> > >
> > > thanks!
> > >
> > > -busbey
> > >
> > > as of this email the posted artifacts have the following SHA512:
> > >
> > > hbase-1.2.7-bin.tar.gz:
> > > 00FC806A 335DFBDD 30720411 9FC0DD19 01AAC2E4 C8220B90
> > > D54263F4 4F49D49A 111C30D0 6E4CC6D3 249C4F5A 7A66064B
> > > 9EF97A92 B8E559F9 11705137 C3B652F2
> > >
> > > hbase-1.2.7-src.tar.gz:
> > > F142B8E2 4F615D32 2B3816B1 71A61D9A 618FDD99 1EE69772
> > > E3D52226 D30E34B8 0F9A469E 5AA00F6F 12AB77D6 C7FC6ADE
> > > 8CAB7254 8B2AF8E6 6D00E9EC D0E93AB4
> > >
> >
>


Re: [VOTE] The first HBase 1.4.7 release candidate (RC0) is available

2018-08-31 Thread Balazs Meszaros
+1

- signatures, checksums: OK
- rat check: OK
- built from source: OK
- unit tests: OK
- ltt with 1M rows: OK
- web UI: OK
- shell and basic commands: OK

On Fri, Aug 31, 2018 at 9:26 AM Mingliang Liu  wrote:

> +1 (non-binding)
>
>
>- Download source and verify with sha512sum
>- Check all the target 18 issues were included in both CHANGE list and
>git commit
>- Run RAT check: mvn apache-rat:check
>- Unit test suite: mvn test -P runAllTests
>- Install on local machine
>   - Check Web UI
>   - basic HBase shell command (put, get, scan, list etc)
>   - Loaded 1M rows with LTT:
>   - hbase ltt -tn TestTable -write 10:16 -num_keys 100
>   - hbase ltt -tn TestTable -read 100 -num_keys 100
>
> All passed.
>
>
> Java version: 8u181
>
> OS: Linux Ubuntu 16.04
>
> On Tue, Aug 28, 2018 at 3:11 PM Andrew Purtell 
> wrote:
>
> > The first HBase 1.4.7 release candidate (RC0) is available for download
> at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.7RC0/ and Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1230/
> .
> >
> > The git tag corresponding to the candidate is '1.4.7RC0' (763f27f583).
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.7RC0/compat-check-report.html
> > . There are no reported compatibility issues.
> >
> > A list of the 18 issues resolved in this release can be found at
> > https://s.apache.org/PvLv .
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > The vote will be open for at least 72 hours. Unless objection I will try
> to
> > close it Monday September 3, 2018 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks:
> >
> > RAT check passes (7u80)
> > Unit test suite passes (7u80)
> > LTT load 1M rows with 100% verification and 20% updates (8u181)
> > ITBLL 500M rows with slowDeterministic and serverKilling monkies
> > (8u181)
> >
> > --
> > Andrew
> >
>


Re: [VOTE] Second release candidate for hbase-2.0.2 (RC1) is available for download

2018-08-31 Thread Balazs Meszaros
+1

- signatures, checksums: OK
- rat check: OK
- built from source: OK
- unit tests: OK
- ltt with 1M rows: OK
- web UI: OK
- shell and basic commands: OK

Thanks Stack!

Balazs

On Fri, Aug 31, 2018 at 3:35 AM 张铎(Duo Zhang)  wrote:

> OK the second time it passed...
>
> +1 (binding)
>
> Built from source: OK
> Checked sigs and sums: OK
> Ran UTs: TestRegionFavoredNodes.testFavoredNodes failed but not a critical
> one
>
> Zach York  于2018年8月31日周五 上午5:48写道:
>
> > +1 (non-binding)
> >
> > - checked sigs and sums: OK
> > - built from source: OK
> > - Ran UTs: OK
> > - RAT check: OK
> >
> > Zach
> >
> > On Thu, Aug 30, 2018 at 5:42 AM 张铎(Duo Zhang) 
> > wrote:
> >
> > > When running UT the TestMergeRegionsProcedure failed for me...
> > >
> > > Let me try again...
> > >
> > > Tak-Lon (Stephen) Wu  于2018年8月30日周四 下午1:07写道:
> > >
> > > > +1 (non-binding)
> > > >
> > > >- checked sums and signatures: ok
> > > >- built from source: ok (8u121)
> > > >- Unit tests pass: ok (8u121)
> > > >- Rat check:  ok (8u121)
> > > >- WEB UI (8u181): looks correct
> > > >- basic HBase shell command
> > > >[put/get/scan/list/disable/drop/create/flush] (8u181) : ok
> > > >- Loaded 1M rows with LTT (8u181):  ok
> > > >- ITBLL *Loop 1* 1M rows with *serverKilling* monkey (8u181): ok
> > > >   - used command `hbase
> > > >   org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList -m
> > > > serverKilling
> > > >   loop 1 10 10 ${RANDOM} 10`
> > > >
> > > > -Stephen
> > > >
> > > > On Wed, Aug 29, 2018 at 8:14 PM Guanghao Zhang 
> > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > hbase-2.0.2-bin.tar.gz (jdk1.8.0_171)
> > > > > - Verified sha512: ok
> > > > > - Start HBase in standalone mode: ok
> > > > > - Verified with shell,
> > create/disable/enable/drop/get/put/scan/delete:
> > > ok
> > > > > - Checked master/regionserver/table/region Web UI: ok
> > > > >
> > > > > hbase-2.0.2-src.tar.gz (jdk1.8.0_171)
> > > > > - Verified sha512: ok
> > > > > - Build tarball: ok
> > > > > - Start HBase in standalone mode: ok
> > > > > - Verified with shell,
> > create/disable/enable/drop/get/put/scan/delete:
> > > ok
> > > > > - Checked master/regionserver/table/region Web UI: ok
> > > > >
> > > > > Andrew Purtell  于2018年8月30日周四 上午7:29写道:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Checked sums and signatures, ok
> > > > > > Built from source, ok (8u172)
> > > > > > RAT check passes (8u172)
> > > > > > Unit test suite passes (8u181)
> > > > > > Loaded 1M rows with ITBLL, looks fine (8u172)
> > > > > >
> > > > > >
> > > > > > On Tue, Aug 28, 2018 at 9:38 PM Stack  wrote:
> > > > > >
> > > > > > > The second release candidate for Apache HBase 2.0.2 (RC1) is
> > > > available
> > > > > > > for download and testing. This is a bug fix release with 100+
> > > commits
> > > > > > [1].
> > > > > > > Release notes are available here [2]. The compatibility report
> is
> > > at
> > > > > [3].
> > > > > > >
> > > > > > > Artifacts are available here:
> > > > > > >
> > > > > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/
> > > > > > >
> > > > > > > Corresponding convenience artifacts for maven use are in the
> > > staging
> > > > > > > repository:
> > > > > > >
> > > > > > >
> > > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1231
> > > > > > >
> > > > > > > All artifacts are signed with my code signing key, 8ACC93D2,
> > which
> > > is
> > > > > > > also in the project KEYS file:
> > > > > > >
> > > > > > > http://www.apache.org/dist/hbase/KEYS
> > > > > > >
> > > > > > > These artifacts correspond to commit ref
> > > > > > >
> > > > > > >  1cfab033e779df840d5612a85277f42a6a4e8172
> > > > > > >
> > > > > > > which has been tagged as 2.0.2RC1.
> > > > > > >
> > > > > > > Please take a few minutes to verify the release and vote on
> > > releasing
> > > > > it:
> > > > > > >
> > > > > > > [ ] +1 Release these artifacts as Apache HBase 2.0.2
> > > > > > > [ ] -1 Do not release this package because ...
> > > > > > >
> > > > > > > This VOTE thread will remain open for at least 72 hours. It
> will
> > > > close
> > > > > > for
> > > > > > > sure
> > > > > > > Saturday morning.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > S
> > > > > > >
> > > > > > > 1.
> > > > > >
> > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/CHANGES.md
> > > > > > > 2.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/RELEASENOTES.md
> > > > > > > 3.
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/compatibility_report_2.0.1_2.0.2.html
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best regards,
> > > > > > Andrew
> > > > > >
> > > > > > Words like orphans lost among the crosstalk, meaning torn from
> > > truth's
> > > > > > decrepit hands
> > > > > >- A23, Crosstalk
> > > > > >
> > > > >
> >

Re: [VOTE] The first HBase 1.4.6 release candidate (RC0) is available

2018-07-30 Thread Balazs Meszaros
+1

- signatures, shasum: OK
- rat check: OK
- built from source (8u122): OK
- unit tests: OK
- web UI: OK
- basic shell operations: OK
- LTT with 1M rows: OK

Best regards,
Balazs

On Mon, Jul 30, 2018 at 10:46 AM Peter Somogyi  wrote:

> +1 (non-binding)
>
> Signatures, checksums correct
> RAT check passed (8u171)
> Unit tests passed (8u171)
> LTT 1M rows passed
> Web UI looks correct
> Simple shell commands work
>
> Thanks for the release,
> Peter
>
> On Wed, Jul 25, 2018 at 8:36 PM Andrew Purtell 
> wrote:
>
> > The first HBase 1.4.6 release candidate (RC0) is available for download
> at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.6RC0/ and Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1226/
> .
> >
> > The git tag corresponding to the candidate is '1.4.6RC0' (a55bcbd4fc).
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.6RC0/compat-check-report.html
> > . There is an added method to the LimitedPrivate interface
> ReplicationPeer
> > which will not cause binary compatibility issues but will require source
> > changes at recompilation. This type of additive change is allowed. The
> > internal utility class Base64 has been made private and so the related
> > changes are allowed.
> >
> > A list of the 34 issues resolved in this release can be found at
> > https://s.apache.org/kolm .
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > This vote will be open for at least 72 hours. Unless objection I will try
> > to close it Monday July 30, 2018 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks:
> >
> > RAT check passes (7u80)
> > Unit test suite passes (7u80)
> > LTT load 1M rows with 100% verification and 20% updates (8u172)
> > ITBLL Loop 1 500M rows with serverKilling monkey (8u172)
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >- A23, Crosstalk
> >
>


[jira] [Created] (HBASE-20833) Modify pre-upgrade coprocessor validator to support table level coprocessors

2018-07-02 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20833:
---

 Summary: Modify pre-upgrade coprocessor validator to support table 
level coprocessors
 Key: HBASE-20833
 URL: https://issues.apache.org/jira/browse/HBASE-20833
 Project: HBase
  Issue Type: New Feature
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] First release candidate for hbase-2.0.1 (RC0) is available

2018-06-18 Thread Balazs Meszaros
+1

- Checksum, signature: OK
- RAT check: OK
- Built from source: OK
- Unit tests: OK
- Web UI and shell: OK
- LTT w/ 1M rows: OK

On Mon, Jun 18, 2018 at 9:29 AM Peter Somogyi  wrote:

> +1 (non-binding)
>
> Checksums, signatures - OK
> Build from source - OK
> Unit tests - OK
> Rat check - OK
> Started in pseudo-distributed mode - OK
> Shell CRUD operations - OK
> Web UI / LOGs - OK
>
> On Wed, Jun 13, 2018 at 11:15 PM Stack  wrote:
>
> > The first release candidate for Apache HBase 2.0.1 is available for
> > download and testing. This is a bug fix release with 70+ commits [1].
> > Release notes are available here [2].
> >
> > Artifacts are available here:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/
> >
> > Corresponding convenience artifacts for maven use are in the staging
> > repository:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1222
> >
> > All artifacts are signed with my code signing key, 8ACC93D2, which is
> > also in the project KEYS file:
> >
> > http://www.apache.org/dist/hbase/KEYS
> >
> > These artifacts correspond to commit ref
> >
> > 987f7b6d37c2fcacc942cc66e5c5122aba8fdfbe
> >
> > which has been tagged as 2.0.1RC0.
> >
> > Please take a few minutes to verify the release and vote on releasing it:
> >
> > [ ] +1 Release these artifacts as Apache HBase 2.0.1
> > [ ] -1 Do not release this package because ...
> >
> > This VOTE thread will remain open for at least 72 hours.
> >
> > Thanks,
> > S
> >
> > 1.
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/CHANGES.md
> > 2. https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.1RC0/
> > RELEASENOTES.md
> >
>


Re: [VOTE] Apache HBase 1.4.5 rc0

2018-06-13 Thread Balazs Meszaros
+1

- signatures & checksums: OK
- built from source: OK
- ran tests (8u112): OK
- web UI: OK
- basic shell commands: OK
- LTT with 1M rows: OK
- rat check: OK

Balazs

On Tue, Jun 12, 2018 at 5:43 PM Sean Busbey  wrote:

> -0
>
> Doesn't look like CHANGES got updated.
>
> On Thu, Jun 7, 2018 at 6:35 PM, Josh Elser  wrote:
> > Hi,
> >
> > Please vote to approve the following as Apache HBase 1.4.5
> >
> > https://dist.apache.org/repos/dist/dev/hbase/1.4.5rc0/
> >
> > Per usual, there is a source release as well as a convenience binary
> >
> > This is built with JDK7 from the commit:
> >
> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=commit;h=74596816c85f1256ec8a302efecc0144f2ea76fa
> > (there is a corresponding tag "1.4.5rc0" for convenience)
> >
> > hbase-1.4.5-bin.tar.gz: 7C8EFD79 CD5EAEFF 92F2E093 8AC8448C ED5717BD
> > 4C8D2C43
> > B95F804B 003E2126 9235EFE0 ABE61302 B81B30B1
> > F9F4A785
> > 17191950 2F436F64 19F50E53 999B5272
> > hbase-1.4.5-src.tar.gz: FED89273 FFA746DA D868DF79 7E46DB75 D0908419
> > F3D418FF
> > 73068583 A6F1DCB2 61BD2389 12DCE920 F8800CAE
> > 23631343
> > DB7601F4 F43331A4 678135E5 E5C566C4
> >
> > There is also a Maven staging repository for this release:
> > https://repository.apache.org/content/repositories/orgapachehbase-1219
> >
> > This vote will be open for at least 72 hours (2018/06/11  UTC).
> >
> > - Josh (on behalf of the HBase PMC)
> >
> >
>


Re: [VOTE] First release candidate for HBase 1.2.6.1 (RC0) is available

2018-06-05 Thread Balazs Meszaros
+1

- Signatures, checksums: OK
- Rat check: OK
- Built from source: OK
- Web UI: OK
- Basic shell commands: OK

On Mon, Jun 4, 2018 at 4:36 PM Peter Somogyi  wrote:

> On Mon, Jun 4, 2018 at 4:05 PM Sean Busbey  wrote:
>
> > On Mon, Jun 4, 2018 at 6:54 AM, Peter Somogyi 
> wrote:
> > > +1 (non-binding)
> > >
> > > Checksums, signatures: OK
> > > Apache rat check: OK
> > > Tarballs' content: OK
> > > Build from source: OK
> > > Unit tests: NOK
> > > TestTableLockManager is flaky
> > > Web UI: OK
> > > Shell w/ basic commands: OK
> > >
> > > Thanks,
> > > Peter
> > >
> > > Running org.apache.hadoop.hbase.master.TestTableLockManager
> > > Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 70.798
> > sec
> > > <<< FAILURE! - in org.apache.hadoop.hbase.master.TestTableLockManager
> > >
> >
> testReapAllTableLocks(org.apache.hadoop.hbase.master.TestTableLockManager)
> > > Time elapsed: 0.099 sec  <<< ERROR!
> > > org.apache.hadoop.hbase.exceptions.LockTimeoutException: Timed out
> > > acquiring writelock for table:table4for:zero timeout after 0 ms.
> > > at
> > >
> >
> org.apache.hadoop.hbase.master.TableLockManager$ZKTableLockManager$TableLockImpl.acquire(TableLockManager.java:282)
> > > at
> > >
> >
> org.apache.hadoop.hbase.master.TestTableLockManager.testReapAllTableLocks(TestTableLockManager.java:283)
> > >
> >
> > Thanks for checking on things Peter! What's your maven + Java versions?
>
>
> I used Maven 3.5.3, java 1.8.0_171 on Mac OS.
>


[jira] [Created] (HBASE-20656) Validate pre-2.0 coprocessors against HBase 2.0+

2018-05-28 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20656:
---

 Summary: Validate pre-2.0 coprocessors against HBase 2.0+
 Key: HBASE-20656
 URL: https://issues.apache.org/jira/browse/HBASE-20656
 Project: HBase
  Issue Type: New Feature
  Components: tooling
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


We have co-processors for a while, but the API has been changed recently. We 
should give some tooling for our users to determine if they can use the 
previous co-processors safely or not.

The tool should:
- try to load the co-processors on our current classpath for ensuring class 
references are on our classpath,
- should check for previously removed co-processor methods.

In this version we check only method signatures. Code references should be 
checked in further versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20571) JMXJsonServlet generates invalid JSON if it has NaN in metrics

2018-05-11 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20571:
---

 Summary: JMXJsonServlet generates invalid JSON if it has NaN in 
metrics
 Key: HBASE-20571
 URL: https://issues.apache.org/jira/browse/HBASE-20571
 Project: HBase
  Issue Type: Bug
  Components: UI
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


{{/jmx}} servlet responses invalid JSON, if some metrics are NaN:

{code}
"l1CacheHitCount" : 0,
"l1CacheMissCount" : 0,
"l1CacheHitRatio" : NaN,
"l1CacheMissRatio" : NaN,
"l2CacheHitCount" : 0,
"l2CacheMissCount" : 0,
"l2CacheHitRatio" : 0.0,
"l2CacheMissRatio" : 0.0,
{code}

NaN is an invalid character sequence in JSON. We should not response NaN in 
metrics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20563) Use parameterized logging in hbase-common

2018-05-10 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20563:
---

 Summary: Use parameterized logging in hbase-common
 Key: HBASE-20563
 URL: https://issues.apache.org/jira/browse/HBASE-20563
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20562) [UMBRELLA] Use parameterized logging

2018-05-10 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20562:
---

 Summary: [UMBRELLA] Use parameterized logging
 Key: HBASE-20562
 URL: https://issues.apache.org/jira/browse/HBASE-20562
 Project: HBase
  Issue Type: Umbrella
Affects Versions: 3.0.0
Reporter: Balazs Meszaros


We should use parameterized log message feature of slf4j/logback. (Use {} 
instead of string concatenation.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (HBASE-15002) TestRSKilledWhenInitializing is flakey

2018-05-09 Thread Balazs Meszaros (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-15002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balazs Meszaros resolved HBASE-15002.
-
Resolution: Duplicate

TestRSKilledWhenInitializing is currently ignored, see HBASE-19515.

> TestRSKilledWhenInitializing is flakey
> --
>
> Key: HBASE-15002
> URL: https://issues.apache.org/jira/browse/HBASE-15002
> Project: HBase
>  Issue Type: Sub-task
>  Components: flakey, test
>Reporter: stack
>Priority: Major
>
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-1.2/449/jdk=latest1.8,label=Hadoop/testReport/junit/org.apache.hadoop.hbase.regionserver/TestRSKilledWhenInitializing/testRSTermnationAfterRegisteringToMasterBeforeCreatingEphemeralNod/history/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (HBASE-15024) TestChoreService is flakey

2018-05-09 Thread Balazs Meszaros (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-15024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balazs Meszaros resolved HBASE-15024.
-
Resolution: Cannot Reproduce

TestChoreService is not flaky currently.

> TestChoreService is flakey
> --
>
> Key: HBASE-15024
> URL: https://issues.apache.org/jira/browse/HBASE-15024
> Project: HBase
>  Issue Type: Sub-task
>  Components: flakey, test
>Reporter: stack
>Priority: Critical
>
> https://builds.apache.org/job/HBase-Trunk_matrix/jdk=latest1.8,label=Hadoop/lastCompletedBuild/testReport/org.apache.hadoop.hbase/TestChoreService/testShutdownRejectsNewSchedules/history/
> Fails a bunch lately



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (HBASE-15307) TestFailedAppendAndSync.testLockupAroundBadAssignSync is flakey

2018-05-09 Thread Balazs Meszaros (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-15307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balazs Meszaros resolved HBASE-15307.
-
Resolution: Won't Fix

This unit test does not exist anymore.

> TestFailedAppendAndSync.testLockupAroundBadAssignSync is flakey
> ---
>
> Key: HBASE-15307
> URL: https://issues.apache.org/jira/browse/HBASE-15307
> Project: HBase
>  Issue Type: Sub-task
>  Components: flakey, test
>Reporter: stack
>Assignee: stack
>Priority: Critical
>
> {code}
> Error Message
> test timed out after 30 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 30 
> milliseconds
>   at java.lang.Thread.sleep(Native Method)
>   at org.apache.hadoop.hbase.util.Threads.sleep(Threads.java:148)
>   at 
> org.apache.hadoop.hbase.regionserver.TestFailedAppendAndSync.testLockupAroundBadAssignSync(TestFailedAppendAndSync.java:242)
> Standard Output
> 2016-02-22 18:14:09,154 INFO  [main] hbase.ResourceChecker(148): before: 
> regionserver.TestFailedAppendAndSync#testLockupAroundBadAssignSync Thread=4, 
> OpenFileDescriptor=206, MaxFileDescriptor=6, SystemLoadAverage=1043, 
> ProcessCount=300, AvailableMemoryMB=1709
> 2016-02-22 18:14:09,809 DEBUG [main] hbase.HBaseTestingUtility(338): Setting 
> hbase.rootdir to 
> /home/jenkins/jenkins-slave/workspace/HBase-Trunk_matrix/jdk/latest1.8/label/yahoo-not-h2/hbase-server/target/test-data/892bb23a-6932-4631-b4e0-a6384423d533
> 2016-02-22 18:14:10,167 WARN  [Time-limited test] util.NativeCodeLoader(62): 
> Unable to load native-hadoop library for your platform... using builtin-java 
> classes where applicable
> 2016-02-22 18:14:10,452 INFO  [Time-limited test] wal.FSHLog(527): WAL 
> configuration: blocksize=32 MB, rollsize=30.40 MB, prefix=wal, suffix=, 
> logDir=/home/jenkins/jenkins-slave/workspace/HBase-Trunk_matrix/jdk/latest1.8/label/yahoo-not-h2/hbase-server/target/test-data/892bb23a-6932-4631-b4e0-a6384423d533/TestHRegiontestLockupAroundBadAssignSync/testLockupAroundBadAssignSync,
>  
> archiveDir=/home/jenkins/jenkins-slave/workspace/HBase-Trunk_matrix/jdk/latest1.8/label/yahoo-not-h2/hbase-server/target/test-data/892bb23a-6932-4631-b4e0-a6384423d533/TestHRegiontestLockupAroundBadAssignSync/oldWALs
> 2016-02-22 18:14:10,534 INFO  [Time-limited test] wal.FSHLog(874): New WAL 
> /home/jenkins/jenkins-slave/workspace/HBase-Trunk_matrix/jdk/latest1.8/label/yahoo-not-h2/hbase-server/target/test-data/892bb23a-6932-4631-b4e0-a6384423d533/TestHRegiontestLockupAroundBadAssignSync/testLockupAroundBadAssignSync/wal.1456164850475
> 2016-02-22 18:14:10,673 INFO  [Time-limited test] regionserver.HRegion(6118): 
> creating HRegion testLockupAroundBadAssignSync HTD == 
> 'testLockupAroundBadAssignSync', {TABLE_ATTRIBUTES => {DURABILITY => 
> 'SYNC_WAL', READONLY => 'false'}, {NAME => 'MyCF', BLOOMFILTER => 'ROW', 
> VERSIONS => '2147483647', IN_MEMORY => 'false', KEEP_DELETED_CELLS => 
> 'FALSE', DATA_BLOCK_ENCODING => 'NONE', TTL => 'FOREVER', COMPRESSION => 
> 'NONE', MIN_VERSIONS => '0', BLOCKCACHE => 'true', BLOCKSIZE => '65536', 
> REPLICATION_SCOPE => '0'} RootDir = 
> /home/jenkins/jenkins-slave/workspace/HBase-Trunk_matrix/jdk/latest1.8/label/yahoo-not-h2/hbase-server/target/test-data/892bb23a-6932-4631-b4e0-a6384423d533
>  Table name == testLockupAroundBadAssignSync
> 2016-02-22 18:14:10,950 DEBUG [Time-limited test] regionserver.HRegion(718): 
> Instantiated 
> testLockupAroundBadAssignSync,,1456164850613.7eee51a40e497870a49a2965af62a054.
> 2016-02-22 18:14:11,253 INFO  
> [StoreOpener-7eee51a40e497870a49a2965af62a054-1] hfile.CacheConfig(292): 
> CacheConfig:disabled
> 2016-02-22 18:14:11,265 INFO  
> [StoreOpener-7eee51a40e497870a49a2965af62a054-1] 
> compactions.CompactionConfiguration(107): size [134217728, 
> 9223372036854775807, 9223372036854775807); files [3, 10); ratio 1.20; 
> off-peak ratio 5.00; throttle point 2684354560; major period 60480, 
> major jitter 0.50, min locality to compact 0.00
> 2016-02-22 18:14:11,269 DEBUG 
> [StoreOpener-7eee51a40e497870a49a2965af62a054-1] 
> regionserver.HRegionFileSystem(202): No StoreFiles for: 
> /home/jenkins/jenkins-slave/workspace/HBase-Trunk_matrix/jdk/latest1.8/label/yahoo-not-h2/hbase-server/target/test-data/892bb23a-6932-4631-b4e0-a6384423d533/data/default/testLockupAroundBadAssignSync/7eee51a40e49787

[jira] [Resolved] (HBASE-15262) TestZooKeeperMainServer#testCommandLineWorks fails with CancelledKeyException

2018-05-09 Thread Balazs Meszaros (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-15262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balazs Meszaros resolved HBASE-15262.
-
  Resolution: Won't Fix
Release Note: This unit test does not exist anymore.

> TestZooKeeperMainServer#testCommandLineWorks fails with CancelledKeyException
> -
>
> Key: HBASE-15262
> URL: https://issues.apache.org/jira/browse/HBASE-15262
> Project: HBase
>  Issue Type: Sub-task
>Reporter: stack
>Priority: Major
>
> {code}
> 2016-02-11 11:34:50,418 ERROR [SyncThread:0] server.NIOServerCnxn(178): 
> Unexpected Exception:
> java.nio.channels.CancelledKeyException
> at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
> at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:77)
> at 
> org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:151)
> at 
> org.apache.zookeeper.server.ZooKeeperServer.finishSessionInit(ZooKeeperServer.java:607)
> at 
> org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:181)
> at 
> org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:200)
> at 
> org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:131)
> [code}
> The test is expecting zk to do a System.exit but an existing zk or previous 
> test is getting us this CancelledKeyException... 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] The first HBase 1.4.4 release candidate (RC0) is available

2018-04-27 Thread Balazs Meszaros
+1

- signatures: OK
- built from source (8u112): OK
- unit tests: OK
- rat check: OK
- LTT with 1M rows: OK
- CRUD shell operations: OK
- web UI: OK

Best regards,
Balazs

On Wed, Apr 25, 2018 at 5:18 AM, Andrew Purtell  wrote:

> The first HBase 1.4.4 release candidate (RC0) is available for download at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.4RC0/ and Maven
> artifacts are available in the temporary repository
> https://repository.apache.org/content/repositories/orgapachehbase-1214/ .
>
> The git tag corresponding to the candidate is '1.4.4RC0' (fe146eb48c).
>
> A detailed source and binary compatibility report for this release is
> available for your review at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.4RC0/
> compat-check-report.html
> .
>
> A list of the 21 issues resolved in this release can be found at
> https://s.apache.org/E6GG .
>
> Please try out the candidate and vote +1/0/-1.
>
> This vote will be open for at least 72 hours. Unless objection I will try
> to close it Monday April 30, 2018 if we have sufficient votes.
>
> Prior to making this announcement I made the following preflight checks:
>
> RAT check passes (7u80)
> Unit test suite passes (7u80)
> LTT load 1M rows with 100% verification and 20% updates (8u152)
> ITBLL Loop 1 1B rows with serverKilling monkey (8u152)
>
> --
> Best regards,
> Andrew
>


[jira] [Created] (HBASE-20487) Sorting table regions by region name does not work on web UI

2018-04-25 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20487:
---

 Summary: Sorting table regions by region name does not work on web 
UI
 Key: HBASE-20487
 URL: https://issues.apache.org/jira/browse/HBASE-20487
 Project: HBase
  Issue Type: Bug
  Components: UI
Affects Versions: 3.0.0
Reporter: Balazs Meszaros


Table regions on {{table.jsp}} cannot be sorted by Name column.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

2018-04-24 Thread Balazs Meszaros
+1

- signatures and checksums: OK
- rat check: OK
- built from source (8u112): OK
- basic shell functionalities: OK
- web UI: OK
- LTT with 1M rows: OK


On Mon, Apr 23, 2018 at 7:10 AM, Stack  wrote:

> The third release candidate for Apache HBase 2.0.0 is available for
> downloading and testing.
>
> Artifacts are available here:
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC2/
>
> Maven artifacts are available in the staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1213
>
> All artifacts are signed with my signing key 8ACC93D2, which is also
> in the project KEYS file at
>
>  http://www.apache.org/dist/hbase/KEYS
>
> These artifacts were tagged 2.0.0RC2 at hash 7483b111e4da77adbfc8062b3b22cb
> e7c2cb91c1
>
> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> Reference Guide before installing or upgrading for a list of
> incompatibilities, major changes, and notable new features. Be aware that
> according to our adopted Semantic Versioning guidelines[1], we've allow
> ourselves to make breaking changes in this major version release. For
> example, Coprocessors will need to be recast to fit more constrained CP
> APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> downtime is (currently) not possible. That said, a bunch of effort has been
> expended mitigating differences; a hbase-1.x client can perform DML against
> an hbase-2 cluster. A
> bundled compatibility report showing difference from 1.2.6 may be of help
> [3].
>
> For the full list of ~6k issues addressed, see [2]. There are also
> CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.
>
> Please take a few minutes to verify the release and vote on releasing it:
>
> [ ] +1 Release this package as Apache HBase 2.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> This VOTE will run for one week and close Sunday, April 29, 2018 @ 21:00
> PST.
>
> Thanks to the myriad who have helped out with this release,
> Your 2.0.0 Release Manager
>
> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> 2. https://s.apache.org/zwS9
> 3.
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC2/
> compatibiliity_report_1.2.6vs2.0.0RC2.html
>


[jira] [Created] (HBASE-20465) Fix TestEnableRSGroup flaky

2018-04-20 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20465:
---

 Summary: Fix TestEnableRSGroup flaky
 Key: HBASE-20465
 URL: https://issues.apache.org/jira/browse/HBASE-20465
 Project: HBase
  Issue Type: Bug
  Components: rsgroup
Affects Versions: 2.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros
 Fix For: 2.0.0


Most recent {{TestEnableRSGroup}} tests failed on branch-2.0 according to our 
flaky dashboard.

{code}
java.lang.AssertionError
at 
org.apache.hadoop.hbase.rsgroup.TestEnableRSGroup.testEnableRSGroup(TestEnableRSGroup.java:80)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20427) thrift.jsp displays "Framed transport" incorrectly

2018-04-16 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20427:
---

 Summary: thrift.jsp displays "Framed transport" incorrectly 
 Key: HBASE-20427
 URL: https://issues.apache.org/jira/browse/HBASE-20427
 Project: HBase
  Issue Type: Bug
  Components: Thrift
Affects Versions: 2.0.0
Reporter: Balazs Meszaros
 Fix For: 3.0.0, 2.0.0


According to thrift usage text:
{code}
 -nonblocking  Use the TNonblockingServer This implies the
   framed transport.
{code}

But the web page at port 9095 indicates {{framed = false}} when I start it with 
{{-nonblocking}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20399) Fix merge layout

2018-04-12 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20399:
---

 Summary: Fix merge layout
 Key: HBASE-20399
 URL: https://issues.apache.org/jira/browse/HBASE-20399
 Project: HBase
  Issue Type: Bug
  Components: UI
Affects Versions: 3.0.0, 2.0.0
Reporter: Balazs Meszaros
 Attachments: merge.png

Merge regions on {{table.jsp}} has wrong layout (see screenshot).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20398) Redirect doesn't work on web UI

2018-04-12 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20398:
---

 Summary: Redirect doesn't work on web UI
 Key: HBASE-20398
 URL: https://issues.apache.org/jira/browse/HBASE-20398
 Project: HBase
  Issue Type: Bug
  Components: UI
Affects Versions: 3.0.0, 2.0.0
Reporter: Balazs Meszaros


{{table.jsp}} contains _"Go Back, or wait for the redirect."_ string after we 
invoke compaction, split, etc. Previously it redirected to the previous page 
after 5 seconds. The string is there currently, but nothing happens.

After digging into the code, a found the following:
 - {{ecce7c2}} (HBASE-3948) it was introduced,
 - {{3bd9191}} (HBASE-9850) it was refactored,
 - {{3b2b22b}} (HBASE-19291) it was removed.

This string appears on {{rsgroup.jsp}}, {{snapshot.jsp}} and {{table.jsp}}. We 
should fix them by removing the string, or by adding redirection again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20386) [DOC] Align WALPlayer help text and refguide

2018-04-11 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20386:
---

 Summary: [DOC] Align WALPlayer help text and refguide
 Key: HBASE-20386
 URL: https://issues.apache.org/jira/browse/HBASE-20386
 Project: HBase
  Issue Type: Task
  Components: documentation
Affects Versions: 2.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20358) Fix bin/hbase thrift usage text

2018-04-06 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20358:
---

 Summary: Fix bin/hbase thrift usage text
 Key: HBASE-20358
 URL: https://issues.apache.org/jira/browse/HBASE-20358
 Project: HBase
  Issue Type: Bug
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


1. Thrift server usage text does not say anything about it requires a {{start}} 
or {{stop}} argument.
 2. It ignores {{stop}} argument, it acts as the same as for {{start}}.

According to this comment:
{code:java}
// This is so complicated to please both bin/hbase and bin/hbase-daemon.
// hbase-daemon provides "start" and "stop" arguments
// hbase should print the help if no argument is provided
{code}
{{start}} and {{stop}} is just supported because {{bin/hbase-daemon}}, but 
hbase-daemon kills the process instead of calling it with a {{stop}} argument.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20343) [DOC] fix log directory paths

2018-04-04 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20343:
---

 Summary: [DOC] fix log directory paths
 Key: HBASE-20343
 URL: https://issues.apache.org/jira/browse/HBASE-20343
 Project: HBase
  Issue Type: Bug
  Components: documentation
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


The documentation refers to the log directories as {{.logs}}, {{splitlog}}, 
etc. These references should be changed to {{WALs}}, {{splitWAL}}, etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] The first HBase 1.4.3 release candidate (RC0) is available

2018-03-26 Thread Balazs Meszaros
+1

- built from source: OK
- unit tests passed: OK
- rat check: OK
- LTT with 1M rows: OK
- ran basic shell commands: OK
- web UI: OK

On Sat, Mar 24, 2018 at 4:37 AM, Ted Yu  wrote:

> +1
>
> Ran test suite with Java 1.8.0_151 - passed
> Ran RAT check - passed
>
> LoadTestTool loaded 1M rows
>
> On Fri, Mar 23, 2018 at 5:09 PM, Andrew Purtell 
> wrote:
>
> > The first HBase 1.4.3 release candidate (RC0) is available for download
> at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.3RC0/ and Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1207/
> .
> >
> > The git tag corresponding to the candidate is '1.4.3RC0' (172373d1f0).
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.3RC0/
> > compat-check-report.html
> > .
> >
> > A list of the 36 issues resolved in this release can be found at
> > https://s.apache.org/FM08 .
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > This vote will be open for at least 72 hours. Unless objection I will try
> > to close it Friday March 30, 2018 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks:
> >
> > RAT check passes (7u80)
> > Unit test suite passes (7u80)
> > LTT load 1M rows with 100% verification and 20% updates (8u152)
> > ITBLL Loop 1 1B rows (8u152)
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>


[jira] [Created] (HBASE-20258) Shell hangs when scanning a disabled table

2018-03-22 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20258:
---

 Summary: Shell hangs when scanning a disabled table
 Key: HBASE-20258
 URL: https://issues.apache.org/jira/browse/HBASE-20258
 Project: HBase
  Issue Type: Sub-task
Reporter: Balazs Meszaros


I executed the following commands against a 2.0 server:

{code}
disable 't'
scan 't'
{code}

>From client-1.2: it throws an error because the table is disabled -> OK.
>From client-2.0: the shell hangs -> NOT OK.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] First release candidate for HBase 1.3.2 (RC1) is available

2018-03-21 Thread Balazs Meszaros
+1

- signatures checksums: OK
- building from source (8u112): OK
- unit tests: OK
- basic shell commands: OK
- rat test: OK
- LTT with 1M rows (read/write): OK

Just a notice: according to our make_rc.sh script, the sha files should be
named as .sha512.

Thanks,
Balazs

On Wed, Mar 21, 2018 at 4:24 PM, Peter Somogyi  wrote:

> +1 (non-binding)
>
> checked signatures, sums
> built from source, ran unit tests
> rat check
> start from source and bin
> basic shell commands
> simple operations from basic java client
> LTT with 1M rows
>
> Thanks for the release,
> Peter
>
> On Tue, Mar 20, 2018 at 5:48 AM, Francis Liu  wrote:
>
> > Hi,
> >
> > The second release candidate for Apache HBase 1.3.2 is available to
> > download and testing.
> >
> > Artifacts are available here:
> >
> > *https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.2RC1/
> > *
> >
> > Maven artifacts are available in the staging repository:
> >
> > *https://repository.apache.org/content/repositories/orgapachehbase-1205
> >  >*
> >
> > All artifacts are signed with my code signing key D646D9F3, which is also
> > in the project KEYS file at
> >
> > http://www.apache.org/dist/hbase/KEYS
> >
> > these artifacts correspond to commit hash
> >
> > 1bedb5bfbb5a99067e7bc54718c3124f632b6e17 tagged as 1.3.2RC1.
> >
> > HBase 1.3.2 is the second maintenance release in the HBase 1.3.z release
> > line, continuing on the theme of bringing a stable, reliable database to
> > the
> > Hadoop and NoSQL communities. This release includes 256 resolved issues
> > since 1.3.1 released 11 months ago.
> >
> > The full list of issues addressed is available at
> >
> > *https://s.apache.org/aMSp *
> >
> > and also in the CHANGES.txt file in the root directory of the source
> > tarball.
> >
> > Please take a few minutes to verify the release and vote on
> > releasing it:
> >
> > [ ] +1 Release this package as Apache HBase 1.3.2
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > This Vote will run for one week and close Mon Mar 26, 2018 22:00 PST.
> >
> > Thanks
> >
>


[jira] [Created] (HBASE-20245) HTrace commands do not work

2018-03-21 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20245:
---

 Summary: HTrace commands do not work
 Key: HBASE-20245
 URL: https://issues.apache.org/jira/browse/HBASE-20245
 Project: HBase
  Issue Type: Sub-task
Reporter: Balazs Meszaros


When running shell-2.0 against server-2.0 we get the following error:

{code}
hbase(main):034:0> trace 'start'

ERROR: undefined method `isTracing' for Java::OrgApacheHtraceCore::Tracer:Class
{code}

It is possible to manipulate tracing from shell-1.2.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (HBASE-20200) list_procedures fails in shell

2018-03-14 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-20200:
---

 Summary: list_procedures fails in shell
 Key: HBASE-20200
 URL: https://issues.apache.org/jira/browse/HBASE-20200
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 2.0.0-beta-2
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


{code}
hbase(main):002:0> list_procedures
 Id Name State Submitted_Time Last_Update Parameters

ERROR: undefined method `slice' for #
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [ANNOUNCE] Please welcome Ashish Singhi to the HBase PMC

2018-02-28 Thread Balazs Meszaros
Great work, congratulations Ashish!

2018. febr. 28. 13:21 ezt írta ("Huaxiang Sun" ):

> Congratulations Ashish!
>
> > On Feb 28, 2018, at 10:53 AM, Tamás Pénzes  wrote:
> >
> > Congrats!
> >
> > On Wed, Feb 28, 2018 at 10:52 AM, Peter Somogyi 
> wrote:
> >
> >> Congratulations!
> >>
> >> On Wed, Feb 28, 2018 at 8:13 AM, Ted Yu  wrote:
> >>
> >>> Congratulations, Ashish.
> >>>
> >>> On Wed, Feb 28, 2018 at 7:55 AM, Sean Busbey 
> wrote:
> >>>
>  On behalf of the Apache HBase PMC I am pleased to announce that Ashish
>  Singhi has accepted our invitation to become a PMC member on the
>  Apache HBase project. We appreciate Ashish stepping up to take more
>  responsibility in the HBase project.
> 
>  As a reminder, if anyone would like to nominate another person as a
>  committer or PMC member, even if you are not currently a committer or
>  PMC member, you can always drop a note to priv...@hbase.apache.org to
>  let us know!
> 
>  - busbey
> 
> >>>
> >>
> >
> >
> >
> > --
> > *Tamás **Pénzes* | Engineering Manager
> > e. tam...@cloudera.com
> > cloudera.com 
>
>


Re: [ANNOUNCE] Please welcome Guanghao Zhang to the HBase PMC

2018-02-28 Thread Balazs Meszaros
Great work, congratulations Guanghao!

2018. febr. 28. 13:21 ezt írta ("Huaxiang Sun" ):

> Congratulations Guanghao!
>
>
> > On Feb 28, 2018, at 10:53 AM, Tamás Pénzes  wrote:
> >
> > Congrats!
> >
> > On Wed, Feb 28, 2018 at 10:52 AM, Peter Somogyi 
> wrote:
> >
> >> Congratulations!
> >>
> >> On Wed, Feb 28, 2018 at 8:13 AM, Ted Yu  wrote:
> >>
> >>> Congratulations, Guanghao !
> >>>
> >>> On Wed, Feb 28, 2018 at 7:55 AM, Sean Busbey 
> wrote:
> >>>
>  On behalf of the Apache HBase PMC I am pleased to announce that
>  Guanghao Zhang has accepted our invitation to become a PMC member on
>  the Apache HBase project. We appreciate Guanghao stepping up to take
>  more responsibility in the HBase project.
> 
>  As a reminder, if anyone would like to nominate another person as a
>  committer or PMC member, even if you are not currently a committer or
>  PMC member, you can always drop a note to priv...@hbase.apache.org to
>  let us know!
> 
>  - busbey
> 
> >>>
> >>
> >
> >
> >
> > --
> > *Tamás **Pénzes* | Engineering Manager
> > e. tam...@cloudera.com
> > cloudera.com 
>
>


Re: [ANNOUNCE] Please welcome Mike Drob to the HBase PMC

2018-02-28 Thread Balazs Meszaros
Great work, congratulations Mike!

2018. febr. 28. 13:22 ezt írta ("Huaxiang Sun" ):

> Congratulations Mike!
>
> > On Feb 28, 2018, at 11:54 AM, Umesh Agashe  wrote:
> >
> > Congratulations Mike!
> >
> > On Wed, Feb 28, 2018 at 10:56 AM, Zach York <
> zyork.contribut...@gmail.com>
> > wrote:
> >
> >> Nice work, Congratulations Mike!
> >>
> >> On Wed, Feb 28, 2018 at 10:52 AM, Peter Somogyi 
> >> wrote:
> >>
> >>> Congratulations!
> >>>
> >>> On Wed, Feb 28, 2018 at 10:40 AM, Esteban Gutierrez <
> >> este...@cloudera.com>
> >>> wrote:
> >>>
>  Excellent! congratulations, Mike!
> 
>  --
>  Cloudera, Inc.
> 
> 
>  On Wed, Feb 28, 2018 at 10:38 AM, Tamás Pénzes 
>  wrote:
> 
> > Congrats Mike!
> >
> > On Wed, Feb 28, 2018 at 8:13 AM, Ted Yu  wrote:
> >
> >> Congratulations, Mike !
> >>
> >> On Wed, Feb 28, 2018 at 7:54 AM, Sean Busbey 
>  wrote:
> >>
> >>> On behalf of the Apache HBase PMC I am pleased to announce that
> >>> Mike
> >>> Drob has accepted our invitation to become a PMC member on the
> >>> Apache
> >>> HBase project. We appreciate Mike stepping up to take more
> >>> responsibility in the HBase project.
> >>>
> >>>
> >>> As a reminder, if anyone would like to nominate another person
> >> as a
> >>> committer or PMC member, even if you are not currently a
> >> committer
> >>> or
> >>> PMC member, you can always drop a note to
> >> priv...@hbase.apache.org
>  to
> >>> let us know!
> >>>
> >>> - busbey
> >>>
> >>
> >
> >
> >
> > --
> >
> > *Tamás **Pénzes* | Engineering Manager
> > e. tam...@cloudera.com
> > cloudera.com 
> >
> > [image: Cloudera] 
> >
> > [image: Cloudera on Twitter]  [image:
> > Cloudera on Facebook]  [image:
>  Cloudera
> > on LinkedIn] 
> > --
> >
> 
> >>>
> >>
>
>


Re: [VOTE] The second HBase 1.4.2 release candidate (RC1) is available

2018-02-23 Thread Balazs Meszaros
+1 (non binding)

- signatures, checksums: OK
- unit tests (8u112): OK
- RAT check: OK
- LTT with 1M rows: OK
- basic shell and web functionality: OK

Thanks,
Balazs

On Thu, Feb 22, 2018 at 4:56 PM, Andrew Purtell  wrote:

> The close date will be *Wednesday* February 28, 2018.
>
> On Thu, Feb 22, 2018 at 3:55 PM, Andrew Purtell 
> wrote:
>
> > The second HBase 1.4.2 release candidate (RC1) is available for download
> > at https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC1/ and
> Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1196/
> .
> >
> > The git tag corresponding to the candidate is '1.4.2RC1' (b4ec89059c).
> > Note this is different from branch-1.4 by one commit because we had an
> > intervening commit between tag and push (08b9939974, HBASE-20016) while I
> > was running tests. The only difference is the CHANGES.txt update for
> > 1.4.2RC1 is placed ahead of the commit for HBASE-20016, but does not
> > mention it, which is fine, because 1.4.2RC1 does not contain HBASE-20016.
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at https://dist.apache.org/repos/
> > dist/dev/hbase/hbase-1.4.2RC1/compat-check-report.html .
> >
> > A list of the 22 issues resolved in this release can be found at
> > https://s.apache.org/aGcb .
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > This vote will be open for at least 72 hours. Unless objection I will try
> > to close it Thursday February 28, 2018 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks:
> >
> >- RAT check passes (7u80)
> >- Unit test suite passes (8u131)
> >- LTT load 1M rows with 100% verification and 20% updates (8u131)
> >- PE sequentialWrite, sequentialRead, randomWrite, randomRead,
> >scanRange100 (8u131)
> >- ITBLL Loop 1 100M rows (8u131)
> >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>


[jira] [Resolved] (HBASE-19854) Add a link to Ref Guide PDF

2018-02-12 Thread Balazs Meszaros (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-19854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balazs Meszaros resolved HBASE-19854.
-
Resolution: Won't Fix

It is also possible to find it through the search box if I search for 
"reference guide". I think we can close this.

> Add a link to Ref Guide PDF
> ---
>
> Key: HBASE-19854
> URL: https://issues.apache.org/jira/browse/HBASE-19854
> Project: HBase
>  Issue Type: Bug
>  Components: documentation
>Reporter: Laxmi Narsimha Rao Oruganti
>Priority: Minor
>
> Many a times, users want to have an offline copy of Ref Guide.  Some people 
> prefer to save HTML, and some people prefer it in PDF format.  Hence, Apache 
> HBase team generates PDF version of document periodically and keeps it 
> available at: [https://hbase.apache.org/apache_hbase_reference_guide.pdf]
> It would be good if a link to this URL is available in the online guide so 
> that users would become aware that there is a PDF version.  Right now, unless 
> some one explicitly looks for it using Google/Bing search, they would not 
> know.
>  
> As the PDF URL is fixed for latest documentation, it can be a static href.  
> However, I don't have any clues about how to make sure to get 
> "version-relevant" PDF link for archived ref guides.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Flaky dashboard is flaky

2018-02-02 Thread Balazs Meszaros
Hi,

The Flaky Dashboard for HBase 2.0 was not updated in the past few days
(last successful run was at 31 January). Last build

failed because of a networking problem:

requests.exceptions.ConnectionError:
HTTPConnectionPool(host='104.198.223.121', port=8080): Max retries
exceeded with url: /job/HBase-Flaky-Tests-branch2.0//api/json (Caused
by : [Errno 111] Connection refused)

I can access the dashboard.html file of the last build, but according to
the last updated field value it was updated at *01/31/2018 00:16:19*.

It is also the same for master flaky dashboard.

Could anybody check it?

Thanks,
Balazs


[jira] [Created] (HBASE-19886) Display maintenance mode in shell, web UI, JMX

2018-01-29 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19886:
---

 Summary: Display maintenance mode in shell, web UI, JMX
 Key: HBASE-19886
 URL: https://issues.apache.org/jira/browse/HBASE-19886
 Project: HBase
  Issue Type: New Feature
Affects Versions: 2.0.0, 3.0.0, 1.4.2
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


Maintenance mode was introduced in HBASE-16008. This mode is controlled by 
hbck. Splitting an balancing is disabled in this mode. It would be useful to 
present this information to users through shell, web UI, JMX.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] The fourth hbase-2.0.0-beta-1 Release Candidate is available for download

2018-01-15 Thread Balazs Meszaros
+1

- checksums, signatures: OK
- build from src: OK (8u112)
- unit tests passes except TestReplicationAdmin. Am I the only one who
cannot run it? It fails constantly, but it isn't in our flaky list.
- LTT with 1M rows works.
- Basic shell functionality works.
- Web UI for master and RS also seem too be good.

Balazs


On Mon, Jan 15, 2018 at 8:36 AM, Yung-An He  wrote:

> +1 non-binding
>
> Checked MD5: OK
> Testing the URL of download is available: OK
> Starting HBase with cluster mode via docker container: OK
> Import data with 100 million rows and 10 columns to table via ImportTsv: OK
> Execute basic command via `hbase shell`: OK
>
> 2018-01-14 4:23 GMT+08:00 Stack :
>
> > Thanks to the votes and testing so far.
> >
> > Last night, a nightly build on hadoop2 completed but I notice that it
> has a
> > bunch of tests filtered out [1] (I'm trying to get this facility turned
> > off). There is also a report by Duo that came in last night a test that
> > passes for me fails for him (HBASE-19791). It happens to be one of those
> > filtered out unfortunately.
> >
> > So, running the test suite (JMS!), you might want to apply the same
> filter
> > for now. See [1] below. I'll work on the failing tests in meantime (Yeah,
> > they were supposed to be fixed by now but its been taking a while).
> >
> > Thanks again for your patience/understanding.
> >
> > Yours,
> > Your RM
> >
> > 1.
> > https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> > 183/artifact/output-jdk8-hadoop2/patch-unit-root.txt
> >
> >
> > On Fri, Jan 12, 2018 at 8:48 PM, Stack  wrote:
> >
> > > The fourth release candidate for HBase 2.0.0-beta-1 is up at:
> > >
> > >   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC3/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > >   https://repository.apache.org/content/repositories/
> orgapachehbase-1193
> > >
> > > All was signed with my key at 8ACC93D2 [1].
> > >
> > > I tagged the RC as 2.0.0-beta-1-RC1.7 at hash 026f535a7747b89003252ded9
> > > 585e827686aa79f
> > >
> > > This RC has some nice bug fixes over RC0-2 including fixing MOST of the
> > > failing and flakey tests (We are still working through them).
> > >
> > > hbase-2.0.0-beta-1 is our first beta release. It includes all that was
> in
> > > previous alphas (new assignment manager, offheap read/write path,
> > in-memory
> > > compactions, etc.). The APIs and feature-set are sealed.
> > >
> > > hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It
> is
> > > meant for devs and downstreamers to test drive and flag us if we messed
> > up
> > > on anything ahead of our rolling GAs. We are particular interested in
> > > hearing from Coprocessor developers.
> > >
> > > The list of features addressed in 2.0.0 so far can be found here [3].
> > > There are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> > > found here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if
> > mistakes).
> > >
> > > I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one
> > > more beta before we put up our first 2.0.0 Release Candidate by the end
> > of
> > > January, 2.0.0-beta-2. Its focus will be making it so users can do a
> > > rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> > > running beta-1). Here is the list of what we have targeted so far for
> > > beta-2 [5]. Check it out.
> > >
> > > One known issue is that the User API has not been properly filtered so
> it
> > > shows more than just InterfaceAudience Public content (HBASE-19663, to
> be
> > > fixed by beta-2).
> > >
> > > Please take this beta for a spin. Please vote on whether it ok to put
> out
> > > this RC as our first beta (Note CHANGES has not yet been updated). Let
> > the
> > > VOTE be open for 72 hours (Lets say Tuesday morning!)
> > >
> > > Thanks,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > 3. https://goo.gl/scYjJr
> > > 4. https://goo.gl/dFFT8b
> > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> > > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > > z9iEu_ktczrlKHK8N4SZzs/
> > >
> >
>


Re: Flaky dashboard for current branch-2

2018-01-12 Thread Balazs Meszaros
Nice job! Thanks Appy!

On Fri, Jan 12, 2018 at 6:09 AM, Stack  wrote:

> Thanks Appy. Looks beautiful. Is Nightly now using a list of flakes?
> Thanks.
> S
>
> On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma 
> wrote:
>
> > https://builds.apache.org/job/HBase-Find-Flaky-Tests-
> > branch2.0/lastSuccessfulBuild/artifact/dashboard.html
> >
> > @stack: when you branch out branch-2.0, let me know, i'll update the jobs
> > to point to that branch so that it's helpful in release. Once release is
> > done, i'll move them back to "branch-2".
> >
> >
> > -- Appy
> >
>


Re: [VOTE] The second hbase-2.0.0-beta-1 Release Candidate is available for download

2018-01-10 Thread Balazs Meszaros
+1

- signatures, checksums OK,
- unit tests passes (8u112),
- shell works,
- load test tool also successed.

Best regards,
Balazs

On Tue, Jan 9, 2018 at 10:38 PM, Andrew Purtell  wrote:

> Linux here.
>
>
> On Tue, Jan 9, 2018 at 1:13 PM, Stack  wrote:
>
> > Andrew:
> >
> > I don't see this:
> >
> > [INFO] ---
> > [INFO]  T E S T S
> > [INFO] ---
> > [INFO] Running
> > org.apache.hadoop.hbase.regionserver.TestMemstoreLABWithoutPool
> > [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> > 4.409 s - in org.apache.hadoop.hbase.regionserver.
> > TestMemstoreLABWithoutPool
> > [INFO]
> > [INFO] Results:
> > [INFO]
> > [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
> >
> > Linux and Mac.
> >
> > What you reckon sir?
> >
> > St.Ack
> >
> >
> >
> >
> > On Tue, Jan 9, 2018 at 10:03 AM, Andrew Purtell 
> > wrote:
> >
> > > -1
> > >
> > > Checked sums and signatures: ok
> > > RAT check passes: ok (8u144)
> > > Built from source: ok (8u144)
> > > Unit tests pass: failed (8u144), TestMemstoreLABWithoutPool always
> fails
> > >
> > >
> > > TestMemstoreLABWithoutPool.org.apache.hadoop.hbase.regionserver.
> > > TestMemstoreLABWithoutPool
> > > can fail with OOME if not run in isolation.
> > >
> > > If run in isolation, I get
> > >
> > > org.apache.hadoop.hbase.regionserver.TestMemstoreLABWithoutPool.
> > > testLABChunkQueueWithMultipleMSLABs(org.apache.hadoop.hbase.
> > regionserver.
> > > TestMemstoreLABWithoutPool)
> > > [ERROR]   Run 1:
> > > TestMemstoreLABWithoutPool.testLABChunkQueueWithMultipleMSLABs:143 All
> > the
> > > chunks must have been cleared
> > > [ERROR]   Run 2:
> > > TestMemstoreLABWithoutPool.testLABChunkQueueWithMultipleMSLABs:143 All
> > the
> > > chunks must have been cleared
> > > [ERROR]   Run 3:
> > > TestMemstoreLABWithoutPool.testLABChunkQueueWithMultipleMSLABs:143 All
> > the
> > > chunks must have been cleared
> > > [ERROR]   Run 4:
> > > TestMemstoreLABWithoutPool.testLABChunkQueueWithMultipleMSLABs:143 All
> > the
> > > chunks must have been cleared
> > >
> > >
> > >
> > >
> > > On Mon, Jan 8, 2018 at 7:43 PM, Stack  wrote:
> > >
> > > > The second release candidate for HBase 2.0.0-beta-1 is up at:
> > > >
> > > >   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> beta-1-RC1/
> > > >
> > > > Maven artifacts are available from a staging directory here:
> > > >
> > > >   https://repository.apache.org/content/repositories/
> > orgapachehbase-1190
> > > >
> > > > All was signed with my key at 8ACC93D2 [1]
> > > >
> > > > I tagged the RC as 2.0.0-beta-1-RC1.5 (It took a few attempts) at
> > > > hash 4c31374a90a487e19a6ef04d7b7adba43dd92ecf
> > > >
> > > > This second RC has fix nice bug fixes over RC0 including fix for
> > failing
> > > > and flakey tests.
> > > >
> > > > hbase-2.0.0-beta-1 is our first beta release. It includes all that
> was
> > in
> > > > previous alphas (new assignment manager, offheap read/write path,
> > > in-memory
> > > > compactions, etc.). The APIs and feature-set are sealed.
> > > >
> > > > hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It
> > is
> > > > meant for devs and downstreamers to test drive and flag us if we
> messed
> > > up
> > > > on anything ahead of our rolling GAs. We are particular interested in
> > > > hearing from Coprocessor developers.
> > > >
> > > > The list of features addressed in 2.0.0 so far can be found here [3].
> > > There
> > > > are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> found
> > > > here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if mistakes).
> > > >
> > > > I've updated our overview doc. on the state of 2.0.0 [6]. We'll do
> one
> > > more
> > > > beta before we put up our first 2.0.0 Release Candidate by the end of
> > > > January, 2.0.0-beta-2. Its focus will be making it so users can do a
> > > > rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes
> found
> > > > running beta-1). Here is the list of what we have targeted so far for
> > > > beta-2 [5]. Check it out.
> > > >
> > > > One known issue is that the User API has not been properly filtered
> so
> > it
> > > > shows more than just InterfaceAudience Public content (HBASE-19663,
> to
> > be
> > > > fixed by beta-2).
> > > >
> > > > Please take this beta for a spin. Please vote on whether it ok to put
> > out
> > > > this RC as our first beta (Note CHANGES has not yet been updated).
> Let
> > > the
> > > > VOTE be open for 72 hours (Wednesday evening)
> > > >
> > > > Thanks,
> > > > Your 2.0.0 Release Manager
> > > >
> > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > > 3. https://goo.gl/scYjJr
> > > > 4. https://goo.gl/dFFT8b
> > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> > > > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > > > z9iEu_ktczrlKHK8N4SZzs/
> > > >
> > >
> > >
> > >
> > > --
> >

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

2018-01-03 Thread Balazs Meszaros
Only that one failed.

Balazs

On Wed, Jan 3, 2018 at 3:48 PM, stack  wrote:

> Thanks balazs. Did you find other failing tests or just this one?
>
> S
>
> On Jan 3, 2018 5:33 AM, "Balazs Meszaros" 
> wrote:
>
> > My observations:
> >
> > - signatures checksums are ok
> > - shell worked
> > - load test tool with read/write also worked
> > - when I built it, TestDefaultCompactSelection failed. The fix is already
> > here: HBASE-19666 <https://issues.apache.org/jira/browse/HBASE-19666>
> >
> > On Mon, Jan 1, 2018 at 11:30 PM, stack  wrote:
> >
> > > Yes. Of course. Need your input lads.
> > > S
> > >
> > > On Jan 1, 2018 3:15 PM, "Andrew Purtell" 
> > wrote:
> > >
> > > > Seconded. I’ll be back later this week. Can try it out then?
> > > >
> > > >
> > > > > On Jan 1, 2018, at 12:13 PM, Mike Drob  wrote:
> > > > >
> > > > > Is an extension here a reasonable ask? Putting the vote up right
> > before
> > > > > what is a long New Year weekend for many folks doesn't give a lot
> of
> > > > > opportunity for thorough review.
> > > > >
> > > > > Mike
> > > > >
> > > > >> On Mon, Jan 1, 2018 at 1:30 PM, stack 
> wrote:
> > > > >>
> > > > >> This is great stuff jms.  Thank you.  Away from computer at mo but
> > > will
> > > > dig
> > > > >> in.
> > > > >>
> > > > >> Is it possible old files left over written with old hbase with old
> > > hfile
> > > > >> version? Can you see on source?  They should have but updated by a
> > > > >> compaction if a long time idle, I agree.
> > > > >>
> > > > >> Yeah. If region assign fails, and goes into assignable state, we
> > need
> > > > >> intervention. We've been shutting down all the ways in which this
> > > could
> > > > >> happen but you seem to have stumbled on a new one. I will take a
> > look
> > > at
> > > > >> your logs.
> > > > >>
> > > > >> What you going to vote?  Does it basically work?
> > > > >>
> > > > >> Thanks again for the try out.
> > > > >> S
> > > > >>
> > > > >> On Dec 31, 2017 12:43 PM, "Jean-Marc Spaggiari" <
> > > > jean-m...@spaggiari.org>
> > > > >> wrote:
> > > > >>
> > > > >> Sorry to spam the list :(
> > > > >>
> > > > >> Another interesting thing.
> > > > >>
> > > > >> Now most of my tablesare online. For few I'm getting this:
> > > > >> Caused by: java.lang.IllegalArgumentException: Invalid HFile
> > version:
> > > > >> major=2, minor=1: expected at least major=2 and minor=3
> > > > >>at
> > > > >> org.apache.hadoop.hbase.io.hfile.HFileReaderImpl.
> checkFileVersion(
> > > > >> HFileReaderImpl.java:332)
> > > > >>at
> > > > >> org.apache.hadoop.hbase.io.hfile.HFileReaderImpl.(
> > > > >> HFileReaderImpl.java:199)
> > > > >>at org.apache.hadoop.hbase.io.
> hfile.HFile.openReader(HFile.
> > > > >> java:538)
> > > > >>... 13 more
> > > > >>
> > > > >> What is interesting is tat I'm not doing anything on the source
> > > cluster
> > > > for
> > > > >> weeks/months. So all tables are all major compacted the same way.
> I
> > > will
> > > > >> major compact them all under HFiles v3 format and retry.
> > > > >>
> > > > >> 2017-12-31 13:33 GMT-05:00 Jean-Marc Spaggiari <
> > > jean-m...@spaggiari.org
> > > > >:
> > > > >>
> > > > >>> Ok. With a brand new DestCP from source cluster, regions are
> > getting
> > > > >>> assigned correctly. So sound like if they get stuck initially for
> > any
> > > > >>> reason, then even if the reason is fixed they can not get
> assigned
> > > > >> anymore
> > > > >>> again. Will keep playing.
> > > > >>>
> > > > >>&

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

2018-01-03 Thread Balazs Meszaros
My observations:

- signatures checksums are ok
- shell worked
- load test tool with read/write also worked
- when I built it, TestDefaultCompactSelection failed. The fix is already
here: HBASE-19666 

On Mon, Jan 1, 2018 at 11:30 PM, stack  wrote:

> Yes. Of course. Need your input lads.
> S
>
> On Jan 1, 2018 3:15 PM, "Andrew Purtell"  wrote:
>
> > Seconded. I’ll be back later this week. Can try it out then?
> >
> >
> > > On Jan 1, 2018, at 12:13 PM, Mike Drob  wrote:
> > >
> > > Is an extension here a reasonable ask? Putting the vote up right before
> > > what is a long New Year weekend for many folks doesn't give a lot of
> > > opportunity for thorough review.
> > >
> > > Mike
> > >
> > >> On Mon, Jan 1, 2018 at 1:30 PM, stack  wrote:
> > >>
> > >> This is great stuff jms.  Thank you.  Away from computer at mo but
> will
> > dig
> > >> in.
> > >>
> > >> Is it possible old files left over written with old hbase with old
> hfile
> > >> version? Can you see on source?  They should have but updated by a
> > >> compaction if a long time idle, I agree.
> > >>
> > >> Yeah. If region assign fails, and goes into assignable state, we need
> > >> intervention. We've been shutting down all the ways in which this
> could
> > >> happen but you seem to have stumbled on a new one. I will take a look
> at
> > >> your logs.
> > >>
> > >> What you going to vote?  Does it basically work?
> > >>
> > >> Thanks again for the try out.
> > >> S
> > >>
> > >> On Dec 31, 2017 12:43 PM, "Jean-Marc Spaggiari" <
> > jean-m...@spaggiari.org>
> > >> wrote:
> > >>
> > >> Sorry to spam the list :(
> > >>
> > >> Another interesting thing.
> > >>
> > >> Now most of my tablesare online. For few I'm getting this:
> > >> Caused by: java.lang.IllegalArgumentException: Invalid HFile version:
> > >> major=2, minor=1: expected at least major=2 and minor=3
> > >>at
> > >> org.apache.hadoop.hbase.io.hfile.HFileReaderImpl.checkFileVersion(
> > >> HFileReaderImpl.java:332)
> > >>at
> > >> org.apache.hadoop.hbase.io.hfile.HFileReaderImpl.(
> > >> HFileReaderImpl.java:199)
> > >>at org.apache.hadoop.hbase.io.hfile.HFile.openReader(HFile.
> > >> java:538)
> > >>... 13 more
> > >>
> > >> What is interesting is tat I'm not doing anything on the source
> cluster
> > for
> > >> weeks/months. So all tables are all major compacted the same way. I
> will
> > >> major compact them all under HFiles v3 format and retry.
> > >>
> > >> 2017-12-31 13:33 GMT-05:00 Jean-Marc Spaggiari <
> jean-m...@spaggiari.org
> > >:
> > >>
> > >>> Ok. With a brand new DestCP from source cluster, regions are getting
> > >>> assigned correctly. So sound like if they get stuck initially for any
> > >>> reason, then even if the reason is fixed they can not get assigned
> > >> anymore
> > >>> again. Will keep playing.
> > >>>
> > >>> I kept the previous /hbase just in case we need something from it.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> JMS
> > >>>
> > >>> 2017-12-31 10:23 GMT-05:00 Jean-Marc Spaggiari <
> > jean-m...@spaggiari.org
> > >>> :
> > >>>
> >  Nothing bad that I can see. Here is a region server log:
> >  https://pastebin.com/0r76Y6ap
> > 
> >  Disabling the table makes the regions leave the transition mode. I'm
> >  trying to disable all tables one by one (because it get stuck after
> > each
> >  disable) and will see if re-enabling them helps...
> > 
> >  On the master side, I now have errors all over:
> >  2017-12-31 10:06:26,511 WARN  [ProcExecWrkr-89]
> >  assignment.RegionTransitionProcedure: Retryable error trying to
> >  transition: pid=511, ppid=398, state=RUNNABLE:REGION_
> > >> TRANSITION_DISPATCH;
> >  UnassignProcedure table=work_proposed, region=
> > >> d0a58b76ad9376b12b3e763660049d3d,
> >  server=node3.com,16020,1514693337210; rit=OPENING, location=
> node3.com
> >  ,16020,1514693337210
> >  org.apache.hadoop.hbase.exceptions.UnexpectedStateException:
> Expected
> >  [SPLITTING, SPLIT, MERGING, OPEN, CLOSING] so could move to CLOSING
> > but
> >  current state=OPENING
> >  at org.apache.hadoop.hbase.master.assignment.RegionStates$Regio
> >  nStateNode.transitionState(RegionStates.java:155)
> >  at org.apache.hadoop.hbase.master.assignment.AssignmentManager.
> >  markRegionAsClosing(AssignmentManager.java:1530)
> >  at org.apache.hadoop.hbase.master.assignment.UnassignProcedure.
> >  updateTransition(UnassignProcedure.java:179)
> >  at org.apache.hadoop.hbase.master.assignment.RegionTransitionPr
> >  ocedure.execute(RegionTransitionProcedure.java:309)
> >  at org.apache.hadoop.hbase.master.assignment.RegionTransitionPr
> >  ocedure.execute(RegionTransitionProcedure.java:85)
> >  at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Proce
> >  dure.java:845)
> >  at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execPro
> >  cedure(ProcedureExecu

[jira] [Created] (HBASE-19598) Fix TestAssignmentManagerMetrics flaky test

2017-12-22 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19598:
---

 Summary: Fix TestAssignmentManagerMetrics flaky test
 Key: HBASE-19598
 URL: https://issues.apache.org/jira/browse/HBASE-19598
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.0.0-beta-1
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


TestAssignmentManagerMetrics fails constantly. After bisecting, it seems that 
commit 010012cbcb broke it (HBASE-18946).

The test method runs successfully, but it cannot shut the minicluster down, and 
hangs forever.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Moving To SLF4J and Log4J2

2017-12-19 Thread Balazs Meszaros
Thanks for reviewing Appy!

1. I tried to verify it, log level changes take place through the web ui.
2. I put back fatals.
3. The property files are still compatible, because I have not updated
log4j to log4j2 yet. But they won't be compatible after the update.
4. I also updated those projects.

Unfortunately there are some issues which need to be solved before updating
to log4j2:
1. There are still some references in our java files to log4j (e.g.
LogManager references). We use it to set log levels from the code:
  - on the web ui,
  - in the unit tests (I removed them, because there were no asserts on the
log messages),
  - some command line tools also configured log levels from the code.
2. hbase-http also uses log4j for request logging.

If we can't rid off from these dependencies, then our codebase won't be
completely independent from the logging implementation.

Best regards,
Balazs

On Tue, Dec 19, 2017 at 2:37 AM, Apekshit Sharma  wrote:

> Thanks for the ping here Stack. Posted review on the jira.
> Summary is, we need at least:
> 1) basic verification
> 2) fatal markers
> 3) clear picture on properties file: Is old one compatible? if not, we need
> new ones and document what's breaking. New ones and documentation can be
> done in followup, but we need clear picture now.
> 4) Followup jira for hbase-backup/http or a reason why they can't be done.
>
> Reverting this patch would be hell, wouldn't want to do it because we
> missed basic checks.
>
> -- Appy
>
>
> On Mon, Dec 18, 2017 at 3:53 PM, Apekshit Sharma 
> wrote:
>
> > Oh, just 60 pages of review :D
> >
> > -- Appy
> >
> > On Mon, Dec 18, 2017 at 3:48 PM, Stack  wrote:
> >
> >> On Wed, Dec 13, 2017 at 10:09 AM, Stack  wrote:
> >>
> >> > On Mon, Dec 11, 2017 at 12:49 PM, Apekshit Sharma 
> >> > wrote:
> >> >
> >> >> Seems like good idea:
> >> >> - remove long dead dependency
> >> >> - a bit cleaner code
> >> >> - hadoop also moved to slf4j
> >> >>
> >> >> Quickly looking at codebase to get idea of amount of work required,
> >> here
> >> >> are some numbers:
> >> >> - LOG.debug : ~1800
> >> >> - LOG.trace : ~500
> >> >> - LOG.info: ~3000
> >> >>
> >> >> Looking at this patch (
> >> >> https://issues.apache.org/jira/secure/attachment/12901002/
> >> >> HBASE-19449.1.patch),
> >> >> seemed like tedious and repetitive task, was wondering if someone has
> >> >> automated it already.
> >> >> Looks like this can help reduce a huge part of grunt work:
> >> >> https://www.slf4j.org/migrator.html.
> >> >>
> >> >> But before progressing, as a basic validation, can we see:
> >> >> - an example of old vs new log lines (that there is no diff, or we
> are
> >> >> comfortable with what's there)
> >> >> - an example of changes in properties file
> >> >>
> >> >> Maybe starting with hbase-examples module for quick POC.
> >> >>
> >> >>
> >> > I like your suggestion Appy,
> >> > S
> >> >
> >> >
> >> Balazs has a patch up on HBASE-10092 making the move. Intend to commit
> it
> >> in next day or so unless objection.
> >> S
> >>
> >>
> >>
> >> >
> >> >
> >> >> -- Appy
> >> >>
> >> >
> >> >
> >>
> >
> >
> >
> > --
> >
> > -- Appy
> >
>
>
>
> --
>
> -- Appy
>


Re: [VOTE] The second HBase 1.4.0 release candidate (RC1) is available

2017-12-12 Thread Balazs Meszaros
+1

I ran the same tests as before:
- signatures, checksums are good,
- building and unit tests pass (8u112),
- shell functionalities are ok,
- RS groups work as expected.

Best regards,
Balazs

On Sat, Dec 9, 2017 at 4:37 AM, Guanghao Zhang  wrote:

> +1 (non-binding)
>
> hbase-1.4.0-bin.tar.gz (jdk8u144)
> - Verified md5sum: ok
> - Start HBase in standalone mode: ok
> - Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
> - Checked master/regionserver/region Web UI: ok
>
> hbase-1.4.0-src.tar.gz (jdk8u144)
> - Verified md5sum: ok
> - Build tarball: ok
> - Start HBase in standalone mode: ok
> - Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
> - Checked master/regionserver/region Web UI: ok
>
> One trivial bug for Table ui: the compaction state will show a exception
> message when the table is disabled. Will fill a issue for this.
>
> Thanks.
>
> 2017-12-09 9:50 GMT+08:00 Andrew Purtell :
>
> > The second HBase 1.4.0​ release candidate (RC1) is available for download
> > at https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.0RC1/ and
> Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1186/
> .
> >
> > The git tag corresponding to the candidate is '1.4.0RC1' (10b9b9fae6).
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.0RC1/
> > hbase-1.3.1-1.4.0RC1_compatibility_report.html
> > ​. All reported compatibility issues should comply with policy but please
> > review them carefully.
> >
> > A list of the 660 issues resolved in this release can be found at
> > https://s.apache.org/OErT .
> >
> > The changes since RC0 are:
> >
> > * [HBASE-19180] - Remove unused imports from AlwaysPasses
> > * [HBASE-19373] - Fix Checkstyle error in hbase-annotations
> > * [HBASE-19435] - Reopen Files for ClosedChannelException in
> > BucketCache
> > * [HBASE-19465] - Required httpcore and httpclient jars not included
> in
> > binary distribution
> > * [HBASE-19467] - rsgroups shell commands don't properly display
> > elapsed time
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > This vote will be open for at least 72 hours. Unless objection I will try
> > to close it ​Monday December 18, 2017 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks
> to
> > 1.4.0RC0 (3d571827cb):
> >
> > RAT check passes (7u80)
> > Unit test suite passes (8u131)
> > LTT load 1M rows with 100% verification and 20% updates (8u131)
> > PE randomWrite, randomRead, scanRange100 (8u131)
> > 100M rows ITBLL (8u131)
> >
> > and the following preflight checks to 1.4.0RC1 (10b9b9fae6):
> >
> > RAT check passes (7u80)
> > Unit test suite passes (8u131)
> >
> > Between now and when I want to close the vote I'll write up human
> readable
> > release notes for the release announcement as promised.
> >
> > I also have agreed to run a scale ITBLL test, a performance comparison
> with
> > 1.2 using YCSB, a  performance comparison with 1.2 using PE, and an
> > analysis of code and allocation hot spot changes from 1.2, all of which I
> > will publish when available and factor in to my vote.
> >
> > --
> > Best regards,
> > Andrew
> >
>


Re: [VOTE] The first HBase 1.4.0 release candidate (RC0) is available

2017-12-08 Thread Balazs Meszaros
Hi,

+1, because:

Signatures: ok
Unit tests: ok (8u112)
RSGroups: worked for me through the shell

-1, because:

hbase(main):005:0> list_rsgroups
GROUPS

test

default

2 row(s) in *1512730813.6580* seconds

Trust me, it was faster than 47 years :) Other listings (e.g.
list_namespace) displayed the elapsed time correctly.

Best regards,
Balazs

On Fri, Dec 8, 2017 at 4:51 AM, Ted Yu  wrote:

> +1
>
> Checked signatures: good
> Ran test suite: pass
> 1M row LTT: pass
>
> Cheers
>
> On Wed, Dec 6, 2017 at 8:40 PM, Andrew Purtell 
> wrote:
>
> > The first HBase 1.4.0​ release candidate (RC0) is available for download
> at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.0RC0/ and Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1185/
> .
> >
> > The git tag corresponding to the candidate is '1.4.0RC0' (3d571827cb).
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.0RC0/
> > hbase-1.3.1-1.4.0RC0_compatibility_report.html
> > ​. All reported compatibility issues should comply with policy but please
> > review them carefully.
> >
> > A list of the ​652 issues resolved in this release can be found at
> > https://s.apache.org/OErT .
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > This vote will be open for at least 72 hours. Unless objection I will try
> > to close it ​Monday December 18, 2017 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks
> to
> > 1.4.0RC0 (3d571827cb):
> >
> >- RAT check passes (7u80)
> >- Unit test suite passes (8u131)
> >- LTT load 1M rows with 100% verification and 20% updates (8u131)
> >- PE randomWrite, randomRead, scanRange100 (8u131)
> >- 100M rows ITBLL (8u131)
> >
> > Between now and when I want to close the vote I'll write up human
> readable
> > release notes for the release announcement as promised. I also have
> agreed
> > to run a scale ITBLL test, a performance comparison with 1.2 using YCSB,
> a
> > performance comparison with 1.2 using PE, and an analysis of code and
> > allocation hot spot changes from 1.2, all of which I will publish when
> > available and factor in to my vote.
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>


[jira] [Created] (HBASE-19403) Add missing security hooks for AdminService RPCs

2017-12-01 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19403:
---

 Summary: Add missing security hooks for AdminService RPCs
 Key: HBASE-19403
 URL: https://issues.apache.org/jira/browse/HBASE-19403
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.0.0-beta-1
Reporter: Balazs Meszaros


The following RPC methods do not call the observers, therefore they are not 
guarded by AccessController:
- updateConfiguration
- replay
- warmupRegion
- updateFavoredNodes
- clearRegionBlockCache



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19402) Add missing security hooks for RegionServerStatusService RPCs

2017-12-01 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19402:
---

 Summary: Add missing security hooks for RegionServerStatusService 
RPCs
 Key: HBASE-19402
 URL: https://issues.apache.org/jira/browse/HBASE-19402
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.0.0-beta-1
Reporter: Balazs Meszaros


The following RPC methods do not call the observers, therefore they are not 
guarded by AccessController:
- regionServerStartup
- regionServerReport
- reportRSFatalError
- reportRegionStateTransition
- reportRegionSpaceUse



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19401) Add missing security hooks for ClientService RPCs

2017-12-01 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19401:
---

 Summary: Add missing security hooks for ClientService RPCs
 Key: HBASE-19401
 URL: https://issues.apache.org/jira/browse/HBASE-19401
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.0.0-beta-1
Reporter: Balazs Meszaros


The following RPC method does not call the observers, therefore it is not 
guarded by AccessController:
- execRegionServerService



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19400) Add missing security hooks for MasterService RPCs

2017-12-01 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19400:
---

 Summary: Add missing security hooks for MasterService RPCs
 Key: HBASE-19400
 URL: https://issues.apache.org/jira/browse/HBASE-19400
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.0.0-beta-1
Reporter: Balazs Meszaros


The following RPC methods do not call the observers, therefore they are not 
guarded by AccessController:
- normalize
- setNormalizerRunning
- runCatalogScan
- enableCatalogJanitor
- runCleanerChore
- setCleanerChoreRunning
- execMasterService
- execProcedure
- execProcedureWithRet



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-19328) Remove asked if splittable log messages

2017-11-22 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-19328:
---

 Summary: Remove asked if splittable log messages
 Key: HBASE-19328
 URL: https://issues.apache.org/jira/browse/HBASE-19328
 Project: HBase
  Issue Type: Task
  Components: proc-v2
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Priority: Minor


I have found this log message in HBase log:
{code}
2017-11-22 11:16:54,133 INFO  
[RpcServer.priority.FPBQ.Fifo.handler=5,queue=0,port=52586] 
regionserver.HRegion(1309): ASKED IF SPLITTABLE true 
0a66d6e20801eec2c6cd1204fedde592
java.lang.Throwable: LOGGING: REMOVE
at 
org.apache.hadoop.hbase.regionserver.HRegion.isSplittable(HRegion.java:1310)
at 
org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegionInfo(RSRpcServices.java:1665)
at 
org.apache.hadoop.hbase.shaded.protobuf.generated.AdminProtos$AdminService$2.callBlockingMethod(AdminProtos.java:28159)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:406)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:325)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:305)
{code}

Still we need this?

It was introduced in commit {{dc1065a85}} by [~stack] and [~mbertozzi].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18805) Unify Admin and AsyncAdmin

2017-09-13 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18805:
---

 Summary: Unify Admin and AsyncAdmin
 Key: HBASE-18805
 URL: https://issues.apache.org/jira/browse/HBASE-18805
 Project: HBase
  Issue Type: Sub-task
Reporter: Balazs Meszaros


Admin and AsyncAdmin differ some places:
- some methods missing from AsyncAdmin (e.g. methods with String regex),
- some methods have different names (listTables vs listTableDescriptors),
- some method parameters are different (e.g. AsyncAdmin has Optional<> 
parameters),
- AsyncAdmin returns Lists instead of arrays (e.g. listTableNames),
- unify Javadoc comments,
- ...




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18706) Remove / fix not working pages from backup master web UI

2017-08-28 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18706:
---

 Summary: Remove / fix not working pages from backup master web UI
 Key: HBASE-18706
 URL: https://issues.apache.org/jira/browse/HBASE-18706
 Project: HBase
  Issue Type: Bug
Reporter: Balazs Meszaros


When I connect to a locally started backup master web interface, I have the 
following issues:
1. {{/tablesDetailed.jsp}} times out, we should remove the links from the menu, 
or we should connect to the active master.
2. {{/procedures.jsp}} throws an exception. The link to it is missing from 
{{/master-status}}, but it is visible under Process Metrics.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18705) bin/hbase does not find cached_classpath.txt

2017-08-28 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18705:
---

 Summary: bin/hbase does not find cached_classpath.txt
 Key: HBASE-18705
 URL: https://issues.apache.org/jira/browse/HBASE-18705
 Project: HBase
  Issue Type: Task
Affects Versions: 3.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


Starting hbase with {{bin/start-hbase.sh}} reports the following error:
{code:none}
As this is a development environment, we need 
/.../hbase/bin/../target/cached_classpath.txt to be generated from maven 
(command: mvn install -DskipTests)
{code}

The {{cached_classpath.txt}} is generated by hbase-assembly but it saves that 
file in {{$project.parent.basedir/...}}. Since hbase-build-configuration is the 
parent of hbase-assembly, the script searches the file at the wrong place.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18367) Reduce ProcedureInfo usage

2017-07-12 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18367:
---

 Summary: Reduce ProcedureInfo usage
 Key: HBASE-18367
 URL: https://issues.apache.org/jira/browse/HBASE-18367
 Project: HBase
  Issue Type: Sub-task
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


If we want to replace ProcedureInfo objects with jsons (HBASE-18106) we have to 
reduce ProcedureInfo usage. Currently it is used several places in the code 
where it could be replaced with Procedure (e.g. ProcedureExecutor). We should 
use ProcedureInfo only for the communication before removing it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


TimeBoundedRequestsWithRegionReplicas with unbalance monkey

2017-06-19 Thread Balazs Meszaros
Hi Enis,

We run IntegrationTestTimeBoundedRequestsWithRegionReplicas integration
test in our test infrastructure with unbalance chaos monkey. According to
the comment on the class, this test works only with serverKilling monkey.
With unbalance monkey it also works if I increase get_timeout_ms to 15
seconds instead of the default 5 seconds timeout.

1. Are there any reasons why should we only test it with serverKilling
monkey?
2. Is it okay for the unbalance monkey if we increase the timeout to 15
seconds or should it also work for 5 seconds timeout?

Thanks,
Balazs


[jira] [Created] (HBASE-18224) Upgrate jetty and thrift

2017-06-15 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18224:
---

 Summary: Upgrate jetty and thrift
 Key: HBASE-18224
 URL: https://issues.apache.org/jira/browse/HBASE-18224
 Project: HBase
  Issue Type: Sub-task
Reporter: Balazs Meszaros


Jetty can be updated to 9.4.6 and thrift can be updated to 0.10.0. I tried to 
update them in HBASE-17898 but some unit tests failed, so created a sub-task 
for them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (HBASE-18185) IntegrationTestTimeBoundedRequestsWithRegionReplicas unbalanced tests fails with AssertionError

2017-06-07 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18185:
---

 Summary: IntegrationTestTimeBoundedRequestsWithRegionReplicas 
unbalanced tests fails with AssertionError
 Key: HBASE-18185
 URL: https://issues.apache.org/jira/browse/HBASE-18185
 Project: HBase
  Issue Type: Bug
  Components: integration tests
Affects Versions: 2.0.0
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros
Priority: Minor


We got the following error:

Exception in thread "main" java.lang.AssertionError: Verification failed with 
error code 1
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.runIngestTest(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:217)
at 
org.apache.hadoop.hbase.IntegrationTestIngest.internalRunIngestTest(IntegrationTestIngest.java:123)
at 
org.apache.hadoop.hbase.IntegrationTestIngest.runTestFromCommandLine(IntegrationTestIngest.java:106)
at 
org.apache.hadoop.hbase.IntegrationTestBase.doWork(IntegrationTestBase.java:123)
at 
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:112)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at 
org.apache.hadoop.hbase.test.IntegrationTestTimeBoundedRequestsWithRegionReplicas.main(IntegrationTestTimeBoundedRequestsWithRegionReplicas.java:362)

The reason why we got it because another assertion fails in 
UnbalanceKillAndRebalanceAction:

Exception in thread "Thread-57" java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.hadoop.hbase.chaos.actions.UnbalanceKillAndRebalanceAction.perform(UnbalanceKillAndRebalanceAction.java:60)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (HBASE-18096) Limit HFileUtil visibility and add missing annotations

2017-05-23 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-18096:
---

 Summary: Limit HFileUtil visibility and add missing annotations
 Key: HBASE-18096
 URL: https://issues.apache.org/jira/browse/HBASE-18096
 Project: HBase
  Issue Type: Task
Reporter: Balazs Meszaros
Assignee: Balazs Meszaros


HFileUtil should be package private and should have @InterfaceAudience.Private 
annotation. This class was introduced in HBASE-17501.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (HBASE-17908) Upgrade guava

2017-04-12 Thread Balazs Meszaros (JIRA)
Balazs Meszaros created HBASE-17908:
---

 Summary: Upgrade guava
 Key: HBASE-17908
 URL: https://issues.apache.org/jira/browse/HBASE-17908
 Project: HBase
  Issue Type: Sub-task
Reporter: Balazs Meszaros


Currently we are using guava 12.0.1, but the latest version is 21.0. Upgrading 
guava is always a hassle because it is not always backward compatible with 
itself.

Currently I think there are to approaches:
1. Upgrade guava to the newest version (21.0) and shade it.
2. Upgrade guava to a version which does not break or builds (15.0).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


<    1   2