cuijianwei created HBASE-10395:
--
Summary: endTime won't be set in VerifyReplication if startTime is
not set
Key: HBASE-10395
URL: https://issues.apache.org/jira/browse/HBASE-10395
Project: HBase
cuijianwei created HBASE-10396:
--
Summary: The constructor of HBaseAdmin may close the shared
HConnection
Key: HBASE-10396
URL: https://issues.apache.org/jira/browse/HBASE-10396
Project: HBase
Anoop Sam John created HBASE-10397:
--
Summary: Fix findbugs introduced from HBASE-9426
Key: HBASE-10397
URL: https://issues.apache.org/jira/browse/HBASE-10397
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-10375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Liochon resolved HBASE-10375.
-
Resolution: Fixed
Fix Version/s: 0.99.0
0.96.2
Why cross-RS RPC is going to cause deadlocks? It is a matter of logic
incorrectness, or resource outage? Say, if we set the #handler to be
large, logically deadlock still occurs?
Best regards,
Wei
From: Vladimir Rodionov vrodio...@carrieriq.com
To: dev@hbase.apache.org
Because each server has regions from many tables, the handlers on server A
may all be busy trying to write to server B. However, server Bs handlers
may all be busy handling requests from the client to update server As
index... Deadlock
On Jan 22, 2014 7:52 AM, Wei Tan w...@us.ibm.com wrote:
Why
Anoop Sam John created HBASE-10398:
--
Summary: HBase book updates for Replication after HBASE-10322
Key: HBASE-10398
URL: https://issues.apache.org/jira/browse/HBASE-10398
Project: HBase
Deadlocks are possible because cross region RPCs create cyclic dependencies in
HBase cluster.
RS1- RS2-RS3-RS1, where - is PRC call
now imagine that last call from RS3 to RS1 is blocked because there no more
available handler threads to process it.
Best regards,
Vladimir Rodionov
Principal
Ted Yu created HBASE-10399:
--
Summary: Add documentation for VerifyReplication to refguide
Key: HBASE-10399
URL: https://issues.apache.org/jira/browse/HBASE-10399
Project: HBase
Issue Type:
FYI, the Phoenix mutable secondary indexing implementation won't make
cyclical RPC calls like this. We do a single batched mutation from the RS
of the data table to the RS of the index table to do the index maintenance.
But the situation Jesse described is possible, though we have not
encountered
Thanks, Vladimir. So a RPC call RS1 -- RS2 takes two handlers, one from
RS1 and one from RS2? If that is true, then I understand that it is a
typical Dining philosophers problem.
Maybe a random yielding mechanism can solve this problem.
Best regards,
Wei
-
Wei
Hi James, I guess as long as you have cross-region RPC this cyclic
deadlock can occur? If you batch the RPC, it may be far less likely to
occur because the number of RPC is far fewer. Do I understand you
correctly?
Thanks,
Wei
-
Wei Tan, PhD
Research Staff
Jonathan Hsieh created HBASE-10400:
--
Summary: [hbck] Continue if region dir missing on region merge
attempt
Key: HBASE-10400
URL: https://issues.apache.org/jira/browse/HBASE-10400
Project: HBase
Jonathan Hsieh created HBASE-10401:
--
Summary: [hbck] perform overlap group merges in parallel
Key: HBASE-10401
URL: https://issues.apache.org/jira/browse/HBASE-10401
Project: HBase
Issue
Jonathan Hsieh created HBASE-10402:
--
Summary: [docs] Add docs on how to create and tag a point release.
Key: HBASE-10402
URL: https://issues.apache.org/jira/browse/HBASE-10402
Project: HBase
That test failure was not reproducible on my build boxes.
Last call for commits that already have a +1 for 0.98 branch, I am tagging
RC0 around midnight tonight Pacific time.
After that please consider the soft freeze over and done, my earlier
request complete. I still reserve the right to
Nick Dimiduk created HBASE-10403:
Summary: Simplify offheap cache configuration
Key: HBASE-10403
URL: https://issues.apache.org/jira/browse/HBASE-10403
Project: HBase
Issue Type: Bug
JIRA has been unavailable or throwing 503s for a few hours now. This will
have to wait one day.
On Wed, Jan 22, 2014 at 3:58 PM, Andrew Purtell apurt...@apache.org wrote:
That test failure was not reproducible on my build boxes.
Last call for commits that already have a +1 for 0.98 branch, I
Hi,
In the past hour I tried 3 times in creating a JIRA.
For the last two attempts, I got:
Error creating issue: Indexing completed with 1 errors
Has anyone got similar error ?
Thanks
Not with JIRA creations, but watching JIRAs is sending back errors. You
have to click multiple times on watch to get it right
Seems unstable.
2014/1/22 Ted Yu yuzhih...@gmail.com
Hi,
In the past hour I tried 3 times in creating a JIRA.
For the last two attempts, I got:
Error creating
I had errors to add new comments. But after refresh the page I got.
2014/1/23 Jean-Marc Spaggiari jean-m...@spaggiari.org
Not with JIRA creations, but watching JIRAs is sending back errors. You
have to click multiple times on watch to get it right
Seems unstable.
2014/1/22 Ted Yu
On Wed, Jan 22, 2014 at 7:40 PM, Ted Yu yuzhih...@gmail.com wrote:
Hi,
In the past hour I tried 3 times in creating a JIRA.
For the last two attempts, I got:
Error creating issue: Indexing completed with 1 errors
Has anyone got similar error ?
I think you ran into the Atlassian hardcoded
Yep JIRA's indexes are still broken, searches for 'fix version' etc are
returning 500s. Until tomorrow.
On Wednesday, January 22, 2014, Andrew Purtell apurt...@apache.org wrote:
JIRA has been unavailable or throwing 503s for a few hours now. This will
have to wait one day.
On Wed, Jan 22,
That, or they're importing the Phoenix github issues into JIRA. :-)
On Wed, Jan 22, 2014 at 9:36 PM, Stack st...@duboce.net wrote:
On Wed, Jan 22, 2014 at 7:40 PM, Ted Yu yuzhih...@gmail.com wrote:
Hi,
In the past hour I tried 3 times in creating a JIRA.
For the last two attempts, I
I think you ran into the Atlassian hardcoded lifetime quota for issue
creations.
St.Ack
+1
On Wed, Jan 22, 2014 at 10:01 PM, James Taylor jtay...@salesforce.comwrote:
That, or they're importing the Phoenix github issues into JIRA. :-)
On Wed, Jan 22, 2014 at 9:36 PM, Stack
25 matches
Mail list logo
