[
https://issues.apache.org/jira/browse/HBASE-15295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212152#comment-15212152
]
stack commented on HBASE-15295:
---
First, nice digging [~enis]. Good one.
RPC while holding
[
https://issues.apache.org/jira/browse/HBASE-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212300#comment-15212300
]
stack commented on HBASE-15499:
---
Why? Looks like non-controversial feature addition to me.
[
https://issues.apache.org/jira/browse/HBASE-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212303#comment-15212303
]
stack commented on HBASE-15496:
---
For a huge KeyValue, there is nothing to do if it already
[
https://issues.apache.org/jira/browse/HBASE-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212312#comment-15212312
]
stack commented on HBASE-15496:
---
Patch LGTM. No good throwing RowTooBigException for intern
[
https://issues.apache.org/jira/browse/HBASE-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15496:
--
Attachment: HBASE-15496.patch
Retry even though the failures are well-known flakies
a
> Throw RowTooBigExcepti
[
https://issues.apache.org/jira/browse/HBASE-15418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212564#comment-15212564
]
stack commented on HBASE-15418:
---
LGTM
> Clean up un-used warning in test util
> --
[
https://issues.apache.org/jira/browse/HBASE-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212575#comment-15212575
]
stack commented on HBASE-15535:
---
Mind putting up a patch [~atanumishra]? Thanks.
> HBase R
[
https://issues.apache.org/jira/browse/HBASE-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212591#comment-15212591
]
stack commented on HBASE-15499:
---
Patch looks good to me. I like your use of our existing ty
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212780#comment-15212780
]
stack commented on HBASE-15265:
---
Go for it. In another issue we can work out if we should m
[
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212838#comment-15212838
]
stack commented on HBASE-14921:
---
Reviewed again after another read of the attached diagram.
[
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212842#comment-15212842
]
stack commented on HBASE-14921:
---
I still don't get this sentence from the diagram attachmen
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212981#comment-15212981
]
stack commented on HBASE-14920:
---
A few notes on the patch
Is the comment right when it say
[
https://issues.apache.org/jira/browse/HBASE-15506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214414#comment-15214414
]
stack commented on HBASE-15506:
---
HDFS-7276 adds 4 new configs (5 including the enable) wher
[
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214437#comment-15214437
]
stack commented on HBASE-14921:
---
bq. As you have mentioned, CellBlock is implementing Concu
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214526#comment-15214526
]
stack commented on HBASE-15525:
---
So in your patch, ByteBufferPool is a FixedSizeBBP?
So we
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214538#comment-15214538
]
stack commented on HBASE-15525:
---
Oh, so, it addresses this issue because sizing of the offh
stack created HBASE-15549:
-
Summary: Change TABLES_ON_MASTER to false in master branch
Key: HBASE-15549
URL: https://issues.apache.org/jira/browse/HBASE-15549
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15549:
--
Summary: Change TABLES_ON_MASTER to 'none' in master branch (was: Change
TABLES_ON_MASTER to false in master b
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15549:
--
Summary: Undo HMaster carrying regions in master branch as default (was:
Change TABLES_ON_MASTER to 'none' in
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15549:
--
Attachment: 15549.patch
Add a means of disabling master-as-regionserver. Default in patch is that
master CAN
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214956#comment-15214956
]
stack commented on HBASE-15549:
---
bq. What's not finished?
What Master's personality is go
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214963#comment-15214963
]
stack commented on HBASE-15549:
---
bq. How is this different from hbase.balancer.tablesOnMast
[
https://issues.apache.org/jira/browse/HBASE-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214983#comment-15214983
]
stack commented on HBASE-15544:
---
Yeah, we allocate buffers to do compression. What you sugg
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215009#comment-15215009
]
stack commented on HBASE-15525:
---
So, just to note, on read side, we are already reading in
stack created HBASE-15550:
-
Summary: Backport HBASE-12220 hedgedRead metrics to 1.2+
Key: HBASE-15550
URL: https://issues.apache.org/jira/browse/HBASE-15550
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15550:
--
Attachment: 15550.branch-1.2.txt
Lets see how this patch does.
> Backport HBASE-12220 hedgedRead metrics to 1.
[
https://issues.apache.org/jira/browse/HBASE-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15550:
--
Assignee: stack
Affects Version/s: 1.2.2
1.3.0
Status: Patch
stack created HBASE-1:
-
Summary: Memory Management
Key: HBASE-1
URL: https://issues.apache.org/jira/browse/HBASE-1
Project: HBase
Issue Type: Umbrella
Reporter: stack
Umbrel
[
https://issues.apache.org/jira/browse/HBASE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1:
--
Attachment: download.svg
Start of a diagram identifying current bigbuffer allocations.
> Memory Management
> -
[
https://issues.apache.org/jira/browse/HBASE-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15513:
--
Issue Type: Sub-task (was: Improvement)
Parent: HBASE-1
> hbase.hregion.memstore.chunkpool.maxsize
[
https://issues.apache.org/jira/browse/HBASE-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-14613:
--
Issue Type: Sub-task (was: Brainstorming)
Parent: HBASE-1
> Remove MemStoreChunkPool?
> --
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15525:
--
Issue Type: Sub-task (was: Bug)
Parent: HBASE-1
> OutOfMemory could occur when using BoundedByteBu
[
https://issues.apache.org/jira/browse/HBASE-15295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215977#comment-15215977
]
stack commented on HBASE-15295:
---
bq. Phoenix defines its own RPCScheduler and controller wh
[
https://issues.apache.org/jira/browse/HBASE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216003#comment-15216003
]
stack commented on HBASE-1:
---
bq. we use BBs from the pool (BoundedByteBufferPool) and r
[
https://issues.apache.org/jira/browse/HBASE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216004#comment-15216004
]
stack commented on HBASE-1:
---
Linking HBASE-15542 (Can't make it a subtask because it ha
[
https://issues.apache.org/jira/browse/HBASE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1:
--
Description:
Umbrella issue on memory management. One-stop shop to learn how we're doing it,
tenets, and work
[
https://issues.apache.org/jira/browse/HBASE-15543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216018#comment-15216018
]
stack commented on HBASE-15543:
---
The method creates a variety of Cell types dependent on se
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216025#comment-15216025
]
stack commented on HBASE-15362:
---
Please raise your observation that we may be able to do w/
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15362:
--
Issue Type: Sub-task (was: Bug)
Parent: HBASE-1
> Compression Algorithm does not respect config pa
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216050#comment-15216050
]
stack commented on HBASE-15362:
---
On the patch, I think the original code is wrong where it
[
https://issues.apache.org/jira/browse/HBASE-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216054#comment-15216054
]
stack commented on HBASE-15499:
---
Patch looks good. What did you change [~heliangliang]? Tha
[
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216085#comment-15216085
]
stack commented on HBASE-14921:
---
bq. We want CellSet to have different types of delegatees,
[
https://issues.apache.org/jira/browse/HBASE-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216100#comment-15216100
]
stack commented on HBASE-15550:
---
Thanks [~busbey]. Think it'd be ok for 1.2? These metrics
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216108#comment-15216108
]
stack commented on HBASE-15549:
---
bq. With a large enough cluster I get double assignments,
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216207#comment-15216207
]
stack commented on HBASE-15549:
---
bq. There's no times that we need to finalize a risky oper
[
https://issues.apache.org/jira/browse/HBASE-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216210#comment-15216210
]
stack commented on HBASE-13639:
---
If you post a paragraph or two, I can help massage it into
[
https://issues.apache.org/jira/browse/HBASE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216213#comment-15216213
]
stack commented on HBASE-1:
---
Is there an issue for this? Seems kinda important. Good on
[
https://issues.apache.org/jira/browse/HBASE-15327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216305#comment-15216305
]
stack commented on HBASE-15327:
---
+1 on patch and on rerunning hadoopqa
> Canary will alway
[
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216318#comment-15216318
]
stack commented on HBASE-14921:
---
I tried changing CNM to NM and it fails because we use tai
[
https://issues.apache.org/jira/browse/HBASE-15295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-15295:
---
This patch causes TestMasterNoCluster#testFailover to fail always.
> MutateTableAccess.multiMutate() does not ge
[
https://issues.apache.org/jira/browse/HBASE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216539#comment-15216539
]
stack commented on HBASE-1:
---
bq. Do you want to raise a JIRA for this? I think the subt
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216662#comment-15216662
]
stack commented on HBASE-15265:
---
It took me a while but a 2B run on 9-node cluster passes w
[
https://issues.apache.org/jira/browse/HBASE-15295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216684#comment-15216684
]
stack commented on HBASE-15295:
---
Understood [~enis] Tests passed when you tried the patch b
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216720#comment-15216720
]
stack commented on HBASE-14920:
---
I like the notion of a 'CompactionMemStore' instead of a p
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216812#comment-15216812
]
stack commented on HBASE-14920:
---
I see/remember why the isCompactingMemStore method. Makes
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216864#comment-15216864
]
stack commented on HBASE-14920:
---
s/startCompact/startCompaction/g
s/doCompact/doCompaction/
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-14920:
--
Attachment: move.to.junit4.patch
Patch to integrate which changes TestMemStoreDefault to be junit4... if it
he
[
https://issues.apache.org/jira/browse/HBASE-15560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217028#comment-15217028
]
stack commented on HBASE-15560:
---
Patch looks good.
Not too interested in giving folks a ch
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218098#comment-15218098
]
stack commented on HBASE-14920:
---
bq. which reside in a segment and have very small sequ
[
https://issues.apache.org/jira/browse/HBASE-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15324:
--
Attachment: HBASE-15324_v3.patch
> Jitter may cause desiredMaxFileSize overflow in ConstantSizeRegionSplitPolic
[
https://issues.apache.org/jira/browse/HBASE-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218102#comment-15218102
]
stack commented on HBASE-15324:
---
+1 on patch. Let me rerun it.
> Jitter may cause desiredM
[
https://issues.apache.org/jira/browse/HBASE-15506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218113#comment-15218113
]
stack commented on HBASE-15506:
---
bq. In any case, we should be able to create some single s
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218139#comment-15218139
]
stack commented on HBASE-15525:
---
bq. This is some thing I discussed with you offline some t
[
https://issues.apache.org/jira/browse/HBASE-15509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218218#comment-15218218
]
stack commented on HBASE-15509:
---
What is the mysterious 'len'?
84 * @param len -
[
https://issues.apache.org/jira/browse/HBASE-15509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218289#comment-15218289
]
stack commented on HBASE-15509:
---
bq. How do we mitigate case where a Cell is 1G? All my thr
[
https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218558#comment-15218558
]
stack commented on HBASE-15536:
---
An overnight run passed (10B ITBLL with chaos monkeys on 8
[
https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218703#comment-15218703
]
stack commented on HBASE-15536:
---
I reviewed HBASE-15407 and HBASE-15538. They seem good to
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218712#comment-15218712
]
stack commented on HBASE-15265:
---
There I go asking for same stuff again... Thanks for filin
stack created HBASE-15566:
-
Summary: Add timeouts on TestMobFlushSnapshotFromClient and
TestRegionMergeTransactionOnCluster
Key: HBASE-15566
URL: https://issues.apache.org/jira/browse/HBASE-15566
Project: HBa
[
https://issues.apache.org/jira/browse/HBASE-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15566:
--
Attachment: timeouts.patch
Let me push this.
> Add timeouts on TestMobFlushSnapshotFromClient and
> TestRegio
[
https://issues.apache.org/jira/browse/HBASE-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-15566.
---
Resolution: Fixed
Assignee: stack
Fix Version/s: 2.0.0
Pushed to master
> Add timeouts on Te
[
https://issues.apache.org/jira/browse/HBASE-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15324:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.4.0
1.3.0
[
https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218822#comment-15218822
]
stack commented on HBASE-15536:
---
I did a rough compare where I ran ycsb load against a sing
[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218899#comment-15218899
]
stack commented on HBASE-15537:
---
When would there ever be more than one provider? In Region
[
https://issues.apache.org/jira/browse/HBASE-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219097#comment-15219097
]
stack commented on HBASE-15549:
---
Balancer gets messed up if master is not carrying regions:
[
https://issues.apache.org/jira/browse/HBASE-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219295#comment-15219295
]
stack commented on HBASE-15536:
---
Running this compare from HBASE-10156
{code}
$ for i in 1
[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219310#comment-15219310
]
stack commented on HBASE-15537:
---
[~busbey] Your opinion appreciated here.
A provider insid
[
https://issues.apache.org/jira/browse/HBASE-15569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219324#comment-15219324
]
stack commented on HBASE-15569:
---
Smile. +1
> Make Bytes.toStringBinary faster
> --
[
https://issues.apache.org/jira/browse/HBASE-15569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15569:
--
Status: Patch Available (was: Open)
> Make Bytes.toStringBinary faster
>
>
>
[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219986#comment-15219986
]
stack commented on HBASE-14920:
---
[~eshcar] I suggested changing stopCompact to stopCompacti
[
https://issues.apache.org/jira/browse/HBASE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221102#comment-15221102
]
stack commented on HBASE-15556:
---
bq. Hold that thought about our custom bit...don't want to
[
https://issues.apache.org/jira/browse/HBASE-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221130#comment-15221130
]
stack commented on HBASE-15571:
---
You fellows get the bit that we want to keep the *Services
[
https://issues.apache.org/jira/browse/HBASE-15569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15569:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.2.2
1.4.0
[
https://issues.apache.org/jira/browse/HBASE-15480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221152#comment-15221152
]
stack commented on HBASE-15480:
---
Group check sounds good. The new API would be used by uppe
[
https://issues.apache.org/jira/browse/HBASE-15572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221217#comment-15221217
]
stack commented on HBASE-15572:
---
bq. Normally the docs mentioned above can be added to this
[
https://issues.apache.org/jira/browse/HBASE-15576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221841#comment-15221841
]
stack commented on HBASE-15576:
---
Hello [~yangzhe1991]
bq. Now for ResultScanner.next(), we
[
https://issues.apache.org/jira/browse/HBASE-15576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221841#comment-15221841
]
stack edited comment on HBASE-15576 at 4/1/16 3:27 PM:
---
Hello [~yan
[
https://issues.apache.org/jira/browse/HBASE-15576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221954#comment-15221954
]
stack commented on HBASE-15576:
---
bq. So for users, ResultScanner.next() will still be block
[
https://issues.apache.org/jira/browse/HBASE-14921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221995#comment-15221995
]
stack commented on HBASE-14921:
---
Nice review [~anoop.hbase] On not needing third int, I lik
[
https://issues.apache.org/jira/browse/HBASE-15562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1551#comment-1551
]
stack commented on HBASE-15562:
---
SurvivorRatio? We'd be making less garbage when using pool
[
https://issues.apache.org/jira/browse/HBASE-15581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222305#comment-15222305
]
stack commented on HBASE-15581:
---
Hurray. Want to go to PB2.6? We'll have to shade?
> Reduc
[
https://issues.apache.org/jira/browse/HBASE-15576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222315#comment-15222315
]
stack commented on HBASE-15576:
---
bq. we think we should save mvcc in HFile to solve some is
[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223638#comment-15223638
]
stack commented on HBASE-15537:
---
Skimmed. Looks great.+1
[~busbey] when you get a chance,
[
https://issues.apache.org/jira/browse/HBASE-15560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224913#comment-15224913
]
stack commented on HBASE-15560:
---
Yes (didn't realize it jdk8 only)... I still owe basic per
[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225647#comment-15225647
]
stack commented on HBASE-15537:
---
bq. Or could you further clarify your concern if I misunde
[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226562#comment-15226562
]
stack commented on HBASE-15537:
---
bq. Is it enough to get the statistics you want?
Yes. I c
stack created HBASE-15594:
-
Summary: [YCSB] Improvements
Key: HBASE-15594
URL: https://issues.apache.org/jira/browse/HBASE-15594
Project: HBase
Issue Type: Umbrella
Reporter: stack
Runn
[
https://issues.apache.org/jira/browse/HBASE-15594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15594:
--
Priority: Critical (was: Major)
> [YCSB] Improvements
> ---
>
> Key: HBASE-155
[
https://issues.apache.org/jira/browse/HBASE-15594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226612#comment-15226612
]
stack commented on HBASE-15594:
---
I think this a critical issue given we should be able to u
[
https://issues.apache.org/jira/browse/HBASE-15594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226655#comment-15226655
]
stack commented on HBASE-15594:
---
branch-1. branch-1 because I want to bring fixes into bran
701 - 800 of 37919 matches
Mail list logo
