Abhishek Singh Chouhan created HBASE-14927:
--
Summary: Backport HBASE-13014 and HBASE-14749 to branch-1 and 0.98
Key: HBASE-14927
URL: https://issues.apache.org/jira/browse/HBASE-14927
Ted Malaska created HBASE-14929:
---
Summary: There is a space missing from Table "foo" is not
currently available.
Key: HBASE-14929
URL: https://issues.apache.org/jira/browse/HBASE-14929
Project: HBase
Ted Yu created HBASE-14928:
--
Summary: Start row should be set for query through HBase REST
gateway involving globbing option
Key: HBASE-14928
URL: https://issues.apache.org/jira/browse/HBASE-14928
Project:
Thanks for the information provided so far.
Please unsubscribe me too from this mailing list.
Sent from Mail for Windows 10
From: Personal
Sent: 04 December 2015 10:08
To: dev@hbase.apache.org
Cc: u...@hbase.apache.org
Subject: unsubscribe me please from this mailing list
Please unsubscribe
Hi all,
The same way you susbscribed on your own, you will have to un-subscribe on
your own too...
https://hbase.apache.org/mail-lists.html
JMS
2015-12-04 5:56 GMT-05:00 Dinu Sweet :
> Thanks for the information provided so far.
> Please unsubscribe me too from this
Build status: Successful
If successful, the website and docs have been generated. If failed, skip to the
bottom of this email.
Use the following commands to download the patch and apply it to a clean branch
based on origin/asf-site:
wget -O-
> Snapshot of AccessController state does not include instance on region
We update a znode and wait for a state change driven by processing a watch
notification for the znode change. The watch notification is apparently
lost. Yeah, once that happens the test is dead. It shouldn't hang
This one fails pretty regularly. The fail is ugly because it spews
megabytes when it goes wrong (almost 1G on fail).
Here is an example:
Anyone up for taking a look at this flakey test?
See here for example:
It shuts down fine. It just fails too often in scheme of things. I could
just disable it.
St.Ack
On Fri, Dec 4, 2015 at 9:42 AM, Andrew Purtell wrote:
> > Snapshot of AccessController state does not include instance on region
>
> We update a znode and wait for a state
[
https://issues.apache.org/jira/browse/HBASE-14580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-14580:
-
> Make the HBaseMiniCluster compliant with Kerberos
>
[
https://issues.apache.org/jira/browse/HBASE-14580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-14580.
-
Resolution: Fixed
> Make the HBaseMiniCluster compliant with Kerberos
>
I'm fine with either option. Deprecating methods of private classes isn't
useful IMHO bit I suppose extra 'nice' for users doing things they shouldn't.
> On Dec 4, 2015, at 12:50 PM, Apekshit Sharma wrote:
>
> Ahh.. if I had mentioned it earlier, there wouldn't have been
Ahh.. if I had mentioned it earlier, there wouldn't have been any confusion.
So the thing is, earlier patches (up to v6) are deleting the functions which
take byte[] or String as argument.
These are like 15 or so 'useless' functions and I believe it's okay to
delete them.
Later I updated the
Shuaifeng Zhou created HBASE-14931:
--
Summary: Active master switches may cause region close forever
Key: HBASE-14931
URL: https://issues.apache.org/jira/browse/HBASE-14931
Project: HBase
Shuaifeng Zhou created HBASE-14932:
--
Summary: bulkload fails because file not found
Key: HBASE-14932
URL: https://issues.apache.org/jira/browse/HBASE-14932
Project: HBase
Issue Type: Bug
I see that locally all tests that start a mini cluster fail.
In the log I see 1000's of messages like these:2015-12-04 22:55:48,215 ERROR
[newbunny,41236,1449298547569_ChoreService_107] se
rver.NIOServerCnxnFactory$1(44): Thread
Thread[newbunny,41236,1449298547569_ChoreService_107,5,main] died
Commented on HBASE-14922, which introduces this class, along with a proposed
fix.
Thanks.
-- Lars
From: "la...@apache.org"
To: HBase Dev List ; Elliott Clark
Sent: Friday, December 4, 2015 11:14 PM
Subject: master unhealthy
Would be a pity to disable the test. On the other hand we seem to flake
wherever using watcher triggers in miniclusters to move state forward.
That's fixed by porting the notification to ProcV2. Otherwise, we hack
around the edges (like HBASE-14209).
On Fri, Dec 4, 2015 at 9:47 AM, Stack
I see. Any chance of similar hack in this test? Or disabling this test in
all but master branch? Or a generic version of your hack (probably not)?
Getting a successful test run requires our going through all unit tests
twice, first on jdk7 and then on jdk8. The probability for fail is high
>
> Any chance of similar hack in this test?
If we don't need multiple regionservers in the minicluster for this test,
yes.
On Fri, Dec 4, 2015 at 11:00 AM, Stack wrote:
> I see. Any chance of similar hack in this test? Or disabling this test in
> all but master branch? Or
Dima Spivak created HBASE-14930:
---
Summary: check_compatibility.sh needs smarter exit codes
Key: HBASE-14930
URL: https://issues.apache.org/jira/browse/HBASE-14930
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-13426.
-
Resolution: Fixed
build has been live since the last jenkins clean up.
> add java6 builds to
23 matches
Mail list logo