Re: Question on DisableTableHandler#handleDisableTable()
The DisableTableHandler#handleDisableTable() is doing a while(true) loop for retrying Step (2) - marking regions offline; however, if there is an InterruptedException exception, it would exit the loop and continue co-processor post operation and complete the process() call without rethrowing the exception. Once Procedure V2 is implemented, we can leverage the proc results to do retry; instead of just checking whether the table is disabled in a loop from client-side. My main question is that is current behavior desired? If (2) failed with InterruptedException exception, should we - rethrow the InterruptedException - or doing some rollback - reset the table state back to ENABLED Thanks Stephen On Tue, Mar 31, 2015 at 3:06 PM, Enis Söztutar e...@apache.org wrote: I was talking about the server side in DisableTableHandler, specifically BulkDisabler. In case of the client side retry, we can now (with procv2) inspect the status of the disable table operation and if it failed retry. Previously, there was no way. Enis On Tue, Mar 31, 2015 at 2:56 PM, Stephen Jiang syuanjiang...@gmail.com wrote: There is no retry in DisableTableHandler code. The sync version of disableTable (HBaseAdmin.java) waits a long period and kept checking whether the table is disabled, even the DisableTableHandler already completes and it does not know. After long wait, it would throw RegionException. It is up to the caller of the disableTable to do retry. The async version, my guess is that the application code would do the same as the sync version of logic. Thanks Stephen On Tue, Mar 31, 2015 at 2:11 PM, Enis Söztutar e...@apache.org wrote: We retry (2) until it succeeds or master is stopped (in which case the new master takes over), no? On Tue, Mar 31, 2015 at 2:00 PM, Stephen Jiang syuanjiang...@gmail.com wrote: In DisableTableHandler#handleDisableTable(), we do the following: (1). Set the table state to DISABLING (2). Try to mark all regions of table (based on in-memory state of the active master) to offline (3). If 2 succeed, then set the table state to DISABLED My question is if (2) failed, it would continue to co-processor post operation and complete the process() call. This will leave the table in DISABLING state without letting user know that the operation actually fails. Is this desired behavior? Thanks Stephen
[jira] [Created] (HBASE-13376) Improvements to Stochastic load balancer
Vandana Ayyalasomayajula created HBASE-13376: Summary: Improvements to Stochastic load balancer Key: HBASE-13376 URL: https://issues.apache.org/jira/browse/HBASE-13376 Project: HBase Issue Type: Improvement Components: Balancer Affects Versions: 0.98.12, 1.0.0 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor There are two things this jira tries to address: 1. The locality picker in the stochastic balancer does not pick regions with least locality as candidates for swap/move. So when any user configures locality cost in the configs, the balancer does not always seems to move regions with bad locality. 2. When a cluster has equal number of loaded regions, it always picks the first one. It should pick a random region on one of the equally loaded servers. This improves a chance of finding a good candidate, when load picker is invoked several times. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-13377) Canary may generate false alarm on the first region when there are many delete markers
He Liangliang created HBASE-13377: - Summary: Canary may generate false alarm on the first region when there are many delete markers Key: HBASE-13377 URL: https://issues.apache.org/jira/browse/HBASE-13377 Project: HBase Issue Type: Bug Components: monitoring Reporter: He Liangliang Assignee: He Liangliang When there are many delete markers, the probe on the first region will timeout and generate a false alarm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-13379) TimeRangeTracker Can Be Non-Blocking
John Leach created HBASE-13379: -- Summary: TimeRangeTracker Can Be Non-Blocking Key: HBASE-13379 URL: https://issues.apache.org/jira/browse/HBASE-13379 Project: HBase Issue Type: New Feature Reporter: John Leach Priority: Minor I am seeing the TimeRangeTracker hotspot under heavy write load. It looks like a good use case for an atomic reference for the data point (min and max timestamp). I have a working proto, will submit patch for consideration once I run this test suite (beast). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-12813) Reporting region in transition shouldn't loop forever
[ https://issues.apache.org/jira/browse/HBASE-12813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark resolved HBASE-12813. --- Resolution: Duplicate Pretty sure that HBASE-13317 fixed this issue. If not I'll open a new task with jstacks. Reporting region in transition shouldn't loop forever - Key: HBASE-12813 URL: https://issues.apache.org/jira/browse/HBASE-12813 Project: HBase Issue Type: Bug Reporter: Elliott Clark Assignee: Elliott Clark We had an issue where a region server wasn't able to send the report region in transition request. Well after failing it just retries forever. At some point it would have been better to just abort the region server if it can't talk to master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-13378) RegionScannerImpl synchronized for READ_UNCOMMITTED Isolation Levels
John Leach created HBASE-13378:
--
Summary: RegionScannerImpl synchronized for READ_UNCOMMITTED
Isolation Levels
Key: HBASE-13378
URL: https://issues.apache.org/jira/browse/HBASE-13378
Project: HBase
Issue Type: New Feature
Reporter: John Leach
Priority: Minor
This block of code below coupled with the close method could be changed so that
READ_UNCOMMITTED does not synchronize.
{CODE:JAVA}
// synchronize on scannerReadPoints so that nobody calculates
// getSmallestReadPoint, before scannerReadPoints is updated.
IsolationLevel isolationLevel = scan.getIsolationLevel();
synchronized(scannerReadPoints) {
this.readPt = getReadpoint(isolationLevel);
scannerReadPoints.put(this, this.readPt);
}
{CODE}
This hotspots for me under heavy get requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Please welcome new HBase committer Srikanth Srungarapu
Congratulations, Srikanth!!! On Wed, Apr 1, 2015 at 11:51 PM, Esteban Gutierrez este...@cloudera.com wrote: Awesome! Congratulations, Srikanth! -- Cloudera, Inc. On Wed, Apr 1, 2015 at 11:02 AM, Ted Yu yuzhih...@gmail.com wrote: Congrats, Srikanth. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[VOTE] The 3rd HBase 0.98.12 release candidate (RC2) is available, vote closing 4/7/2015
The 3rd HBase 0.98.12 release candidate (RC2) is available for download at http://people.apache.org/~apurtell/0.98.12RC2/ and Maven artifacts are also available in the temporary repository https://repository.apache.org/content/repositories/orgapachehbase-1071/ The API compatibility report with respect to the previous release can be found at http://people.apache.org/~apurtell/0.98.11_0.98.12RC2_compat_report.html Signed with my code signing key D5365CCD. The issues resolved in this release can be found at http://s.apache.org/zH Please try out the candidate and vote +1/-1 by midnight Pacific Time (00:00 -0800 GMT) on April 7 on whether or not we should release this as 0.98.12. Three +1 votes from PMC will be required to release. -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
RE: Please welcome new HBase committer Srikanth Srungarapu
Congrats, Srikanth. Regards, Abhishek -Original Message- From: Andrew Purtell [mailto:apurt...@apache.org] Sent: 02 April 2015 01:53 To: dev@hbase.apache.org; u...@hbase.apache.org Subject: Please welcome new HBase committer Srikanth Srungarapu On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Please welcome new HBase committer Srikanth Srungarapu
Congrats, Srikanth~ -Shaohui Liu On 04/02/2015 11:40 AM, ramkrishna vasudevan wrote: Congratulations, Srikanth!!! On Wed, Apr 1, 2015 at 11:51 PM, Esteban Gutierrez este...@cloudera.com wrote: Awesome! Congratulations, Srikanth! -- Cloudera, Inc. On Wed, Apr 1, 2015 at 11:02 AM, Ted Yu yuzhih...@gmail.com wrote: Congrats, Srikanth. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Please welcome new HBase committer Jing Chen (Jerry) He
Congrats, Jerry~ -Shaohui Liu On 04/02/2015 02:28 AM, Demai Ni wrote: Jerry, congratulations! well deserved On Wed, Apr 1, 2015 at 11:23 AM, Esteban Gutierrez este...@cloudera.com wrote: Congrats, Jerry! -- Cloudera, Inc. On Wed, Apr 1, 2015 at 10:55 AM, Ted Yu yuzhih...@gmail.com wrote: Congratulations, Jerry. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
RE: Please welcome new HBase committer Jing Chen (Jerry) He
Congratulations, Jerry! -Original Message- From: Andrew Purtell [mailto:apurt...@apache.org] Sent: 01 April 2015 23:23 To: dev@hbase.apache.org; u...@hbase.apache.org Subject: Please welcome new HBase committer Jing Chen (Jerry) He On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Resolved] (HBASE-13380) Cherry pick the HBASE-12808 compatibility checker tool back to 0.98+
[ https://issues.apache.org/jira/browse/HBASE-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-13380. Resolution: Fixed I cherry picked back HBASE-12808 (15a4738), HBASE-13340 (797573e), and HBASE-13341 (1632cd9) to branch-1.0, branch-1, and 0.98. Cherry pick the HBASE-12808 compatibility checker tool back to 0.98+ Key: HBASE-13380 URL: https://issues.apache.org/jira/browse/HBASE-13380 Project: HBase Issue Type: Task Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 1.1.0, 0.98.13, 1.0.2 The compatibility checker tool added to dev-support by HBASE-12808 can be cleanly cherry picked, in my experience, because it's a self contained change, so let's do this to every active branch that has a dev-support directory so RMs don't have to grab it from master for every release candidate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: Please welcome new HBase committer Srikanth Srungarapu
Congratulations, Srikanth! -Original Message- From: Andrew Purtell [mailto:apurt...@apache.org] Sent: 01 April 2015 23:23 To: dev@hbase.apache.org; u...@hbase.apache.org Subject: Please welcome new HBase committer Srikanth Srungarapu On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Created] (HBASE-13383) TestRegionServerObserver.testCoprocessorHooksInRegionsMerge zombie after HBASE-12975
Andrew Purtell created HBASE-13383:
--
Summary:
TestRegionServerObserver.testCoprocessorHooksInRegionsMerge zombie after
HBASE-12975
Key: HBASE-13383
URL: https://issues.apache.org/jira/browse/HBASE-13383
Project: HBase
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 2.0.0
Stuck here:
{noformat}
main prio=10 tid=0x7f3ff4008000 nid=0x6183 waiting on condition [0x7f3
ffa49e000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.coprocessor.TestRegionServerObserver.testCoprocessorHooksInRegionsMerge(TestRegionServerObserver.java:100)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-13384) Fix Javadoc warnings introduced by HBASE-12972
[
https://issues.apache.org/jira/browse/HBASE-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-13384.
Resolution: Fixed
Fix Version/s: 1.1.0
Fix Javadoc warnings introduced by HBASE-12972
--
Key: HBASE-13384
URL: https://issues.apache.org/jira/browse/HBASE-13384
Project: HBase
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Trivial
Fix For: 2.0.0, 1.1.0
Attachments: HBASE-13384.patch
Missed these new Javadoc warnings introduced by HBASE-12972 on master:
{noformat}
[WARNING] Javadoc Warnings
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-13384) Fix Javadoc warnings introduced by HBASE-12972
Andrew Purtell created HBASE-13384:
--
Summary: Fix Javadoc warnings introduced by HBASE-12972
Key: HBASE-13384
URL: https://issues.apache.org/jira/browse/HBASE-13384
Project: HBase
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Trivial
Fix For: 2.0.0
Missed these new Javadoc warnings introduced by HBASE-12972 on master:
{noformat}
[WARNING] Javadoc Warnings
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java:596:
warning - Tag @link: reference not found: HConstants#LATEST_TIMESTAMP
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-13386) Backport HBASE-12601 to all active branches other than master
Ashish Singhi created HBASE-13386: - Summary: Backport HBASE-12601 to all active branches other than master Key: HBASE-13386 URL: https://issues.apache.org/jira/browse/HBASE-13386 Project: HBase Issue Type: Sub-task Components: documentation, shell Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: Please welcome new HBase committer Jing Chen (Jerry) He
Congrats, Jerry. Regards, Abhishek -Original Message- From: Ted Yu [mailto:yuzhih...@gmail.com] Sent: 02 April 2015 01:56 To: u...@hbase.apache.org Cc: dev@hbase.apache.org Subject: Re: Please welcome new HBase committer Jing Chen (Jerry) He Congratulations, Jerry. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Created] (HBASE-13385) TestGenerateDelegationToken is broken with hadoop 2.8.0
zhangduo created HBASE-13385: Summary: TestGenerateDelegationToken is broken with hadoop 2.8.0 Key: HBASE-13385 URL: https://issues.apache.org/jira/browse/HBASE-13385 Project: HBase Issue Type: Bug Components: test Affects Versions: 2.0.0, 1.1.0 Reporter: zhangduo Assignee: zhangduo -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-13187) Add ITBLL that exercises per CF flush
[ https://issues.apache.org/jira/browse/HBASE-13187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-13187. --- Resolution: Fixed Release Note: Pass the -D flag generator.multiple.columnfamilies on the command-line if you want the generator to write three column families rather than the default one. When set, we will write the usual 'meta' column family and use it checking linked-list is wholesome but we will also write a 'tiny' column family and a 'big' column family to provoke uneven flushing; good for testing the flush-by-columnfamily feature. Hadoop Flags: Reviewed Pushed to branch-1+. Thanks for doing the extra work and some nice cleanup in PE (assigned you the issue). I should get to running this for a sustained period in next day or so. Thanks [~Apache9] Add ITBLL that exercises per CF flush - Key: HBASE-13187 URL: https://issues.apache.org/jira/browse/HBASE-13187 Project: HBase Issue Type: Task Components: integration tests Reporter: stack Assignee: zhangduo Priority: Critical Fix For: 2.0.0, 1.1.0 Attachments: 13187.txt, HBASE-13187_v1.patch Let me work on this. It would be excellent if we could have confidence to turn this on earlier rather than later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Rolling the next 0.98.12 RC tonight
It looks like issues have settled down and it's a good time to cut the next 0.98.12 RC tonight. Please let me know if you have any concerns. -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Please welcome new HBase committer Jing Chen (Jerry) He
On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Please welcome new HBase committer Srikanth Srungarapu
On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Resolved] (HBASE-12954) Ability impaired using HBase on multihomed hosts
[
https://issues.apache.org/jira/browse/HBASE-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved HBASE-12954.
Resolution: Fixed
Thanks for the review, Esteban.
Ability impaired using HBase on multihomed hosts
Key: HBASE-12954
URL: https://issues.apache.org/jira/browse/HBASE-12954
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.4
Reporter: Clay B.
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0, 1.1.0
Attachments: 12954-addendum.txt, 12954-branch-1-v14.txt,
12954-v1.txt, 12954-v10.txt, 12954-v11.txt, 12954-v12.txt, 12954-v12.txt,
12954-v12.txt, 12954-v13.txt, 12954-v14.txt, 12954-v7.txt, 12954-v8.txt,
Hadoop Three Interfaces.png
For HBase clusters running on unusual networks (such as NAT'd cloud
environments or physical machines with multiple IP's per network interface)
it would be ideal to have a way to both specify:
# which IP interface to which HBase master or region-server will bind
# what hostname HBase will advertise in Zookeeper both for a master or
region-server process
While efforts such as HBASE-8640 go a long way to normalize these two sources
of information, it is not possible in the current design of the properties
available to an administrator for these to be unambiguously specified.
One has been able to request {{hbase.master.ipc.address}} or
{{hbase.regionserver.ipc.address}} but one can not specify the desired HBase
{{hbase.master.hostname}}. (It was removed in HBASE-1357, further I am
unaware of a region-server equivalent.)
I use a configuration management system to generate all of my configuration
files on a per-machine basis. As such, an option to generate a file
specifying exactly which hostname to use would be helpful.
Today, specifying the bind address for HBase works and one can use an
HBase-only DNS for faking what to put in Zookeeper but this is far from
ideal. Network interfaces have no intrinsic IP address, nor hostname.
Specifing a DNS server is awkward as the DNS server may differ from the
system's resolver and is a single IP address. Similarly, on hosts which use a
transient VIP (e.g. through keepalived) for other services, it means there's
a seemingly non-deterministic hostname choice made by HBase depending on the
state of the VIP at daemon start-up time.
I will attach two networking examples I use which become very difficult to
manage under the current properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Please welcome new HBase committer Jing Chen (Jerry) He
Jerry, congratulations! well deserved On Wed, Apr 1, 2015 at 11:23 AM, Esteban Gutierrez este...@cloudera.com wrote: Congrats, Jerry! -- Cloudera, Inc. On Wed, Apr 1, 2015 at 10:55 AM, Ted Yu yuzhih...@gmail.com wrote: Congratulations, Jerry. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Please welcome new HBase committer Jing Chen (Jerry) He
Congratulations, Jerry. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Please welcome new HBase committer Srikanth Srungarapu
Congrats, Srikanth. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Created] (HBASE-13380) Cherry pick the HBASE-12808 compatibility checker tool back to 0.98+
Andrew Purtell created HBASE-13380: -- Summary: Cherry pick the HBASE-12808 compatibility checker tool back to 0.98+ Key: HBASE-13380 URL: https://issues.apache.org/jira/browse/HBASE-13380 Project: HBase Issue Type: Task Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 1.1.0, 1.0.2, 0.98.12 The compatibility checker tool added to dev-support by HBASE-12808 can be cleanly cherry picked, in my experience, because it's a self contained change, so let's do this to every active branch that has a dev-support directory so RMs don't have to grab it from master for every release candidate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-13381) Expand TestSizeFailures to include small scans
Josh Elser created HBASE-13381:
--
Summary: Expand TestSizeFailures to include small scans
Key: HBASE-13381
URL: https://issues.apache.org/jira/browse/HBASE-13381
Project: HBase
Issue Type: Improvement
Components: test
Reporter: Josh Elser
Assignee: Josh Elser
Priority: Minor
Fix For: 1.1.0, 2.2.0, 0.98.14, 1.0.2
From Jonathan on HBASE-13335:
{quote}
It may also be a good idea to extend TestSizeFailures so that it also tests to
ensure that all data is seen when the scan is small (e.g. perform that same
scan near the end with but configure it with Scan.setSmall(true)). Even though
that wouldn't be a small scan, it would test to make sure the fix behaves as
expected.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Please welcome new HBase committer Jing Chen (Jerry) He
Congrats, Jerry! -- Cloudera, Inc. On Wed, Apr 1, 2015 at 10:55 AM, Ted Yu yuzhih...@gmail.com wrote: Congratulations, Jerry. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Jerry He has accepted the PMC's invitation to become a committer on the project. We appreciate all of Jerry's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Jerry! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Please welcome new HBase committer Srikanth Srungarapu
Awesome! Congratulations, Srikanth! -- Cloudera, Inc. On Wed, Apr 1, 2015 at 11:02 AM, Ted Yu yuzhih...@gmail.com wrote: Congrats, Srikanth. On Wed, Apr 1, 2015 at 10:53 AM, Andrew Purtell apurt...@apache.org wrote: On behalf of the Apache HBase PMC, I am pleased to announce that Srikanth Srungarapu has accepted the PMC's invitation to become a committer on the project. We appreciate all of Srikanth's hard work and generous contributions thus far, and look forward to his continued involvement. Congratulations and welcome, Srikanth! -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Created] (HBASE-13382) IntegrationTestBigLinkedList should use SecureRandom
Todd Lipcon created HBASE-13382: --- Summary: IntegrationTestBigLinkedList should use SecureRandom Key: HBASE-13382 URL: https://issues.apache.org/jira/browse/HBASE-13382 Project: HBase Issue Type: Bug Components: integration tests Reporter: Todd Lipcon IntegrationTestBigLinkedList currently uses java.util.Random to generate its random keys. The keys are 128 bits long, but we generate them using Random.nextBytes(). The Random implementation itself only has a 48-bit seed, so even though we have a very long key string, it doesn't have anywhere near that amount of entropy. This means that after a few billion rows, it's quite likely to run into a collision: filling in a 16-byte key is equivalent to four calls to rand.nextInt(). So, for 10B rows, we are cycling through 40B different 'seed' values. With a 48-bit seed, it's quite likely we'll end up using the same seed twice, after which point any future rows generated by the colliding mappers are going to be equal. This results in broken chains and a failed verification job. The fix is simple -- we should use SecureRandom to generate the random keys, instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
