stack created HBASE-19960:
-
Summary: Doc test timeouts and test categories in hbase2
Key: HBASE-19960
URL: https://issues.apache.org/jira/browse/HBASE-19960
Project: HBase
Issue Type: Sub-task
Chance Li created HBASE-19959:
-
Summary: How much RAM space is to be really consumed by the
memstore?
Key: HBASE-19959
URL: https://issues.apache.org/jira/browse/HBASE-19959
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-19958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-19958.
---
Resolution: Invalid
Network lag...
> General framework to transit sync replication state
>
Duo Zhang created HBASE-19957:
-
Summary: General framework to transit sync replication state
Key: HBASE-19957
URL: https://issues.apache.org/jira/browse/HBASE-19957
Project: HBase
Issue Type:
Duo Zhang created HBASE-19958:
-
Summary: General framework to transit sync replication state
Key: HBASE-19958
URL: https://issues.apache.org/jira/browse/HBASE-19958
Project: HBase
Issue Type:
stack created HBASE-19956:
-
Summary: Remove category as a consideration timing out tests; set
all test to timeout at 10minutes regardless
Key: HBASE-19956
URL: https://issues.apache.org/jira/browse/HBASE-19956
Response to the survey so far. I think it confirms our expectations.
Multiple choice was allowed so percentage will not add up to 100%.
1.0: 8%
1.1: 21%
1.2: 47%
1.3: 24%
1.4: 8%
1.5: 5%
[image: Inline image 1]
On Fri, Feb 2, 2018 at 3:40 PM, Andrew Purtell wrote:
>
The HBase team is happy to announce the immediate availability of Apach
āeā
e HBase 1.4.1!
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardware.
stack created HBASE-19955:
-
Summary: Put back CategoryBased test method timeout Annotation
Key: HBASE-19955
URL: https://issues.apache.org/jira/browse/HBASE-19955
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-19947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-19947.
---
Resolution: Fixed
removed extra conf line and pushed to branch-2 and master. thanks for review,
Ted Yu created HBASE-19954:
--
Summary: ShutdownHook should check whether shutdown hook is
tracked by ShutdownHookManager
Key: HBASE-19954
URL: https://issues.apache.org/jira/browse/HBASE-19954
Project: HBase
Josh Elser created HBASE-19953:
--
Summary: Avoid calling post* hook when procedure fails
Key: HBASE-19953
URL: https://issues.apache.org/jira/browse/HBASE-19953
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-19791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-19791.
---
Resolution: Fixed
Re-resolving. It no longer shows in flakies list.
> TestZKAsyncRegistry hangs
>
[
https://issues.apache.org/jira/browse/HBASE-19840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-19840.
---
Resolution: Fixed
Re-resolving. This fell off the flakies list.
> Flakey TestMetaWithReplicas
>
Hi Mike,
You are right. For rpc throttling, definitely it is retryable. For storage
quota, I think it will be fail faster (non-retryable).
We probably need to separate these two types of exceptions, I will do some
more research and follow up.
Thanks,
Huaxiang
> On Feb 7, 2018,
I think, philosophically, there can be two kinds of QEE -
For throttling, we can retry. The quota is a temporal quota - you have done
too many operations this minute, please try again next minute and
everything will work.
For storage, we shouldn't retry. The quota is a fixed quote - you have
Hi Stack,
I run into a case that a mapreduce job in hive cannot finish because it
runs into a QEE.
I need to look into the hive mr task to see if QEE is not handled correctly in
hbase code or in hive code.
I am thinking that if QEE is a retryable exception, then it should be taken
On Fri, Feb 2, 2018 at 9:13 PM, Mike Drob wrote:
> Hi folks, has there been any consideration put forth toward the next
> HBaseCon? The last one was very productive for me personally, but I hadn't
> heard anything about the schedule for 2018 so figured I could ask on list.
>
QEE being a DNRIOE seems right on the face of it.
But if throttling, a DNRIOE is inappropriate. Where you seeing a QEE in a
throttling scenario Huaxiang?
Thanks,
S
On Tue, Feb 6, 2018 at 4:56 PM, Huaxiang Sun wrote:
> Hi HBase devs,
>
> I found that
[
https://issues.apache.org/jira/browse/HBASE-8997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-8997.
--
Resolution: Not A Problem
Closed this one, because the test does not exist anymore.
> Restore
[
https://issues.apache.org/jira/browse/HBASE-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-11156.
---
Resolution: Not A Problem
Close this one, because the discussion was moved to the mailing
Duo Zhang created HBASE-19952:
-
Summary: Find tests which are declared with wrong category
Key: HBASE-19952
URL: https://issues.apache.org/jira/browse/HBASE-19952
Project: HBase
Issue Type:
Duo Zhang created HBASE-19951:
-
Summary: Cleanup the explicit timeout value for test method
Key: HBASE-19951
URL: https://issues.apache.org/jira/browse/HBASE-19951
Project: HBase
Issue Type:
23 matches
Mail list logo