[jira] [Created] (HBASE-4933) Ability to calculate the blockcache hit ratio for the last few minutes
Ability to calculate the blockcache hit ratio for the last few minutes -- Key: HBASE-4933 URL: https://issues.apache.org/jira/browse/HBASE-4933 Project: HBase Issue Type: Improvement Components: metrics Reporter: dhruba borthakur Assignee: dhruba borthakur The metric blockcacheHitRatio is since the beginning of time. It would be nice to calculate the block cache hit ratio for the past few minutes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4712) Document rules for writing tests
[ https://issues.apache.org/jira/browse/HBASE-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161470#comment-13161470 ] Jesse Yates commented on HBASE-4712: bq. As most as possible, tests should use the default settings for the cluster. When they don't, they should document it. This will allow to share the cluster later. It would be cool if we could actually do that with the annotation. For instance: @LargeTest(modifications=false) would be a large test that hasn't made modifications to the minicluster. Makes it really easy to parallelize in the same jvm later. Another component I could see needing for the same jvm minicluster is a getUniqueTable() method. But lets put that off until we actually get there :) > Document rules for writing tests > > > Key: HBASE-4712 > URL: https://issues.apache.org/jira/browse/HBASE-4712 > Project: HBase > Issue Type: Task > Components: test >Affects Versions: 0.92.0 >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > > We saw that some tests could be improved. Documenting the general rules could > help. > Proposal: > HBase tests are divided in three categories: small, medium and large, with > corresponding JUnit categories: SmallTest, MediumTest, LargeTest > Small tests are executed in parallel in a shared JVM. They must last less > than 15 seconds. They must NOT use a cluster. > Medium tests are executed in separate JVM. They must last less than 50 > seconds. They can use a cluster. They must not fail occasionally. > Small and medium tests must not need more than 30 minutes to run altogether. > Small and medium tests should be executed by the developers before submitting > a patch. > Large tests are everything else. They are typically integration tests, > non-regression tests for specific bugs, timeout tests, performance tests. > Tests rules & hints are: > - As most as possible, tests should be written as small tests. > - All tests should be written to support parallel execution on the same > machine, hence should not use shared resources as fixed ports or fixed file > names. > - All tests should be written to be as fast as possible. > - Tests should not overlog. More than 100 lines/second makes the logs complex > to read and use i/o that are hence not available for the other tests. > - Tests can be written with HBaseTestingUtility . This class offers helper > function to create a temp directory and do the cleanup, or to start a cluster. > - Sleeps: > - Tests should not do a 'Thread.sleep' without testing an ending > condition. This allows understanding what the test is waiting for. Moreover, > the test will work whatever the machine performances. > - Sleep should be minimal to be as fast as possible. Waiting for a > variable should be done in a 40ms sleep loop. Waiting for a socket operation > should be done in a 200 ms sleep loop. > - Tests using cluster: > - Tests using a HRegion do not have to start a cluster: A region can use > the local file system. > - Start/stopping a cluster cost around 10 seconds. They should not be > started per test method but per class. > - Started cluster must be shutdown using > HBaseTestingUtility#shutdownMiniCluster, which cleans the directories. > - As most as possible, tests should use the default settings for the > cluster. When they don't, they should document it. This will allow to share > the cluster later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4925) Collect test cases for hadoop/hbase cluster
[ https://issues.apache.org/jira/browse/HBASE-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161466#comment-13161466 ] Thomas Pan commented on HBASE-4925: --- Once framework is available, we will write them. Regardless, we plan to carry out these tests to mainly achieve two goals: 1. To build up the experiences on how to handle various outages before production launch, which we plan to share with the community once we have more details. 2. To reveal more issues in the code base so that the community could fix them. Last time, Todd found more HBase bugs while helping us recover from one big outage. > Collect test cases for hadoop/hbase cluster > --- > > Key: HBASE-4925 > URL: https://issues.apache.org/jira/browse/HBASE-4925 > Project: HBase > Issue Type: Brainstorming > Components: test >Reporter: Thomas Pan > > This entry is used to collect all the useful test cases to verify a > hadoop/hbase cluster. This is to follow up on yesterday's hack day in > Salesforce. Hopefully that the information would be very useful for the whole > community. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4712) Document rules for writing tests
[
https://issues.apache.org/jira/browse/HBASE-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161464#comment-13161464
]
Jesse Yates commented on HBASE-4712:
Couple of comments:
bq. there is one report for small tests and one report for medium and large
tests if they are executed
Is that one report each for the medium and large or one report for the two?
Just need a single word of clarification in there
bq. 1.3) mvn test -P localTests -Dtest=myTests
Is this new behavior from what's in trunk currently? Because I'm pretty sure I
can just run
mvn test -Dtest=myTest and get it to run them.
{quote}
mvn test -P runMediumTests - execute medium tests in a single JVM.
mvn test -P runLargeTests - execute medium tests in a single JVM.
{quote}
I don't think we really want to have these options available, right? A lot of
the large tests depend on the fact that jvms are forked.
bq. Categories and execution time
A simple example or two here with the annotations would make this super
obvious. For example:
{quote}
a small test would look like this:
@SmallTest
public class TestMyClass{
...
}
Or you could test each method:
public class TestMyClass{
@SmallTest
public void testMyMethod() ...
}
{quote}
This is assuming the per-method annotation still work as Todd suggested a while
ago?
bq. Tests using a HRegion do not have to start a cluster: A region can use the
local file system.
Do we need to add a MiniRegion just for testing these situations?
Otherwise, I'm fine with the rest of the comments.
However, with recent discussions(http://search-hadoop.com/m/q41O6YiyfN), there
may be some changes coming to this soon.
> Document rules for writing tests
>
>
> Key: HBASE-4712
> URL: https://issues.apache.org/jira/browse/HBASE-4712
> Project: HBase
> Issue Type: Task
> Components: test
>Affects Versions: 0.92.0
>Reporter: nkeywal
>Assignee: nkeywal
>Priority: Minor
>
> We saw that some tests could be improved. Documenting the general rules could
> help.
> Proposal:
> HBase tests are divided in three categories: small, medium and large, with
> corresponding JUnit categories: SmallTest, MediumTest, LargeTest
> Small tests are executed in parallel in a shared JVM. They must last less
> than 15 seconds. They must NOT use a cluster.
> Medium tests are executed in separate JVM. They must last less than 50
> seconds. They can use a cluster. They must not fail occasionally.
> Small and medium tests must not need more than 30 minutes to run altogether.
> Small and medium tests should be executed by the developers before submitting
> a patch.
> Large tests are everything else. They are typically integration tests,
> non-regression tests for specific bugs, timeout tests, performance tests.
> Tests rules & hints are:
> - As most as possible, tests should be written as small tests.
> - All tests should be written to support parallel execution on the same
> machine, hence should not use shared resources as fixed ports or fixed file
> names.
> - All tests should be written to be as fast as possible.
> - Tests should not overlog. More than 100 lines/second makes the logs complex
> to read and use i/o that are hence not available for the other tests.
> - Tests can be written with HBaseTestingUtility . This class offers helper
> function to create a temp directory and do the cleanup, or to start a cluster.
> - Sleeps:
> - Tests should not do a 'Thread.sleep' without testing an ending
> condition. This allows understanding what the test is waiting for. Moreover,
> the test will work whatever the machine performances.
> - Sleep should be minimal to be as fast as possible. Waiting for a
> variable should be done in a 40ms sleep loop. Waiting for a socket operation
> should be done in a 200 ms sleep loop.
> - Tests using cluster:
> - Tests using a HRegion do not have to start a cluster: A region can use
> the local file system.
> - Start/stopping a cluster cost around 10 seconds. They should not be
> started per test method but per class.
> - Started cluster must be shutdown using
> HBaseTestingUtility#shutdownMiniCluster, which cleans the directories.
> - As most as possible, tests should use the default settings for the
> cluster. When they don't, they should document it. This will allow to share
> the cluster later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4931) CopyTable instructions are out of date in book and usage in source.
[
https://issues.apache.org/jira/browse/HBASE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-4931:
--
Summary: CopyTable instructions are out of date in book and usage in
source. (was: CopyTable instructions are of date in book and usage in source.)
> CopyTable instructions are out of date in book and usage in source.
> ---
>
> Key: HBASE-4931
> URL: https://issues.apache.org/jira/browse/HBASE-4931
> Project: HBase
> Issue Type: Bug
> Components: util
>Affects Versions: 0.90.4, 0.92.0
>Reporter: Jonathan Hsieh
>
> The book and the usage instructions refer to ReplicationRegionInterface and
> ReplicationRegionServer which are no longer present in the 0.90+ versions.
> {code}
> $ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
> --rs.class=org.apache.hadoop.hbase.ipc.ReplicationRegionInterface
> --rs.impl=org.apache.hadoop.hbase.regionserver.replication.ReplicationRegionServer
> --starttime=1265875194289 --endtime=1265878794289
> --peer.adr=server1,server2,server3:2181:/hbase TestTable
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4844) Coprocessor hooks for log rolling
[ https://issues.apache.org/jira/browse/HBASE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161461#comment-13161461 ] stack commented on HBASE-4844: -- A pre could alter the edit? Remove it? Accumulate a bunch of them and do some summing before letting it out into the WAL? > Coprocessor hooks for log rolling > - > > Key: HBASE-4844 > URL: https://issues.apache.org/jira/browse/HBASE-4844 > Project: HBase > Issue Type: New Feature >Affects Versions: 0.94.0 >Reporter: Lars Hofhansl >Priority: Minor > > In order to eventually do point in time recovery we need a way to reliably > back up the logs. Rather than adding some hard coded changes, we can provide > coprocessor hooks and folks can implement their own policies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4844) Coprocessor hooks for log rolling
[ https://issues.apache.org/jira/browse/HBASE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161462#comment-13161462 ] stack commented on HBASE-4844: -- Adding a WALObserver would necessitate adding the implementation to classpath and restarting regionserver? > Coprocessor hooks for log rolling > - > > Key: HBASE-4844 > URL: https://issues.apache.org/jira/browse/HBASE-4844 > Project: HBase > Issue Type: New Feature >Affects Versions: 0.94.0 >Reporter: Lars Hofhansl >Priority: Minor > > In order to eventually do point in time recovery we need a way to reliably > back up the logs. Rather than adding some hard coded changes, we can provide > coprocessor hooks and folks can implement their own policies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4925) Collect test cases for hadoop/hbase cluster
[ https://issues.apache.org/jira/browse/HBASE-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161460#comment-13161460 ] stack commented on HBASE-4925: -- That is a pretty nice list Thomas. Thanks. You have a means of running these scenarios now or you are waiting on framework in which you/we could write them? > Collect test cases for hadoop/hbase cluster > --- > > Key: HBASE-4925 > URL: https://issues.apache.org/jira/browse/HBASE-4925 > Project: HBase > Issue Type: Brainstorming > Components: test >Reporter: Thomas Pan > > This entry is used to collect all the useful test cases to verify a > hadoop/hbase cluster. This is to follow up on yesterday's hack day in > Salesforce. Hopefully that the information would be very useful for the whole > community. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4921) HTable initialization looks for EMPTY_START_ROW
[
https://issues.apache.org/jira/browse/HBASE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161458#comment-13161458
]
stack commented on HBASE-4921:
--
@Pritam I think that line an old one and its purpose is yes a check the table
can be reached. Maybe this shouldn't be in HTable constructor at all? In
other words, let the table instance construct w/o going to the cluster. Its
probably a pretty radical change -- my guess is that a bunch of unit tests
would start breaking -- but makes sense.
> HTable initialization looks for EMPTY_START_ROW
> ---
>
> Key: HBASE-4921
> URL: https://issues.apache.org/jira/browse/HBASE-4921
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.4
>Reporter: Pritam Damania
>
> The HTable initialization does something like this :
> {code}this.connection.locateRegion(tableName,
> HConstants.EMPTY_START_ROW);{code}
> What is the rationale behind this ? What would happen if this region is in
> flight ? I ran into a problem where I disabled the first region of the table
> and now I can't create an HTable instance to this table.
> Disabling the first region is like disabling the entire table from a client
> perspective. I feel this is not the correct behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161455#comment-13161455 ] stack commented on HBASE-4847: -- I don't think the above failures because of your patch N. Trying it here... > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch, > 4847_pom.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, > 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4932) Block cache can be mistakenly instantiated by tools
[ https://issues.apache.org/jira/browse/HBASE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161450#comment-13161450 ] stack commented on HBASE-4932: -- Yeah. This is actually a pain. Master splitting WALs used to be creating blockcaches until ugly-hacked it not too. > Block cache can be mistakenly instantiated by tools > --- > > Key: HBASE-4932 > URL: https://issues.apache.org/jira/browse/HBASE-4932 > Project: HBase > Issue Type: Bug >Reporter: Prakash Khemani >Assignee: Prakash Khemani > > Map Reduce tasks that create a writer to write HFiles inadvertently end up > creating block cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4927) CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the last region when the endkey is empty
[ https://issues.apache.org/jira/browse/HBASE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161449#comment-13161449 ] stack commented on HBASE-4927: -- When we sort, we don't consider endkey, no? Its startkey and timestamp? > CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the > last region when the endkey is empty > --- > > Key: HBASE-4927 > URL: https://issues.apache.org/jira/browse/HBASE-4927 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > > When reviewing HBASE-4238 backporting, Jon found this issue. > What happens if the split points are (empty end key is the last key, empty > start key is the first key) > Parent [A,) > L daughter [A,B), > R daughter [B,) > When sorted, we gets to end key comparision which results in this incorrector > order: > [A,B), [A,), [B,) > we wanted: > [A,), [A,B), [B,) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161448#comment-13161448 ] stack commented on HBASE-4930: -- Man, your screenshot broke all hbase unit tests Doug! +1 on patch though, is the FAQ the right place to go get more info? Maybe point them at the manual, downloads and mailing lists instead? Or leave off this section (the 'more info' is all in the left-hand-side menu) > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index.html, index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161446#comment-13161446 ] stack commented on HBASE-4930: -- Man, your screenshot broke all hbase unit tests Doug! +1 on patch though, is the FAQ the right place to go get more info? Maybe point them at the manual, downloads and mailing lists instead? Or leave off this section (the 'more info' is all in the left-hand-side menu) > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index.html, index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161447#comment-13161447 ] stack commented on HBASE-4930: -- Man, your screenshot broke all hbase unit tests Doug! +1 on patch though, is the FAQ the right place to go get more info? Maybe point them at the manual, downloads and mailing lists instead? Or leave off this section (the 'more info' is all in the left-hand-side menu) > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index.html, index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4932) Block cache can be mistakenly instantiated by tools
Block cache can be mistakenly instantiated by tools --- Key: HBASE-4932 URL: https://issues.apache.org/jira/browse/HBASE-4932 Project: HBase Issue Type: Bug Reporter: Prakash Khemani Map Reduce tasks that create a writer to write HFiles inadvertently end up creating block cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161445#comment-13161445 ] stack commented on HBASE-4930: -- Man, your screenshot broke all hbase unit tests Doug! +1 on patch though, is the FAQ the right place to go get more info? Maybe point them at the manual, downloads and mailing lists instead? Or leave off this section (the 'more info' is all in the left-hand-side menu) > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index.html, index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-4932) Block cache can be mistakenly instantiated by tools
[ https://issues.apache.org/jira/browse/HBASE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Khemani reassigned HBASE-4932: -- Assignee: Prakash Khemani > Block cache can be mistakenly instantiated by tools > --- > > Key: HBASE-4932 > URL: https://issues.apache.org/jira/browse/HBASE-4932 > Project: HBase > Issue Type: Bug >Reporter: Prakash Khemani >Assignee: Prakash Khemani > > Map Reduce tasks that create a writer to write HFiles inadvertently end up > creating block cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4899) Region would be assigned twice easily with continually killing server and moving region in testing environment
[
https://issues.apache.org/jira/browse/HBASE-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4899:
-
Resolution: Fixed
Fix Version/s: 0.92.1
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Applied to trunk and 0.92 branch. I ran all tests and first time a
TestReplication failed. Its failing on trunk and 0.92 at mo. Second time I
ran it all tests passed. Thanks for the patch Chunhui.
> Region would be assigned twice easily with continually killing server and
> moving region in testing environment
> ---
>
> Key: HBASE-4899
> URL: https://issues.apache.org/jira/browse/HBASE-4899
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.1
>Reporter: chunhui shen
>Assignee: chunhui shen
>Priority: Critical
> Fix For: 0.92.1
>
> Attachments: hbase-4899.patch, hbase-4899v2.patch, hbase-4899v3.patch
>
>
> Before assigning region in ServerShutdownHandler#process, it will check
> whether region is in RIT,
> however, this checking doesn't work as the excepted in the following case:
> 1.move region A from server B to server C
> 2.kill server B
> 3.start server B immediately
> Let's see what happen in the code for the above case
> {code}
> for step1:
> 1.1 server B close the region A,
> 1.2 master setOffline for region
> A,(AssignmentManager#setOffline:this.regions.remove(regionInfo))
> 1.3 server C start to open region A.(Not completed)
> for step3:
> master ServerShutdownHandler#process() for server B
> {
> ..
> splitlog()
> ...
> List regionsInTransition =
> this.services.getAssignmentManager()
> .processServerShutdown(this.serverName);
> ...
> Skip regions that were in transition unless CLOSING or PENDING_CLOSE
> ...
> assign region
> }
> {code}
> In fact, when running
> ServerShutdownHandler#process()#this.services.getAssignmentManager().processServerShutdown(this.serverName),
> region A is in RIT (step1.3 not completed), but the return List
> regionsInTransition doesn't contain it, because region A has removed from
> AssignmentManager.regions by AssignmentManager#setOffline in step 1.2
> Therefore, region A will be assigned twice.
> Actually, one server killed and started twice will also easily cause region
> assigned twice.
> Exclude the above reason, another probability :
> when execute ServerShutdownHandler#process()#MetaReader.getServerUserRegions
> ,region is included which is in RIT now.
> But after completing MetaReader.getServerUserRegions, the region has been
> opened in other server and is not in RIT now.
> In our testing environment where balancing,moving and killing are executed
> periodly, assigning region twice often happens, and it is hateful because it
> will affect other test cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4903) Return a result from RegionObserver.preIncrement()
[ https://issues.apache.org/jira/browse/HBASE-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161433#comment-13161433 ] Lars Hofhansl commented on HBASE-4903: -- addendum committed to 0.92 and trunk. > Return a result from RegionObserver.preIncrement() > -- > > Key: HBASE-4903 > URL: https://issues.apache.org/jira/browse/HBASE-4903 > Project: HBase > Issue Type: Improvement >Reporter: Daniel Gómez Ferro > Fix For: 0.94.0, 0.92.1 > > Attachments: 4903-add.txt, HBASE-4903-0.92.patch, HBASE-4903.patch, > HBASE-4903.patch > > > The only way to return a result from RegionObserver.preIncrement() is to use > Result.readFields() after serializing the correct result. > This can be fixed either returning a Result object from that function or > adding setters to Result. Another option is to modify the parameters and > receive a List as preGet() does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4903) Return a result from RegionObserver.preIncrement()
[ https://issues.apache.org/jira/browse/HBASE-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-4903: - Attachment: 4903-add.txt Addendum for the security build (both 0.92 and trunk). > Return a result from RegionObserver.preIncrement() > -- > > Key: HBASE-4903 > URL: https://issues.apache.org/jira/browse/HBASE-4903 > Project: HBase > Issue Type: Improvement >Reporter: Daniel Gómez Ferro > Fix For: 0.94.0, 0.92.1 > > Attachments: 4903-add.txt, HBASE-4903-0.92.patch, HBASE-4903.patch, > HBASE-4903.patch > > > The only way to return a result from RegionObserver.preIncrement() is to use > Result.readFields() after serializing the correct result. > This can be fixed either returning a Result object from that function or > adding setters to Result. Another option is to modify the parameters and > receive a List as preGet() does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4918) HTablePool Constructor may cause unintended behavior
[
https://issues.apache.org/jira/browse/HBASE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161419#comment-13161419
]
Hudson commented on HBASE-4918:
---
Integrated in HBase-TRUNK-security #18 (See
[https://builds.apache.org/job/HBase-TRUNK-security/18/])
HBASE-4918 HTablePool Constructor may cause unintended behavior
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
> HTablePool Constructor may cause unintended behavior
>
>
> Key: HBASE-4918
> URL: https://issues.apache.org/jira/browse/HBASE-4918
> Project: HBase
> Issue Type: Bug
> Components: client
> Environment: r1125533
>Reporter: Kitora, Naoki
> Fix For: 0.92.0
>
> Attachments: HTablePool.java.patch
>
>
> {code:title=HTablePool.java}
> 96 public HTablePool(final Configuration config, final int maxSize,
> 97 final HTableInterfaceFactory tableFactory) {
> 98 this(config, maxSize, null, PoolType.Reusable);
> 99 }
> {code}
> I think that 3rd argument in line 98 should be "tableFactory".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4903) Return a result from RegionObserver.preIncrement()
[ https://issues.apache.org/jira/browse/HBASE-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161418#comment-13161418 ] Hudson commented on HBASE-4903: --- Integrated in HBase-TRUNK-security #18 (See [https://builds.apache.org/job/HBase-TRUNK-security/18/]) HBASE-4903 Return a result from RegionObserver.preIncrement (Daniel Gómez Ferro) larsh : Files : * /hbase/trunk/CHANGES.txt * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseRegionObserver.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/RegionCoprocessorHost.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/coprocessor/SimpleRegionObserver.java > Return a result from RegionObserver.preIncrement() > -- > > Key: HBASE-4903 > URL: https://issues.apache.org/jira/browse/HBASE-4903 > Project: HBase > Issue Type: Improvement >Reporter: Daniel Gómez Ferro > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-4903-0.92.patch, HBASE-4903.patch, HBASE-4903.patch > > > The only way to return a result from RegionObserver.preIncrement() is to use > Result.readFields() after serializing the correct result. > This can be fixed either returning a Result object from that function or > adding setters to Result. Another option is to modify the parameters and > receive a List as preGet() does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4928) [book] overhaul FAQ
[ https://issues.apache.org/jira/browse/HBASE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161420#comment-13161420 ] Hudson commented on HBASE-4928: --- Integrated in HBase-TRUNK-security #18 (See [https://builds.apache.org/job/HBase-TRUNK-security/18/]) hbase-4928. overhauled FAQ in book. > [book] overhaul FAQ > --- > > Key: HBASE-4928 > URL: https://issues.apache.org/jira/browse/HBASE-4928 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: book_HBASE_4928.xml.patch > > > Overhauled the FAQ in the book and aligned the groups of questions to the way > the book is aligned (e.g., configuration, schema design, performance, etc.) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4918) HTablePool Constructor may cause unintended behavior
[
https://issues.apache.org/jira/browse/HBASE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161417#comment-13161417
]
Hudson commented on HBASE-4918:
---
Integrated in HBase-0.92-security #28 (See
[https://builds.apache.org/job/HBase-0.92-security/28/])
HBASE-4918 HTablePool Constructor may cause unintended behavior
HBASE-4918 HTablePool Constructor may cause unintended behavior
stack :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
> HTablePool Constructor may cause unintended behavior
>
>
> Key: HBASE-4918
> URL: https://issues.apache.org/jira/browse/HBASE-4918
> Project: HBase
> Issue Type: Bug
> Components: client
> Environment: r1125533
>Reporter: Kitora, Naoki
> Fix For: 0.92.0
>
> Attachments: HTablePool.java.patch
>
>
> {code:title=HTablePool.java}
> 96 public HTablePool(final Configuration config, final int maxSize,
> 97 final HTableInterfaceFactory tableFactory) {
> 98 this(config, maxSize, null, PoolType.Reusable);
> 99 }
> {code}
> I think that 3rd argument in line 98 should be "tableFactory".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4903) Return a result from RegionObserver.preIncrement()
[ https://issues.apache.org/jira/browse/HBASE-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161416#comment-13161416 ] Hudson commented on HBASE-4903: --- Integrated in HBase-0.92-security #28 (See [https://builds.apache.org/job/HBase-0.92-security/28/]) HBASE-4903 Return a result from RegionObserver.preIncrement (Daniel Gómez Ferro) larsh : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseRegionObserver.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/RegionCoprocessorHost.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/coprocessor/SimpleRegionObserver.java > Return a result from RegionObserver.preIncrement() > -- > > Key: HBASE-4903 > URL: https://issues.apache.org/jira/browse/HBASE-4903 > Project: HBase > Issue Type: Improvement >Reporter: Daniel Gómez Ferro > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-4903-0.92.patch, HBASE-4903.patch, HBASE-4903.patch > > > The only way to return a result from RegionObserver.preIncrement() is to use > Result.readFields() after serializing the correct result. > This can be fixed either returning a Result object from that function or > adding setters to Result. Another option is to modify the parameters and > receive a List as preGet() does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161400#comment-13161400 ] Hadoop QA commented on HBASE-4930: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505822/index_HBASE_4930.xml.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. -1 javadoc. The javadoc tool appears to have generated -160 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.master.TestRollingRestart org.apache.hadoop.hbase.util.TestRegionSplitter org.apache.hadoop.hbase.client.TestMultiParallel org.apache.hadoop.hbase.master.TestRestartCluster org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler org.apache.hadoop.hbase.client.TestInstantSchemaChange org.apache.hadoop.hbase.regionserver.wal.TestHLogBench org.apache.hadoop.hbase.rest.TestGzipFilter org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD org.apache.hadoop.hbase.regionserver.TestAtomicOperation org.apache.hadoop.hbase.rest.TestScannersWithFilters org.apache.hadoop.hbase.TestInfoServers org.apache.hadoop.hbase.regionserver.TestParallelPut org.apache.hadoop.hbase.coprocessor.TestClassLoading org.apache.hadoop.hbase.client.TestAdmin org.apache.hadoop.hbase.regionserver.wal.TestLogRolling org.apache.hadoop.hbase.filter.TestColumnRangeFilter org.apache.hadoop.hbase.mapred.TestTableInputFormat org.apache.hadoop.hbase.client.TestHCM org.apache.hadoop.hbase.regionserver.TestStoreFileBlockCacheSummary org.apache.hadoop.hbase.util.hbck.TestOfflineMetaRebuildHole org.apache.hadoop.hbase.coprocessor.TestMasterObserver org.apache.hadoop.hbase.rest.TestStatusResource org.apache.hadoop.hbase.TestRegionRebalancing org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort org.apache.hadoop.hbase.rest.TestVersionResource org.apache.hadoop.hbase.client.TestScannerTimeout org.apache.hadoop.hbase.client.TestFromClientSide org.apache.hadoop.hbase.regionserver.TestFSErrorsExposed org.apache.hadoop.hbase.coprocessor.TestAggregateProtocol org.apache.hadoop.hbase.rest.TestRowResource org.apache.hadoop.hbase.rest.TestScannerResource org.apache.hadoop.hbase.ipc.TestDelayedRpc org.apache.hadoop.hbase.rest.client.TestRemoteAdmin org.apache.hadoop.hbase.util.TestFSUtils org.apache.hadoop.hbase.master.TestDistributedLogSplitting org.apache.hadoop.hbase.rest.TestTableResource org.apache.hadoop.hbase.regionserver.wal.TestWALReplay org.apache.hadoop.hbase.master.TestHMasterRPCException org.apache.hadoop.hbase.util.TestIdLock org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster org.apache.hadoop.hbase.rest.TestTransform org.apache.hadoop.hbase.coprocessor.TestCoprocessorEndpoint org.apache.hadoop.hbase.client.TestInstantSchemaChangeSplit org.apache.hadoop.hbase.regionserver.TestHRegion org.apache.hadoop.hbase.regionserver.TestReadWriteConsistencyControl org.apache.hadoop.hbase.client.TestMultipleTimestamps org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort org.apache.hadoop.hbase.catalog.TestMetaReaderEditor org.apache.hadoop.hbase.regionserver.TestHRegionServerBulkLoad org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster org.apache.hadoop.hbase.mapreduce.TestTimeRangeMapRed org.apache.hadoop.hbase.client.TestMetaScanner org.apache.hadoop.hbase.io.hfile.TestHFileBlock org.apache.hadoop.hbase.client.TestTimestampsFilter org.apache.hadoop.hbase.client.TestI
[jira] [Updated] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4930: - Attachment: index.html attaching a generated version of the index page so people can see what it will look like. > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index.html, index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4931) CopyTable instructions are of date in book and usage in source.
[
https://issues.apache.org/jira/browse/HBASE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161355#comment-13161355
]
Jonathan Hsieh commented on HBASE-4931:
---
* Docs should give warning about zoo.cfg settings vs hbase-site.xml settings.
* Docs should say requires same/compatible versions of hbase.
* Run time warning if there are unexpected arguments (or typos)
> CopyTable instructions are of date in book and usage in source.
> ---
>
> Key: HBASE-4931
> URL: https://issues.apache.org/jira/browse/HBASE-4931
> Project: HBase
> Issue Type: Bug
> Components: util
>Affects Versions: 0.90.4, 0.92.0
>Reporter: Jonathan Hsieh
>
> The book and the usage instructions refer to ReplicationRegionInterface and
> ReplicationRegionServer which are no longer present in the 0.90+ versions.
> {code}
> $ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
> --rs.class=org.apache.hadoop.hbase.ipc.ReplicationRegionInterface
> --rs.impl=org.apache.hadoop.hbase.regionserver.replication.ReplicationRegionServer
> --starttime=1265875194289 --endtime=1265878794289
> --peer.adr=server1,server2,server3:2181:/hbase TestTable
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4614) Can't CopyTable between clusters if zoo.cfg is on the classpath
[ https://issues.apache.org/jira/browse/HBASE-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161353#comment-13161353 ] Jonathan Hsieh commented on HBASE-4614: --- Good thread from Lars G on zoo.cfg: http://comments.gmane.org/gmane.comp.java.hadoop.hbase.devel/22462 > Can't CopyTable between clusters if zoo.cfg is on the classpath > --- > > Key: HBASE-4614 > URL: https://issues.apache.org/jira/browse/HBASE-4614 > Project: HBase > Issue Type: Bug >Affects Versions: 0.90.4 >Reporter: Jean-Daniel Cryans > Fix For: 0.94.0 > > > Kinger on IRC found out that it's currently impossible to CopyTable between > clusters if there's a zoo.cfg on the classpath as it will take precedence > over the --peer.adr or whatever else the user passes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4928) [book] overhaul FAQ
[ https://issues.apache.org/jira/browse/HBASE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161346#comment-13161346 ] Hudson commented on HBASE-4928: --- Integrated in HBase-TRUNK #2507 (See [https://builds.apache.org/job/HBase-TRUNK/2507/]) hbase-4928. overhauled FAQ in book. > [book] overhaul FAQ > --- > > Key: HBASE-4928 > URL: https://issues.apache.org/jira/browse/HBASE-4928 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: book_HBASE_4928.xml.patch > > > Overhauled the FAQ in the book and aligned the groups of questions to the way > the book is aligned (e.g., configuration, schema design, performance, etc.) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4931) CopyTable instructions are of date in book and usage in source.
[
https://issues.apache.org/jira/browse/HBASE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161336#comment-13161336
]
Jonathan Hsieh commented on HBASE-4931:
---
This should give a better actionable error message.
{code}
11/12/01 17:05:19 WARN client.HConnectionManager$HConnectionImplementation:
Encountered problems when prefetch META table:
org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for
table: splittable, row=splittable,,99
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:136)
at
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:95)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:649)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:703)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:594)
{code}
> CopyTable instructions are of date in book and usage in source.
> ---
>
> Key: HBASE-4931
> URL: https://issues.apache.org/jira/browse/HBASE-4931
> Project: HBase
> Issue Type: Bug
> Components: util
>Affects Versions: 0.90.4, 0.92.0
>Reporter: Jonathan Hsieh
>
> The book and the usage instructions refer to ReplicationRegionInterface and
> ReplicationRegionServer which are no longer present in the 0.90+ versions.
> {code}
> $ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
> --rs.class=org.apache.hadoop.hbase.ipc.ReplicationRegionInterface
> --rs.impl=org.apache.hadoop.hbase.regionserver.replication.ReplicationRegionServer
> --starttime=1265875194289 --endtime=1265878794289
> --peer.adr=server1,server2,server3:2181:/hbase TestTable
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4931) CopyTable instructions are of date in book and usage in source.
[
https://issues.apache.org/jira/browse/HBASE-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161335#comment-13161335
]
Jonathan Hsieh commented on HBASE-4931:
---
Other things:
* Docs should say this is a push operation.
* Run time warning if bad zk quorum peer is specified
* Run time warning if bad zk node is specified
> CopyTable instructions are of date in book and usage in source.
> ---
>
> Key: HBASE-4931
> URL: https://issues.apache.org/jira/browse/HBASE-4931
> Project: HBase
> Issue Type: Bug
> Components: util
>Affects Versions: 0.90.4, 0.92.0
>Reporter: Jonathan Hsieh
>
> The book and the usage instructions refer to ReplicationRegionInterface and
> ReplicationRegionServer which are no longer present in the 0.90+ versions.
> {code}
> $ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
> --rs.class=org.apache.hadoop.hbase.ipc.ReplicationRegionInterface
> --rs.impl=org.apache.hadoop.hbase.regionserver.replication.ReplicationRegionServer
> --starttime=1265875194289 --endtime=1265878794289
> --peer.adr=server1,server2,server3:2181:/hbase TestTable
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[
https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161317#comment-13161317
]
Hadoop QA commented on HBASE-4415:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505818/HBASE-4415-9.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 javadoc. The javadoc tool appears to have generated -160 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 71 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestAdmin
org.apache.hadoop.hbase.client.TestInstantSchemaChange
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/420//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/420//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/420//console
This message is automatically generated.
> Add configuration script for setup HBase (hbase-setup-conf.sh)
> --
>
> Key: HBASE-4415
> URL: https://issues.apache.org/jira/browse/HBASE-4415
> Project: HBase
> Issue Type: New Feature
> Components: scripts
>Affects Versions: 0.90.4, 0.92.0
> Environment: Java 6, Linux
>Reporter: Eric Yang
>Assignee: Eric Yang
> Fix For: 0.92.1
>
> Attachments: HBASE-4415-1.patch, HBASE-4415-2.patch,
> HBASE-4415-3.patch, HBASE-4415-4.patch, HBASE-4415-5.patch,
> HBASE-4415-6.patch, HBASE-4415-7.patch, HBASE-4415-8.patch,
> HBASE-4415-9.patch, HBASE-4415.patch
>
>
> The goal of this jura is to provide a installation script for configuring
> HBase environment and configuration. By using the same pattern of
> *-setup-conf.sh for all Hadoop related projects. For HBase, the usage of the
> script looks like this:
> {noformat}
> usage: ./hbase-setup-conf.sh
> Optional parameters:
> --hadoop-conf=/etc/hadoopSet Hadoop configuration directory
> location
> --hadoop-home=/usr Set Hadoop directory location
> --hadoop-namenode=localhost Set Hadoop namenode hostname
> --hadoop-replication=3 Set HDFS replication
> --hbase-home=/usrSet HBase directory location
> --hbase-conf=/etc/hbase Set HBase configuration
> directory location
> --hbase-log=/var/log/hbase Set HBase log directory location
> --hbase-pid=/var/run/hbase Set HBase pid directory location
> --hbase-user=hbase Set HBase user
> --java-home=/usr/java/defaultSet JAVA_HOME directory location
> --kerberos-realm=KERBEROS.EXAMPLE.COMSet Kerberos realm
> --kerberos-principal-id=_HOSTSet Kerberos principal ID
> --keytab-dir=/etc/security/keytabs Set keytab directory
> --regionservers=localhostSet regionservers hostnames
> --zookeeper-home=/usrSet ZooKeeper directory location
> --zookeeper-quorum=localhost Set ZooKeeper Quorum
> --zookeeper-snapshot=/var/lib/zookeeper Set ZooKeeper snapshot location
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4918) HTablePool Constructor may cause unintended behavior
[
https://issues.apache.org/jira/browse/HBASE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161310#comment-13161310
]
Hudson commented on HBASE-4918:
---
Integrated in HBase-0.92 #167 (See
[https://builds.apache.org/job/HBase-0.92/167/])
HBASE-4918 HTablePool Constructor may cause unintended behavior
HBASE-4918 HTablePool Constructor may cause unintended behavior
stack :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
> HTablePool Constructor may cause unintended behavior
>
>
> Key: HBASE-4918
> URL: https://issues.apache.org/jira/browse/HBASE-4918
> Project: HBase
> Issue Type: Bug
> Components: client
> Environment: r1125533
>Reporter: Kitora, Naoki
> Fix For: 0.92.0
>
> Attachments: HTablePool.java.patch
>
>
> {code:title=HTablePool.java}
> 96 public HTablePool(final Configuration config, final int maxSize,
> 97 final HTableInterfaceFactory tableFactory) {
> 98 this(config, maxSize, null, PoolType.Reusable);
> 99 }
> {code}
> I think that 3rd argument in line 98 should be "tableFactory".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161307#comment-13161307 ] Jean-Daniel Cryans commented on HBASE-4930: --- Sounds good, can you post a screen shot of the result? > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4931) CopyTable instructions are of date in book and usage in source.
CopyTable instructions are of date in book and usage in source.
---
Key: HBASE-4931
URL: https://issues.apache.org/jira/browse/HBASE-4931
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 0.90.4, 0.92.0
Reporter: Jonathan Hsieh
The book and the usage instructions refer to ReplicationRegionInterface and
ReplicationRegionServer which are no longer present in the 0.90+ versions.
{code}
$ bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable
--rs.class=org.apache.hadoop.hbase.ipc.ReplicationRegionInterface
--rs.impl=org.apache.hadoop.hbase.regionserver.replication.ReplicationRegionServer
--starttime=1265875194289 --endtime=1265878794289
--peer.adr=server1,server2,server3:2181:/hbase TestTable
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4927) CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the last region when the endkey is empty
[ https://issues.apache.org/jira/browse/HBASE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161299#comment-13161299 ] Jimmy Xiang commented on HBASE-4927: SplitParentFirstComparator is used to sort split parents so that parent is before its daughters. Suppose parent P split into F1 and F2, and F1 is split into D1 and D2, F2 is split into E1 and E2. Now we have split parents: P, F1 and F2. The expected order should be P, F1, and F2 so that CatalogJanior can clean up P before F1 (HBASE-4238). If The endkey of P is empty, due to this bug, the order will be F1, P and F2. So F1 will be removed before P. That's not what we want, right? > CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the > last region when the endkey is empty > --- > > Key: HBASE-4927 > URL: https://issues.apache.org/jira/browse/HBASE-4927 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > > When reviewing HBASE-4238 backporting, Jon found this issue. > What happens if the split points are (empty end key is the last key, empty > start key is the first key) > Parent [A,) > L daughter [A,B), > R daughter [B,) > When sorted, we gets to end key comparision which results in this incorrector > order: > [A,B), [A,), [B,) > we wanted: > [A,), [A,B), [B,) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[
https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161285#comment-13161285
]
Hadoop QA commented on HBASE-4415:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505810/HBASE-4415-8.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 javadoc. The javadoc tool appears to have generated -160 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 71 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestAdmin
org.apache.hadoop.hbase.client.TestInstantSchemaChange
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/419//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/419//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/419//console
This message is automatically generated.
> Add configuration script for setup HBase (hbase-setup-conf.sh)
> --
>
> Key: HBASE-4415
> URL: https://issues.apache.org/jira/browse/HBASE-4415
> Project: HBase
> Issue Type: New Feature
> Components: scripts
>Affects Versions: 0.90.4, 0.92.0
> Environment: Java 6, Linux
>Reporter: Eric Yang
>Assignee: Eric Yang
> Fix For: 0.92.1
>
> Attachments: HBASE-4415-1.patch, HBASE-4415-2.patch,
> HBASE-4415-3.patch, HBASE-4415-4.patch, HBASE-4415-5.patch,
> HBASE-4415-6.patch, HBASE-4415-7.patch, HBASE-4415-8.patch,
> HBASE-4415-9.patch, HBASE-4415.patch
>
>
> The goal of this jura is to provide a installation script for configuring
> HBase environment and configuration. By using the same pattern of
> *-setup-conf.sh for all Hadoop related projects. For HBase, the usage of the
> script looks like this:
> {noformat}
> usage: ./hbase-setup-conf.sh
> Optional parameters:
> --hadoop-conf=/etc/hadoopSet Hadoop configuration directory
> location
> --hadoop-home=/usr Set Hadoop directory location
> --hadoop-namenode=localhost Set Hadoop namenode hostname
> --hadoop-replication=3 Set HDFS replication
> --hbase-home=/usrSet HBase directory location
> --hbase-conf=/etc/hbase Set HBase configuration
> directory location
> --hbase-log=/var/log/hbase Set HBase log directory location
> --hbase-pid=/var/run/hbase Set HBase pid directory location
> --hbase-user=hbase Set HBase user
> --java-home=/usr/java/defaultSet JAVA_HOME directory location
> --kerberos-realm=KERBEROS.EXAMPLE.COMSet Kerberos realm
> --kerberos-principal-id=_HOSTSet Kerberos principal ID
> --keytab-dir=/etc/security/keytabs Set keytab directory
> --regionservers=localhostSet regionservers hostnames
> --zookeeper-home=/usrSet ZooKeeper directory location
> --zookeeper-quorum=localhost Set ZooKeeper Quorum
> --zookeeper-snapshot=/var/lib/zookeeper Set ZooKeeper snapshot location
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4930: - Component/s: documentation > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4927) CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the last region when the endkey is empty
[ https://issues.apache.org/jira/browse/HBASE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161280#comment-13161280 ] stack commented on HBASE-4927: -- I don't think we sort that way (IIRC, there is hacky stuff to make sure we sort properly) > CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the > last region when the endkey is empty > --- > > Key: HBASE-4927 > URL: https://issues.apache.org/jira/browse/HBASE-4927 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.92.0, 0.94.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > > When reviewing HBASE-4238 backporting, Jon found this issue. > What happens if the split points are (empty end key is the last key, empty > start key is the first key) > Parent [A,) > L daughter [A,B), > R daughter [B,) > When sorted, we gets to end key comparision which results in this incorrector > order: > [A,B), [A,), [B,) > we wanted: > [A,), [A,B), [B,) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161269#comment-13161269 ] Hadoop QA commented on HBASE-4930: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505822/index_HBASE_4930.xml.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 javadoc. The javadoc tool appears to have generated -160 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.master.TestRollingRestart org.apache.hadoop.hbase.master.TestRestartCluster org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler org.apache.hadoop.hbase.zookeeper.TestZKLeaderManager org.apache.hadoop.hbase.master.TestDistributedLogSplitting org.apache.hadoop.hbase.master.TestHMasterRPCException org.apache.hadoop.hbase.regionserver.TestKeepDeletes org.apache.hadoop.hbase.mapreduce.TestTimeRangeMapRed org.apache.hadoop.hbase.zookeeper.TestZooKeeperNodeTracker org.apache.hadoop.hbase.master.TestMaster org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFilesSplitRecovery org.apache.hadoop.hbase.master.TestMasterRestartAfterDisablingTable org.apache.hadoop.hbase.TestDrainingServer org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan org.apache.hadoop.hbase.master.TestZKBasedOpenCloseRegion org.apache.hadoop.hbase.TestFullLogReconstruction org.apache.hadoop.hbase.avro.TestAvroServer org.apache.hadoop.hbase.mapreduce.TestLoadIncrementalHFiles org.apache.hadoop.hbase.master.TestMasterFailover org.apache.hadoop.hbase.mapreduce.TestImportTsv org.apache.hadoop.hbase.zookeeper.TestZooKeeperACL org.apache.hadoop.hbase.master.TestMasterTransitions org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat org.apache.hadoop.hbase.master.TestSplitLogManager org.apache.hadoop.hbase.mapreduce.TestTableMapReduce org.apache.hadoop.hbase.master.TestOpenedRegionHandler Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/421//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/421//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/421//console This message is automatically generated. > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4930: - Status: Patch Available (was: Open) > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4930: - Description: Reformat the HBase home page. It's not a radical redesign but breaks the information that is there into clearer sections: * Welcome to HBase! (it's always good to be polite to the reader) * When Should I Use HBase? * Features * How Can I Get More Information? * News I also updated the feature-list in this page (added some things, clarified a few things, removed one or two things) Note: I just overhauled the FAQ in the book today as well. was: Reformat the HBase home page. It's not a radical redesign but breaks the information that is there into clearer sections: * Welcome to HBase! (it's always good to be polite to the reader) * When Should I Use HBase? * Features * How Can I Get More Information? * News I also updated the feature-list. > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list in this page (added some things, clarified a > few things, removed one or two things) > Note: I just overhauled the FAQ in the book today as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4930) Reformat HBase home page
Reformat HBase home page Key: HBASE-4930 URL: https://issues.apache.org/jira/browse/HBASE-4930 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: index_HBASE_4930.xml.patch Reformat the HBase home page. It's not a radical redesign but breaks the information that is there into clearer sections: * Welcome to HBase! (it's always good to be polite to the reader) * When Should I Use HBase? * Features * How Can I Get More Information? * News I also updated the feature-list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4930) Reformat HBase home page
[ https://issues.apache.org/jira/browse/HBASE-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4930: - Attachment: index_HBASE_4930.xml.patch > Reformat HBase home page > > > Key: HBASE-4930 > URL: https://issues.apache.org/jira/browse/HBASE-4930 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: index_HBASE_4930.xml.patch > > > Reformat the HBase home page. It's not a radical redesign but breaks the > information that is there into clearer sections: > * Welcome to HBase! (it's always good to be polite to the reader) > * When Should I Use HBase? > * Features > * How Can I Get More Information? > * News > I also updated the feature-list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4929) Two servlet-api jars in 0.92 tarball -- fix
Two servlet-api jars in 0.92 tarball -- fix --- Key: HBASE-4929 URL: https://issues.apache.org/jira/browse/HBASE-4929 Project: HBase Issue Type: Bug Reporter: stack Fix For: 0.92.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4929) Two servlet-api jars in 0.92 tarball -- fix
[ https://issues.apache.org/jira/browse/HBASE-4929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161246#comment-13161246 ] stack commented on HBASE-4929: -- Via Kan. > Two servlet-api jars in 0.92 tarball -- fix > --- > > Key: HBASE-4929 > URL: https://issues.apache.org/jira/browse/HBASE-4929 > Project: HBase > Issue Type: Bug >Reporter: stack > Fix For: 0.92.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4918) HTablePool Constructor may cause unintended behavior
[
https://issues.apache.org/jira/browse/HBASE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161231#comment-13161231
]
Hudson commented on HBASE-4918:
---
Integrated in HBase-TRUNK #2506 (See
[https://builds.apache.org/job/HBase-TRUNK/2506/])
HBASE-4918 HTablePool Constructor may cause unintended behavior
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
> HTablePool Constructor may cause unintended behavior
>
>
> Key: HBASE-4918
> URL: https://issues.apache.org/jira/browse/HBASE-4918
> Project: HBase
> Issue Type: Bug
> Components: client
> Environment: r1125533
>Reporter: Kitora, Naoki
> Fix For: 0.92.0
>
> Attachments: HTablePool.java.patch
>
>
> {code:title=HTablePool.java}
> 96 public HTablePool(final Configuration config, final int maxSize,
> 97 final HTableInterfaceFactory tableFactory) {
> 98 this(config, maxSize, null, PoolType.Reusable);
> 99 }
> {code}
> I think that 3rd argument in line 98 should be "tableFactory".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[
https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated HBASE-4415:
---
Attachment: HBASE-4415-9.patch
now that HDFS-2246 (short circuit read) has been committed to hadoop, we need
to support enabling of the short circuit read for the client. Attaching a new
patch that also adds the support to set short circuit read configs.
> Add configuration script for setup HBase (hbase-setup-conf.sh)
> --
>
> Key: HBASE-4415
> URL: https://issues.apache.org/jira/browse/HBASE-4415
> Project: HBase
> Issue Type: New Feature
> Components: scripts
>Affects Versions: 0.90.4, 0.92.0
> Environment: Java 6, Linux
>Reporter: Eric Yang
>Assignee: Eric Yang
> Fix For: 0.92.1
>
> Attachments: HBASE-4415-1.patch, HBASE-4415-2.patch,
> HBASE-4415-3.patch, HBASE-4415-4.patch, HBASE-4415-5.patch,
> HBASE-4415-6.patch, HBASE-4415-7.patch, HBASE-4415-8.patch,
> HBASE-4415-9.patch, HBASE-4415.patch
>
>
> The goal of this jura is to provide a installation script for configuring
> HBase environment and configuration. By using the same pattern of
> *-setup-conf.sh for all Hadoop related projects. For HBase, the usage of the
> script looks like this:
> {noformat}
> usage: ./hbase-setup-conf.sh
> Optional parameters:
> --hadoop-conf=/etc/hadoopSet Hadoop configuration directory
> location
> --hadoop-home=/usr Set Hadoop directory location
> --hadoop-namenode=localhost Set Hadoop namenode hostname
> --hadoop-replication=3 Set HDFS replication
> --hbase-home=/usrSet HBase directory location
> --hbase-conf=/etc/hbase Set HBase configuration
> directory location
> --hbase-log=/var/log/hbase Set HBase log directory location
> --hbase-pid=/var/run/hbase Set HBase pid directory location
> --hbase-user=hbase Set HBase user
> --java-home=/usr/java/defaultSet JAVA_HOME directory location
> --kerberos-realm=KERBEROS.EXAMPLE.COMSet Kerberos realm
> --kerberos-principal-id=_HOSTSet Kerberos principal ID
> --keytab-dir=/etc/security/keytabs Set keytab directory
> --regionservers=localhostSet regionservers hostnames
> --zookeeper-home=/usrSet ZooKeeper directory location
> --zookeeper-quorum=localhost Set ZooKeeper Quorum
> --zookeeper-snapshot=/var/lib/zookeeper Set ZooKeeper snapshot location
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[ https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-4415: -- Comment: was deleted (was: -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505810/HBASE-4415-8.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 javadoc. The javadoc tool appears to have generated -160 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.master.TestRollingRestart org.apache.hadoop.hbase.util.TestRegionSplitter org.apache.hadoop.hbase.io.hfile.TestLruBlockCache org.apache.hadoop.hbase.client.TestMultiParallel org.apache.hadoop.hbase.master.TestRestartCluster org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler org.apache.hadoop.hbase.client.TestInstantSchemaChange org.apache.hadoop.hbase.regionserver.TestStore org.apache.hadoop.hbase.regionserver.wal.TestHLogBench org.apache.hadoop.hbase.rest.TestGzipFilter org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD org.apache.hadoop.hbase.master.TestLogsCleaner org.apache.hadoop.hbase.regionserver.TestAtomicOperation org.apache.hadoop.hbase.rest.TestScannersWithFilters org.apache.hadoop.hbase.TestInfoServers org.apache.hadoop.hbase.regionserver.TestParallelPut org.apache.hadoop.hbase.coprocessor.TestClassLoading org.apache.hadoop.hbase.client.TestAdmin org.apache.hadoop.hbase.regionserver.wal.TestLogRolling org.apache.hadoop.hbase.filter.TestColumnRangeFilter org.apache.hadoop.hbase.mapred.TestTableInputFormat org.apache.hadoop.hbase.client.TestHCM org.apache.hadoop.hbase.regionserver.TestStoreFileBlockCacheSummary org.apache.hadoop.hbase.util.hbck.TestOfflineMetaRebuildHole org.apache.hadoop.hbase.coprocessor.TestMasterObserver org.apache.hadoop.hbase.rest.TestStatusResource org.apache.hadoop.hbase.TestRegionRebalancing org.apache.hadoop.hbase.regionserver.TestMultiColumnScanner org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort org.apache.hadoop.hbase.regionserver.TestSeekOptimizations org.apache.hadoop.hbase.rest.TestVersionResource org.apache.hadoop.hbase.client.TestScannerTimeout org.apache.hadoop.hbase.client.TestFromClientSide org.apache.hadoop.hbase.regionserver.TestFSErrorsExposed org.apache.hadoop.hbase.coprocessor.TestAggregateProtocol org.apache.hadoop.hbase.regionserver.TestSplitTransaction org.apache.hadoop.hbase.rest.TestRowResource org.apache.hadoop.hbase.rest.TestScannerResource org.apache.hadoop.hbase.ipc.TestDelayedRpc org.apache.hadoop.hbase.rest.client.TestRemoteAdmin org.apache.hadoop.hbase.util.TestFSUtils org.apache.hadoop.hbase.zookeeper.TestZKLeaderManager org.apache.hadoop.hbase.master.TestDistributedLogSplitting org.apache.hadoop.hbase.rest.TestTableResource org.apache.hadoop.hbase.regionserver.wal.TestWALReplay org.apache.hadoop.hbase.master.TestHMasterRPCException org.apache.hadoop.hbase.util.TestIdLock org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster org.apache.hadoop.hbase.regionserver.TestMemStore org.apache.hadoop.hbase.rest.TestTransform org.apache.hadoop.hbase.coprocessor.TestCoprocessorEndpoint org.apache.hadoop.hbase.client.TestInstantSchemaChangeSplit org.apache.hadoop.hbase.regionserver.TestHRegion org.apache.hadoop.hbase.regionserver.TestReadWriteConsistencyControl org.apache.hadoop.hb
[jira] [Commented] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[ https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161195#comment-13161195 ] Hadoop QA commented on HBASE-4415: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505810/HBASE-4415-8.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 javadoc. The javadoc tool appears to have generated -160 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.master.TestRollingRestart org.apache.hadoop.hbase.util.TestRegionSplitter org.apache.hadoop.hbase.io.hfile.TestLruBlockCache org.apache.hadoop.hbase.client.TestMultiParallel org.apache.hadoop.hbase.master.TestRestartCluster org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler org.apache.hadoop.hbase.client.TestInstantSchemaChange org.apache.hadoop.hbase.regionserver.TestStore org.apache.hadoop.hbase.regionserver.wal.TestHLogBench org.apache.hadoop.hbase.rest.TestGzipFilter org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD org.apache.hadoop.hbase.master.TestLogsCleaner org.apache.hadoop.hbase.regionserver.TestAtomicOperation org.apache.hadoop.hbase.rest.TestScannersWithFilters org.apache.hadoop.hbase.TestInfoServers org.apache.hadoop.hbase.regionserver.TestParallelPut org.apache.hadoop.hbase.coprocessor.TestClassLoading org.apache.hadoop.hbase.client.TestAdmin org.apache.hadoop.hbase.regionserver.wal.TestLogRolling org.apache.hadoop.hbase.filter.TestColumnRangeFilter org.apache.hadoop.hbase.mapred.TestTableInputFormat org.apache.hadoop.hbase.client.TestHCM org.apache.hadoop.hbase.regionserver.TestStoreFileBlockCacheSummary org.apache.hadoop.hbase.util.hbck.TestOfflineMetaRebuildHole org.apache.hadoop.hbase.coprocessor.TestMasterObserver org.apache.hadoop.hbase.rest.TestStatusResource org.apache.hadoop.hbase.TestRegionRebalancing org.apache.hadoop.hbase.regionserver.TestMultiColumnScanner org.apache.hadoop.hbase.regionserver.wal.TestLogRollAbort org.apache.hadoop.hbase.regionserver.TestSeekOptimizations org.apache.hadoop.hbase.rest.TestVersionResource org.apache.hadoop.hbase.client.TestScannerTimeout org.apache.hadoop.hbase.client.TestFromClientSide org.apache.hadoop.hbase.regionserver.TestFSErrorsExposed org.apache.hadoop.hbase.coprocessor.TestAggregateProtocol org.apache.hadoop.hbase.regionserver.TestSplitTransaction org.apache.hadoop.hbase.rest.TestRowResource org.apache.hadoop.hbase.rest.TestScannerResource org.apache.hadoop.hbase.ipc.TestDelayedRpc org.apache.hadoop.hbase.rest.client.TestRemoteAdmin org.apache.hadoop.hbase.util.TestFSUtils org.apache.hadoop.hbase.zookeeper.TestZKLeaderManager org.apache.hadoop.hbase.master.TestDistributedLogSplitting org.apache.hadoop.hbase.rest.TestTableResource org.apache.hadoop.hbase.regionserver.wal.TestWALReplay org.apache.hadoop.hbase.master.TestHMasterRPCException org.apache.hadoop.hbase.util.TestIdLock org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster org.apache.hadoop.hbase.regionserver.TestMemStore org.apache.hadoop.hbase.rest.TestTransform org.apache.hadoop.hbase.coprocessor.TestCoprocessorEndpoint org.apache.hadoop.hbase.client.TestInstantSchemaChangeSplit org.apache.hadoop.hbase.regionserver.TestHRegion org.apache.hadoop.hbase.regionserver.TestReadWriteConsistencyControl
[jira] [Updated] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[
https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated HBASE-4415:
--
Attachment: HBASE-4415-8.patch
> Add configuration script for setup HBase (hbase-setup-conf.sh)
> --
>
> Key: HBASE-4415
> URL: https://issues.apache.org/jira/browse/HBASE-4415
> Project: HBase
> Issue Type: New Feature
> Components: scripts
>Affects Versions: 0.90.4, 0.92.0
> Environment: Java 6, Linux
>Reporter: Eric Yang
>Assignee: Eric Yang
> Fix For: 0.92.1
>
> Attachments: HBASE-4415-1.patch, HBASE-4415-2.patch,
> HBASE-4415-3.patch, HBASE-4415-4.patch, HBASE-4415-5.patch,
> HBASE-4415-6.patch, HBASE-4415-7.patch, HBASE-4415-8.patch, HBASE-4415.patch
>
>
> The goal of this jura is to provide a installation script for configuring
> HBase environment and configuration. By using the same pattern of
> *-setup-conf.sh for all Hadoop related projects. For HBase, the usage of the
> script looks like this:
> {noformat}
> usage: ./hbase-setup-conf.sh
> Optional parameters:
> --hadoop-conf=/etc/hadoopSet Hadoop configuration directory
> location
> --hadoop-home=/usr Set Hadoop directory location
> --hadoop-namenode=localhost Set Hadoop namenode hostname
> --hadoop-replication=3 Set HDFS replication
> --hbase-home=/usrSet HBase directory location
> --hbase-conf=/etc/hbase Set HBase configuration
> directory location
> --hbase-log=/var/log/hbase Set HBase log directory location
> --hbase-pid=/var/run/hbase Set HBase pid directory location
> --hbase-user=hbase Set HBase user
> --java-home=/usr/java/defaultSet JAVA_HOME directory location
> --kerberos-realm=KERBEROS.EXAMPLE.COMSet Kerberos realm
> --kerberos-principal-id=_HOSTSet Kerberos principal ID
> --keytab-dir=/etc/security/keytabs Set keytab directory
> --regionservers=localhostSet regionservers hostnames
> --zookeeper-home=/usrSet ZooKeeper directory location
> --zookeeper-quorum=localhost Set ZooKeeper Quorum
> --zookeeper-snapshot=/var/lib/zookeeper Set ZooKeeper snapshot location
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4415) Add configuration script for setup HBase (hbase-setup-conf.sh)
[
https://issues.apache.org/jira/browse/HBASE-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giridharan Kesavan updated HBASE-4415:
--
Attachment: HBASE-4415-7.patch
updating patch after HBASE-4894 commit.
> Add configuration script for setup HBase (hbase-setup-conf.sh)
> --
>
> Key: HBASE-4415
> URL: https://issues.apache.org/jira/browse/HBASE-4415
> Project: HBase
> Issue Type: New Feature
> Components: scripts
>Affects Versions: 0.90.4, 0.92.0
> Environment: Java 6, Linux
>Reporter: Eric Yang
>Assignee: Eric Yang
> Fix For: 0.92.1
>
> Attachments: HBASE-4415-1.patch, HBASE-4415-2.patch,
> HBASE-4415-3.patch, HBASE-4415-4.patch, HBASE-4415-5.patch,
> HBASE-4415-6.patch, HBASE-4415-7.patch, HBASE-4415.patch
>
>
> The goal of this jura is to provide a installation script for configuring
> HBase environment and configuration. By using the same pattern of
> *-setup-conf.sh for all Hadoop related projects. For HBase, the usage of the
> script looks like this:
> {noformat}
> usage: ./hbase-setup-conf.sh
> Optional parameters:
> --hadoop-conf=/etc/hadoopSet Hadoop configuration directory
> location
> --hadoop-home=/usr Set Hadoop directory location
> --hadoop-namenode=localhost Set Hadoop namenode hostname
> --hadoop-replication=3 Set HDFS replication
> --hbase-home=/usrSet HBase directory location
> --hbase-conf=/etc/hbase Set HBase configuration
> directory location
> --hbase-log=/var/log/hbase Set HBase log directory location
> --hbase-pid=/var/run/hbase Set HBase pid directory location
> --hbase-user=hbase Set HBase user
> --java-home=/usr/java/defaultSet JAVA_HOME directory location
> --kerberos-realm=KERBEROS.EXAMPLE.COMSet Kerberos realm
> --kerberos-principal-id=_HOSTSet Kerberos principal ID
> --keytab-dir=/etc/security/keytabs Set keytab directory
> --regionservers=localhostSet regionservers hostnames
> --zookeeper-home=/usrSet ZooKeeper directory location
> --zookeeper-quorum=localhost Set ZooKeeper Quorum
> --zookeeper-snapshot=/var/lib/zookeeper Set ZooKeeper snapshot location
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4928) [book] overhaul FAQ
[ https://issues.apache.org/jira/browse/HBASE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4928: - Resolution: Fixed Status: Resolved (was: Patch Available) > [book] overhaul FAQ > --- > > Key: HBASE-4928 > URL: https://issues.apache.org/jira/browse/HBASE-4928 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: book_HBASE_4928.xml.patch > > > Overhauled the FAQ in the book and aligned the groups of questions to the way > the book is aligned (e.g., configuration, schema design, performance, etc.) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4928) [book] overhaul FAQ
[ https://issues.apache.org/jira/browse/HBASE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4928: - Status: Patch Available (was: Open) > [book] overhaul FAQ > --- > > Key: HBASE-4928 > URL: https://issues.apache.org/jira/browse/HBASE-4928 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: book_HBASE_4928.xml.patch > > > Overhauled the FAQ in the book and aligned the groups of questions to the way > the book is aligned (e.g., configuration, schema design, performance, etc.) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4928) [book] overhaul FAQ
[ https://issues.apache.org/jira/browse/HBASE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4928: - Attachment: book_HBASE_4928.xml.patch > [book] overhaul FAQ > --- > > Key: HBASE-4928 > URL: https://issues.apache.org/jira/browse/HBASE-4928 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: book_HBASE_4928.xml.patch > > > Overhauled the FAQ in the book and aligned the groups of questions to the way > the book is aligned (e.g., configuration, schema design, performance, etc.) > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4928) [book] overhaul FAQ
[book] overhaul FAQ --- Key: HBASE-4928 URL: https://issues.apache.org/jira/browse/HBASE-4928 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: book_HBASE_4928.xml.patch Overhauled the FAQ in the book and aligned the groups of questions to the way the book is aligned (e.g., configuration, schema design, performance, etc.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4440) add an option to presplit table to PerformanceEvaluation
[ https://issues.apache.org/jira/browse/HBASE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sujee Maniyam updated HBASE-4440: - Attachment: PerformanceEvaluation_HBASE_4440_2.patch thanks for the comments. I have attached a revised patch. removed sleep-wait after deleting table. I had some issues with 0.90.1, works fine with 0.90.4 > add an option to presplit table to PerformanceEvaluation > > > Key: HBASE-4440 > URL: https://issues.apache.org/jira/browse/HBASE-4440 > Project: HBase > Issue Type: Improvement > Components: util >Reporter: Sujee Maniyam >Priority: Minor > Labels: benchmark > Attachments: PerformanceEvaluation.java, > PerformanceEvaluation_HBASE_4440.patch, > PerformanceEvaluation_HBASE_4440_2.patch > > > PerformanceEvaluation a quick way to 'benchmark' a HBase cluster. The > current 'write*' operations do not pre-split the table. Pre splitting the > table will really boost the insert performance. > It would be nice to have an option to enable pre-splitting table before the > inserts begin. > it would look something like: > (a) hbase ...PerformanceEvaluation --presplit=10 > (b) hbase ...PerformanceEvaluation --presplit > (b) will try to presplit the table on some default value (say number of > region servers) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4927) CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the last region when the endkey is empty
CatalogJanior:SplitParentFirstComparator doesn't sort as expected, for the last region when the endkey is empty --- Key: HBASE-4927 URL: https://issues.apache.org/jira/browse/HBASE-4927 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.92.0, 0.94.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor When reviewing HBASE-4238 backporting, Jon found this issue. What happens if the split points are (empty end key is the last key, empty start key is the first key) Parent [A,) L daughter [A,B), R daughter [B,) When sorted, we gets to end key comparision which results in this incorrector order: [A,B), [A,), [B,) we wanted: [A,), [A,B), [B,) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4926) DebugFilter; counts how many KVs skipped before result found, counts storefiles we tripped over
[ https://issues.apache.org/jira/browse/HBASE-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161086#comment-13161086 ] Jean-Daniel Cryans commented on HBASE-4926: --- It could also be used in the shell to do stuff like debug_get, debug_scan, and then it would be easy to debug performance of requests. > DebugFilter; counts how many KVs skipped before result found, counts > storefiles we tripped over > --- > > Key: HBASE-4926 > URL: https://issues.apache.org/jira/browse/HBASE-4926 > Project: HBase > Issue Type: Task >Reporter: stack > > I'm not sure this possible but chatting w/ J-D after he finished helping a > crew who had a slow scan, we need ways to help folks figure out why stuff is > slow on the server side. In this case, the user had a region that had gigs > of deletes in it that had to be skipped before the scanner got to a value to > return so scans looked slow though working 'correctly'. If the user could > enable a DebugFilter than did counts of what Scans were skipping and size of > data skipped among other things, it might help w/ the situation above -- and > perhaps with others (What else could we count in a filter?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4926) DebugFilter; counts how many KVs skipped before result found, counts storefiles we tripped over
DebugFilter; counts how many KVs skipped before result found, counts storefiles we tripped over --- Key: HBASE-4926 URL: https://issues.apache.org/jira/browse/HBASE-4926 Project: HBase Issue Type: Task Reporter: stack I'm not sure this possible but chatting w/ J-D after he finished helping a crew who had a slow scan, we need ways to help folks figure out why stuff is slow on the server side. In this case, the user had a region that had gigs of deletes in it that had to be skipped before the scanner got to a value to return so scans looked slow though working 'correctly'. If the user could enable a DebugFilter than did counts of what Scans were skipping and size of data skipped among other things, it might help w/ the situation above -- and perhaps with others (What else could we count in a filter?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4918) HTablePool Constructor may cause unintended behavior
[
https://issues.apache.org/jira/browse/HBASE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4918:
-
Resolution: Fixed
Fix Version/s: 0.92.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed branch and trunk. Thanks for patch Naoki.
> HTablePool Constructor may cause unintended behavior
>
>
> Key: HBASE-4918
> URL: https://issues.apache.org/jira/browse/HBASE-4918
> Project: HBase
> Issue Type: Bug
> Components: client
> Environment: r1125533
>Reporter: Kitora, Naoki
> Fix For: 0.92.0
>
> Attachments: HTablePool.java.patch
>
>
> {code:title=HTablePool.java}
> 96 public HTablePool(final Configuration config, final int maxSize,
> 97 final HTableInterfaceFactory tableFactory) {
> 98 this(config, maxSize, null, PoolType.Reusable);
> 99 }
> {code}
> I think that 3rd argument in line 98 should be "tableFactory".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3437) Allow Explicit Splits from the Shell
[ https://issues.apache.org/jira/browse/HBASE-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3437: - Fix Version/s: (was: 0.90.2) Updating fix version after Ben's digging > Allow Explicit Splits from the Shell > > > Key: HBASE-3437 > URL: https://issues.apache.org/jira/browse/HBASE-3437 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Nicolas Spiegelberg >Assignee: Nicolas Spiegelberg >Priority: Trivial > Fix For: 0.92.0 > > Attachments: HBASE-3437.patch > > > There is no way currently to issue explicit splits from the shell. You can > only accomplish it through HBaseAdmin currently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3437) Allow Explicit Splits from the Shell
[ https://issues.apache.org/jira/browse/HBASE-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160952#comment-13160952 ] Ben West commented on HBASE-3437: - I'm not seeing this in 0.90.2-0.90.4 but I do see it in trunk. Is this correct? If so, could we update the fix versions on this ticket? I'm looking at split.rb which should have the additional parameter. You can see it's not in: * [0.90.2|http://svn.apache.org/viewvc/hbase/tags/0.90.2/src/main/ruby/shell/commands/split.rb?view=markup] * [0.90.3|http://svn.apache.org/viewvc/hbase/tags/0.90.3/src/main/ruby/shell/commands/split.rb?view=markup] * [0.90.4|http://svn.apache.org/viewvc/hbase/tags/0.90.4/src/main/ruby/shell/commands/split.rb?view=markup] But it is in: * [0.92RC0|http://svn.apache.org/viewvc/hbase/tags/0.92.0rc0/src/main/ruby/shell/commands/split.rb?view=markup] * [trunk|http://svn.apache.org/viewvc/hbase/trunk/src/main/ruby/shell/commands/split.rb?view=markup] > Allow Explicit Splits from the Shell > > > Key: HBASE-3437 > URL: https://issues.apache.org/jira/browse/HBASE-3437 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Nicolas Spiegelberg >Assignee: Nicolas Spiegelberg >Priority: Trivial > Fix For: 0.90.2, 0.92.0 > > Attachments: HBASE-3437.patch > > > There is no way currently to issue explicit splits from the shell. You can > only accomplish it through HBaseAdmin currently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160923#comment-13160923 ] Hadoop QA commented on HBASE-4847: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505769/4847_all.v7.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 12 new or modified tests. -1 javadoc. The javadoc tool appears to have generated -160 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestColumnSeeking org.apache.hadoop.hbase.regionserver.TestCompaction org.apache.hadoop.hbase.regionserver.TestScanner org.apache.hadoop.hbase.executor.TestExecutorService org.apache.hadoop.hbase.regionserver.TestSplitTransaction org.apache.hadoop.hbase.util.TestThreads org.apache.hadoop.hbase.coprocessor.TestCoprocessorInterface org.apache.hadoop.hbase.regionserver.TestMemStore org.apache.hadoop.hbase.regionserver.TestReadWriteConsistencyControl org.apache.hadoop.hbase.regionserver.TestKeepDeletes org.apache.hadoop.hbase.filter.TestDependentColumnFilter org.apache.hadoop.hbase.regionserver.TestResettingCounters org.apache.hadoop.hbase.coprocessor.TestRegionObserverStacking org.apache.hadoop.hbase.regionserver.TestScanWithBloomError org.apache.hadoop.hbase.regionserver.wal.TestWALActionsListener org.apache.hadoop.hbase.regionserver.TestCompactSelection org.apache.hadoop.hbase.filter.TestColumnPrefixFilter org.apache.hadoop.hbase.filter.TestMultipleColumnPrefixFilter org.apache.hadoop.hbase.regionserver.TestMinVersions org.apache.hadoop.hbase.regionserver.TestGetClosestAtOrBefore org.apache.hadoop.hbase.regionserver.TestWideScanner org.apache.hadoop.hbase.regionserver.TestMemStoreLAB org.apache.hadoop.hbase.filter.TestFilter Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/417//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/417//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/417//console This message is automatically generated. > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch, > 4847_pom.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, > 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Status: Patch Available (was: Open) > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch, > 4847_pom.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, > 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Attachment: 4847_all.v7.patch > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch, > 4847_pom.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, > 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Attachment: 4847_all.v7.patch > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_pom.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Status: Open (was: Patch Available) > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_pom.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4847) Activate single jvm for small tests on jenkins
[
https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160917#comment-13160917
]
nkeywal commented on HBASE-4847:
{noformat}unable to create new native thread{noformat}
back to the crazy state. Let's retry.
> Activate single jvm for small tests on jenkins
> --
>
> Key: HBASE-4847
> URL: https://issues.apache.org/jira/browse/HBASE-4847
> Project: HBase
> Issue Type: Improvement
> Components: build, test
>Affects Versions: 0.94.0
> Environment: build
>Reporter: nkeywal
>Assignee: nkeywal
>Priority: Minor
> Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch,
> 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_pom.patch,
> 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch
>
>
> This will not revolutionate performances alone. We will win between 1 to 4
> minutes.
> But we win as well:
> - it's a step for parallelizing the tests
> - new tests are less expensive as they do not create a new jvm: it's a
> continuous win
> - it will allow to push it on dev env while having the same env on dev & on
> build, and 3 minutes are 10% of small + medium tests execution time.
> I will do a few "submit patch" to see if it works well before asking for the
> real commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160915#comment-13160915 ] Hadoop QA commented on HBASE-4847: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505764/4847_all.v7.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 12 new or modified tests. -1 javadoc. The javadoc tool appears to have generated -160 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.master.TestCatalogJanitor org.apache.hadoop.hbase.regionserver.TestColumnSeeking org.apache.hadoop.hbase.regionserver.TestCompaction org.apache.hadoop.hbase.regionserver.TestScanner org.apache.hadoop.hbase.executor.TestExecutorService org.apache.hadoop.hbase.regionserver.TestSplitTransaction org.apache.hadoop.hbase.util.TestThreads org.apache.hadoop.hbase.coprocessor.TestCoprocessorInterface org.apache.hadoop.hbase.regionserver.TestMemStore org.apache.hadoop.hbase.regionserver.TestReadWriteConsistencyControl org.apache.hadoop.hbase.regionserver.TestKeepDeletes org.apache.hadoop.hbase.filter.TestDependentColumnFilter org.apache.hadoop.hbase.coprocessor.TestRegionObserverStacking org.apache.hadoop.hbase.regionserver.TestScanWithBloomError org.apache.hadoop.hbase.regionserver.wal.TestWALActionsListener org.apache.hadoop.hbase.regionserver.TestCompactSelection org.apache.hadoop.hbase.filter.TestColumnPrefixFilter org.apache.hadoop.hbase.filter.TestMultipleColumnPrefixFilter org.apache.hadoop.hbase.regionserver.TestMinVersions org.apache.hadoop.hbase.regionserver.TestGetClosestAtOrBefore org.apache.hadoop.hbase.regionserver.TestWideScanner org.apache.hadoop.hbase.regionserver.TestMemStoreLAB org.apache.hadoop.hbase.filter.TestFilter Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/416//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/416//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/416//console This message is automatically generated. > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_pom.patch, 4847_pom.v2.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Status: Patch Available (was: Open) > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_pom.patch, 4847_pom.v2.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160899#comment-13160899 ] nkeywal commented on HBASE-4847: Well, as with this patch all small tests are executed in a shared jvm, we can see some side effects. However, I ran these test more than 20 times, and it's working in my env. I deactivated parallelism to avoid random results. So it's strange. I went to the debugger for TestMinVersions#testBaseCase, and it seems the only to get this results is using a wrong EnvironmentEdgeManager. But I checked that only the default is used for small tests. The patch v7 add a check & a reset for the EnvironmentEdgeManager, I will see what are the results... > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_pom.patch, 4847_pom.v2.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Status: Open (was: Patch Available) > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_pom.patch, 4847_pom.v2.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-4847) Activate single jvm for small tests on jenkins
[ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4847: --- Attachment: 4847_all.v7.patch > Activate single jvm for small tests on jenkins > -- > > Key: HBASE-4847 > URL: https://issues.apache.org/jira/browse/HBASE-4847 > Project: HBase > Issue Type: Improvement > Components: build, test >Affects Versions: 0.94.0 > Environment: build >Reporter: nkeywal >Assignee: nkeywal >Priority: Minor > Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, > 4847_all.v6.patch, 4847_all.v7.patch, 4847_pom.patch, 4847_pom.v2.patch, > 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch > > > This will not revolutionate performances alone. We will win between 1 to 4 > minutes. > But we win as well: > - it's a step for parallelizing the tests > - new tests are less expensive as they do not create a new jvm: it's a > continuous win > - it will allow to push it on dev env while having the same env on dev & on > build, and 3 minutes are 10% of small + medium tests execution time. > I will do a few "submit patch" to see if it works well before asking for the > real commit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4903) Return a result from RegionObserver.preIncrement()
[ https://issues.apache.org/jira/browse/HBASE-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160807#comment-13160807 ] Hudson commented on HBASE-4903: --- Integrated in HBase-0.92 #166 (See [https://builds.apache.org/job/HBase-0.92/166/]) HBASE-4903 Return a result from RegionObserver.preIncrement (Daniel Gómez Ferro) larsh : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseRegionObserver.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/RegionCoprocessorHost.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/coprocessor/SimpleRegionObserver.java > Return a result from RegionObserver.preIncrement() > -- > > Key: HBASE-4903 > URL: https://issues.apache.org/jira/browse/HBASE-4903 > Project: HBase > Issue Type: Improvement >Reporter: Daniel Gómez Ferro > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-4903-0.92.patch, HBASE-4903.patch, HBASE-4903.patch > > > The only way to return a result from RegionObserver.preIncrement() is to use > Result.readFields() after serializing the correct result. > This can be fixed either returning a Result object from that function or > adding setters to Result. Another option is to modify the parameters and > receive a List as preGet() does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4903) Return a result from RegionObserver.preIncrement()
[ https://issues.apache.org/jira/browse/HBASE-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160759#comment-13160759 ] Hudson commented on HBASE-4903: --- Integrated in HBase-TRUNK #2505 (See [https://builds.apache.org/job/HBase-TRUNK/2505/]) HBASE-4903 Return a result from RegionObserver.preIncrement (Daniel Gómez Ferro) larsh : Files : * /hbase/trunk/CHANGES.txt * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/BaseRegionObserver.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/RegionCoprocessorHost.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/coprocessor/SimpleRegionObserver.java > Return a result from RegionObserver.preIncrement() > -- > > Key: HBASE-4903 > URL: https://issues.apache.org/jira/browse/HBASE-4903 > Project: HBase > Issue Type: Improvement >Reporter: Daniel Gómez Ferro > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-4903-0.92.patch, HBASE-4903.patch, HBASE-4903.patch > > > The only way to return a result from RegionObserver.preIncrement() is to use > Result.readFields() after serializing the correct result. > This can be fixed either returning a Result object from that function or > adding setters to Result. Another option is to modify the parameters and > receive a List as preGet() does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4918) HTablePool Constructor may cause unintended behavior
[
https://issues.apache.org/jira/browse/HBASE-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160718#comment-13160718
]
Hadoop QA commented on HBASE-4918:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12505726/HTablePool.java.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 javadoc. The javadoc tool appears to have generated -160 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 71 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestAdmin
org.apache.hadoop.hbase.client.TestInstantSchemaChange
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/415//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/415//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/415//console
This message is automatically generated.
> HTablePool Constructor may cause unintended behavior
>
>
> Key: HBASE-4918
> URL: https://issues.apache.org/jira/browse/HBASE-4918
> Project: HBase
> Issue Type: Bug
> Components: client
> Environment: r1125533
>Reporter: Kitora, Naoki
> Attachments: HTablePool.java.patch
>
>
> {code:title=HTablePool.java}
> 96 public HTablePool(final Configuration config, final int maxSize,
> 97 final HTableInterfaceFactory tableFactory) {
> 98 this(config, maxSize, null, PoolType.Reusable);
> 99 }
> {code}
> I think that 3rd argument in line 98 should be "tableFactory".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4912) HDFS API Changes
[ https://issues.apache.org/jira/browse/HBASE-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160713#comment-13160713 ] Jonathan Hsieh commented on HBASE-4912: --- I think this this might be one that is related to this bucket HADOOP-7873. > HDFS API Changes > > > Key: HBASE-4912 > URL: https://issues.apache.org/jira/browse/HBASE-4912 > Project: HBase > Issue Type: Sub-task > Components: client, regionserver >Reporter: Nicolas Spiegelberg >Assignee: Pritam Damania > Fix For: 0.94.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
