Re: What cause "Compaction is trying to add a bad range"

The fatal log happened at 15:48:57,398 Can you pastebin the log before that (w.r.t. StripeStoreFileManager) ? If you can reproduce this in unit test, that would be nice. Thanks

Re: What cause "Compaction is trying to add a bad range"

Here is my below all log 2016-04-26 15:48:57,396 INFO [regionserver/ regionserver.SplitLogWorker: Sending interrupt to stop the worker thread 2016-04-26 15:48:57,398 FATAL [MemStoreFlusher.1] regionserver.HRegionServer: RegionServer abort: loaded coprocessors are: [] 2016-04-26 15:48:57,399

[ANNOUNCE] PhoenixCon 2016 on Wed, May 25th 9am-1pm

We invite you to attend the inaugural PhoenixCon on Wed, May 25th 9am-1pm (the day after HBaseCon) hosted by Salesforce.com in San Francisco. There will be two tracks: one for use cases and one for internals. Drop me a note if you're interested in giving a talk. To RSVP and for more details, see

Re: API compatibility history for HBase

Looks useful. Link from our docs? Enis On Tue, Apr 26, 2016 at 2:56 PM, Sean Busbey wrote: > Hi Folks! > > The developer behind the Java API Compatibility Checker tool has been > working on tools to show API changes over time. He was gracious enough > to add us to his list

[jira] [Created] (HBASE-15720) Print row locks at the debug dump page

Enis Soztutar created HBASE-15720: - Summary: Print row locks at the debug dump page Key: HBASE-15720 URL: https://issues.apache.org/jira/browse/HBASE-15720 Project: HBase Issue Type:

Re: API compatibility history for HBase

Woah, what's was this ? 0.96.0 2013-10-12 changelog 51.63% 50.21%

[jira] [Created] (HBASE-15719) TestMasterCoprocessorExceptionWithAbort#testExceptionFromCoprocessorWhenCreatingTable fails due to premature master abortion

Ted Yu created HBASE-15719: -- Summary: TestMasterCoprocessorExceptionWithAbort#testExceptionFromCoprocessorWhenCreatingTable fails due to premature master abortion Key: HBASE-15719 URL:

Re: API compatibility history for HBase

This is awesome! Andrey originally added annotation support in Java ACC for us and it looks like he hasn’t stopped being great since then. :) -Dima On Tue, Apr 26, 2016 at 2:56 PM, Sean Busbey wrote: > Hi Folks! > > The developer behind the Java API Compatibility Checker

API compatibility history for HBase

Hi Folks! The developer behind the Java API Compatibility Checker tool has been working on tools to show API changes over time. He was gracious enough to add us to his list of examples: http://abi-laboratory.pro/java/tracker/timeline/hbase/ -- busbey

[jira] [Created] (HBASE-15718) Add on TableName implementation and tests

Elliott Clark created HBASE-15718: - Summary: Add on TableName implementation and tests Key: HBASE-15718 URL: https://issues.apache.org/jira/browse/HBASE-15718 Project: HBase Issue Type:

[jira] [Created] (HBASE-15717) TestClassLoading#testMasterCoprocessorsReported fails due to Master Coprocessors mismatch

Ted Yu created HBASE-15717: -- Summary: TestClassLoading#testMasterCoprocessorsReported fails due to Master Coprocessors mismatch Key: HBASE-15717 URL: https://issues.apache.org/jira/browse/HBASE-15717

[jira] [Created] (HBASE-15716) HRegion#RegionScannerImpl scannerReadPoints synchronization costs

stack created HBASE-15716: - Summary: HRegion#RegionScannerImpl scannerReadPoints synchronization costs Key: HBASE-15716 URL: https://issues.apache.org/jira/browse/HBASE-15716 Project: HBase Issue

[jira] [Resolved] (HBASE-14363) Print more details on the row behind an Empty REGIONINFO_QUALIFIER warning

[ https://issues.apache.org/jira/browse/HBASE-14363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-14363. --- Resolution: Not A Problem Not a problem anymore Thanks [~mwarhaftig] (and [~qwertymaniac]) > Print more

[jira] [Resolved] (HBASE-15477) Do not save 'next block header' when we cache hfileblocks

[ https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-15477. --- Resolution: Fixed Re-resolving. For backport, do HBASE-15713 instead. > Do not save 'next block header'

[jira] [Created] (HBASE-15713) Backport "HBASE-15477 Do not save 'next block header' when we cache hfileblocks"

stack created HBASE-15713: - Summary: Backport "HBASE-15477 Do not save 'next block header' when we cache hfileblocks" Key: HBASE-15713 URL: https://issues.apache.org/jira/browse/HBASE-15713 Project: HBase

[jira] [Created] (HBASE-15712) Tool for retiring empty regions

Nick Dimiduk created HBASE-15712: Summary: Tool for retiring empty regions Key: HBASE-15712 URL: https://issues.apache.org/jira/browse/HBASE-15712 Project: HBase Issue Type: Task

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around

[jira] [Created] (HBASE-15710) Include issue servers information in RetriesExhaustedWithDetailsException message

Yu Li created HBASE-15710: - Summary: Include issue servers information in RetriesExhaustedWithDetailsException message Key: HBASE-15710 URL: https://issues.apache.org/jira/browse/HBASE-15710 Project: HBase

Re: What cause "Compaction is trying to add a bad range"

Can you pastebin region server log leading up to the exception below ? Thanks > On Apr 26, 2016, at 5:19 AM, 曾伟展 wrote: > > Hi, ALL > >I used PE to test HBase-1.1.2 ，and cause many regionserver died ! > > here is my log: > > FATAL [MemStoreFlusher.1]

What cause "Compaction is trying to add a bad range"

Hi, ALL I used PE to test HBase-1.1.2 ，and cause many regionserver died ! here is my log: FATAL [MemStoreFlusher.1] regionserver.HRegionServer: ABORTING region server MyIP Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: