[
https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15261:
--
Attachment: HBASE-15261-001.patch
Retry
+1 on patch. Needs to be volatile.
Hard to make a test of concurrent
stack created HBASE-15414:
-
Summary: Bound the size of multi request returns and/or allow
return of partial result up to client
Key: HBASE-15414
URL: https://issues.apache.org/jira/browse/HBASE-15414
Project:
stack created HBASE-15416:
-
Summary: TestHFileBackedByBucketCache is flakey since it went in
Key: HBASE-15416
URL: https://issues.apache.org/jira/browse/HBASE-15416
Project: HBase
Issue Type: Sub-tas
[
https://issues.apache.org/jira/browse/HBASE-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15416:
--
Attachment: 15416.patch
I applied this. Marks test large and clears the global cache just in case. When
large,
[
https://issues.apache.org/jira/browse/HBASE-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15416:
--
Assignee: stack
Fix Version/s: 2.0.0
> TestHFileBackedByBucketCache is flakey since it went in
> -
[
https://issues.apache.org/jira/browse/HBASE-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184092#comment-15184092
]
stack commented on HBASE-15416:
---
Pushed patch to master. Leaving open to see if this fixes
[
https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15261:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 1.4.0
1.1.4
stack created HBASE-15421:
-
Summary: Convert TestStoreScanner to junit4 from junit3 and clean
up close of scanners
Key: HBASE-15421
URL: https://issues.apache.org/jira/browse/HBASE-15421
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15421:
--
Attachment: 15421.patch
What I pushed.
> Convert TestStoreScanner to junit4 from junit3 and clean up close of
[
https://issues.apache.org/jira/browse/HBASE-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15421:
--
Affects Version/s: 2.0.0
Dang. Can only push to master w/o work. That'll do for now.
> Convert TestStoreScanne
[
https://issues.apache.org/jira/browse/HBASE-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-15421.
---
Resolution: Fixed
Fix Version/s: 2.0.0
Resolving. Simple refactoring of a test.
> Convert TestStoreSc
[
https://issues.apache.org/jira/browse/HBASE-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15421:
--
Priority: Minor (was: Major)
> Convert TestStoreScanner to junit4 from junit3 and clean up close of scanners
>
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184446#comment-15184446
]
stack commented on HBASE-15265:
---
Excellent.
I owe review and a run of ITBLL up on cluster
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v4.patch
Patch with tests. Optimize seems broke to me. We keep SKIPping even though
we've fou
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185775#comment-15185775
]
stack commented on HBASE-15392:
---
bq, If there's a seek to next row and optimize decides to
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185799#comment-15185799
]
stack commented on HBASE-15392:
---
If I purge this whole section from optimize:
{code}
c
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185886#comment-15185886
]
stack commented on HBASE-15392:
---
Oh, just to say that the testOptimize will fail because I
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186240#comment-15186240
]
stack commented on HBASE-15392:
---
I expected TestStoreScanner to fail until I figure what ex
[
https://issues.apache.org/jira/browse/HBASE-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186544#comment-15186544
]
stack commented on HBASE-15314:
---
Thanks [~Amal Joshy]
bq. But it is not possible to obtain
[
https://issues.apache.org/jira/browse/HBASE-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186567#comment-15186567
]
stack commented on HBASE-15406:
---
This issue is 'critical'?
bq. I really don't like one th
[
https://issues.apache.org/jira/browse/HBASE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186595#comment-15186595
]
stack commented on HBASE-15398:
---
The storeHeap/joinedHeap came in here:
{code}
commit 3995
[
https://issues.apache.org/jira/browse/HBASE-15180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186625#comment-15186625
]
stack commented on HBASE-15180:
---
The horrid names are fine by me. They are explicit and for
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187434#comment-15187434
]
stack commented on HBASE-15392:
---
bq. ...the thing is that if we have a scan with specified
[
https://issues.apache.org/jira/browse/HBASE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187477#comment-15187477
]
stack commented on HBASE-15398:
---
Result has up to this not needed sorting. Adding it implie
[
https://issues.apache.org/jira/browse/HBASE-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187490#comment-15187490
]
stack commented on HBASE-15431:
---
bq. I tried to increase -XX:FreqInlineSize to 1010 to inli
[
https://issues.apache.org/jira/browse/HBASE-15378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187527#comment-15187527
]
stack commented on HBASE-15378:
---
Yes. Once w/ 1.7 and then again w/ 1.8. As of yesterday, w
[
https://issues.apache.org/jira/browse/HBASE-15378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187532#comment-15187532
]
stack commented on HBASE-15378:
---
+1 on patch. Thanks [~yangzhe1991] for nice fix.
> Scanne
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187548#comment-15187548
]
stack commented on HBASE-15392:
---
So, while waiting on how optimize is meant to work when th
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: reads.png
gc.png
Two charts comparing GC and hits w/ patch and w/o. Weird is how li
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: reads.png
gc.png
io.png
Small YCSB test comparing before and after
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188782#comment-15188782
]
stack commented on HBASE-15265:
---
Needs a release note when you get a chance [~Apache9]
Why
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188788#comment-15188788
]
stack commented on HBASE-15265:
---
Would this be tough to put on branch-1 [~Apache9]? Would b
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189602#comment-15189602
]
stack commented on HBASE-15392:
---
bq. If the SEEK gets us to another block it does the SEEK
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189622#comment-15189622
]
stack commented on HBASE-15392:
---
Thanks for the text diagram [~lhofhansl] Let me add it to
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189725#comment-15189725
]
stack commented on HBASE-15392:
---
Thanks for reminder. Let me doc this because it not plain
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15265:
--
Release Note:
To enable, set the WALProvider as follows:
{code}
hbase.wal.provider
asyncfs
{code}
To check
[
https://issues.apache.org/jira/browse/HBASE-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189867#comment-15189867
]
stack commented on HBASE-15360:
---
Thanks [~mantonov]
> Fix flaky TestSimpleRpcScheduler
> -
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190139#comment-15190139
]
stack commented on HBASE-15265:
---
Ok. Finished a review. I didn't go too deep. Looks good to
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190162#comment-15190162
]
stack commented on HBASE-15265:
---
Though, I wish we could get an ITBLL run in that showed it
[
https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190170#comment-15190170
]
stack commented on HBASE-15261:
---
[~huaxiang] Want me to revert then?
> Make Throwable t in
[
https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-15261:
---
Reopening because reverted everywhere.. not needed afterall
> Make Throwable t in DaughterOpener volatile
>
[
https://issues.apache.org/jira/browse/HBASE-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-15261.
---
Resolution: Invalid
Resolving again as not needed afterall
> Make Throwable t in DaughterOpener volatile
> -
[
https://issues.apache.org/jira/browse/HBASE-15441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190208#comment-15190208
]
stack commented on HBASE-15441:
---
warmup says: "...It synchrnously opens the region and clos
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190460#comment-15190460
]
stack commented on HBASE-15265:
---
ok
> Implement an asynchronous FSHLog
> -
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190522#comment-15190522
]
stack commented on HBASE-15392:
---
[~lhofhansl] When you say
bq. The seek keys will neve
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190523#comment-15190523
]
stack commented on HBASE-15392:
---
[~lhofhansl] When you say
bq. The seek keys will neve
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190593#comment-15190593
]
stack commented on HBASE-15392:
---
bq. Alas won't work either, since the next indexed key is
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v5.patch
v5. Doc not done yet because I am not yet sure on the index compare. Also need
to ad
[
https://issues.apache.org/jira/browse/HBASE-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191477#comment-15191477
]
stack commented on HBASE-15406:
---
To be more clear, -1 on a patch that has master doing a ro
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v6.patch
-v6 includes your comment w/ an edit of what was in optimize. Will commit if
hadoopq
[
https://issues.apache.org/jira/browse/HBASE-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191887#comment-15191887
]
stack commented on HBASE-15447:
---
Makes sense. Throw up a patch if you have a moment [~wchev
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v7.patch
Address [~lhofhansl] comment. Retry. See if docker succeeds this time.
> Single Cell
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192681#comment-15192681
]
stack commented on HBASE-15265:
---
I think we've run into this before:
{code}
[0m[91mERROR
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v7.patch
Retry
> Single Cell Get reads two HFileBlocks
>
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193575#comment-15193575
]
stack commented on HBASE-15392:
---
[~danielpol]
* The index contains the first key in a blo
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v7.patch
Some hadoopqa builds are running... others are getting this docker fail
retry
>
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193616#comment-15193616
]
stack commented on HBASE-15265:
---
DLR never worked and is now deprecated and to be removed (
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193662#comment-15193662
]
stack commented on HBASE-15392:
---
[~danielpol]
bq. Maybe it a matter of how scan is impleme
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v7.patch
Retry. I unchecked RUN_IN_DOCKER
> Single Cell Get reads two HFileBlocks
> -
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193850#comment-15193850
]
stack commented on HBASE-15392:
---
I filed HBASE-15457 [~danielpol] Lets continue this discus
stack created HBASE-15457:
-
Summary: [performance] Save-a-seek; hint HFileReader when Scan is
a "Get" Scan
Key: HBASE-15457
URL: https://issues.apache.org/jira/browse/HBASE-15457
Project: HBase
Issu
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Release Note:
When an explicit Get with a one or more columns specified, we at a minimum,
were overseeking, re
[
https://issues.apache.org/jira/browse/HBASE-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194017#comment-15194017
]
stack commented on HBASE-15453:
---
Yeah... remove the @Test... Add a main that calls your tes
[
https://issues.apache.org/jira/browse/HBASE-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15453:
--
Assignee: Lars Hofhansl
Priority: Critical (was: Major)
Component/s: Performance
Issue Type:
stack created HBASE-15462:
-
Summary: Docker-based builds failing...
Key: HBASE-15462
URL: https://issues.apache.org/jira/browse/HBASE-15462
Project: HBase
Issue Type: Bug
Components: build
[
https://issues.apache.org/jira/browse/HBASE-15459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194088#comment-15194088
]
stack commented on HBASE-15459:
---
Looks great Good stuff
> Fix infer issues in hbase-se
[
https://issues.apache.org/jira/browse/HBASE-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194403#comment-15194403
]
stack commented on HBASE-15416:
---
See the note by [~liushaohui] over in HBASE-15409
{code}
[
https://issues.apache.org/jira/browse/HBASE-15457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194416#comment-15194416
]
stack commented on HBASE-15457:
---
HFIleBlock has notion of a block 'range'. HFileReaderImpl
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v7.patch
The jdk8 tests failed because of outstanding TestSimpleRpcScheduler failure.
This is
[
https://issues.apache.org/jira/browse/HBASE-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195252#comment-15195252
]
stack commented on HBASE-15360:
---
Ok I disable this for now [~mantonov]? Its a small test so
[
https://issues.apache.org/jira/browse/HBASE-15265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195263#comment-15195263
]
stack commented on HBASE-15265:
---
[~Apache9] none. I am trying to test it on a cluster befor
[
https://issues.apache.org/jira/browse/HBASE-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195268#comment-15195268
]
stack commented on HBASE-15452:
---
[~lhofhansl] You did compare of locking techniques and in
[
https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196527#comment-15196527
]
stack commented on HBASE-14070:
---
Just to note the importance of this effort.
Was chatting
[
https://issues.apache.org/jira/browse/HBASE-15467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196692#comment-15196692
]
stack commented on HBASE-15467:
---
What is TableSchema?
The TableDescrriptor stuff came in h
[
https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196699#comment-15196699
]
stack commented on HBASE-14070:
---
bq. The tracker just drops the older sequence id. It doesn
[
https://issues.apache.org/jira/browse/HBASE-15467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196818#comment-15196818
]
stack commented on HBASE-15467:
---
That explains it. Thanks. +1 then.
> Remove 1.x/2.0 Table
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15477:
--
Attachment: 15477v3.patch
Fix compile error
> Do not save 'next block header' when we cache hfileblocks
>
[
https://issues.apache.org/jira/browse/HBASE-13938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-13938:
--
Release Note: Use the master's timestamp when sending hbase:meta edits on
region merge to ensure proper orderin
[
https://issues.apache.org/jira/browse/HBASE-15460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202536#comment-15202536
]
stack commented on HBASE-15460:
---
Skimmed. +1
> Fix infer issues in hbase-common
>
[
https://issues.apache.org/jira/browse/HBASE-15405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15405:
--
Attachment: HBASE-15405-master-v4.patch
Retry
> Fix PE logging and wrong defaults in help message
> --
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15477:
--
Attachment: 15366v4.patch
Address [~ram_krish] comments up on rb and fix failing unit tests
> Do not save 'nex
[
https://issues.apache.org/jira/browse/HBASE-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15392:
--
Attachment: 15392v7 (1).patch
Retry. See if timeouts have gone away
> Single Cell Get reads two HFileBlocks
>
[
https://issues.apache.org/jira/browse/HBASE-13895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-13895:
--
Release Note: If the master went to assign a region concurrent with a
RegionServer abort, the returned RegionSe
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15477:
--
Attachment: 15477v2.patch
Finished patch
> Do not save 'next block header' when we cache hfileblocks
> ---
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15477:
--
Status: Patch Available (was: Open)
> Do not save 'next block header' when we cache hfileblocks
>
[
https://issues.apache.org/jira/browse/HBASE-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197442#comment-15197442
]
stack commented on HBASE-15360:
---
bq. I'm already on the bed and using a mobile phone to ty
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200240#comment-15200240
]
stack commented on HBASE-15477:
---
Commit message. Will post to rb when I do up v2 of this pa
[
https://issues.apache.org/jira/browse/HBASE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197524#comment-15197524
]
stack commented on HBASE-15398:
---
bq. I checked the code and run a small test locally, as lo
[
https://issues.apache.org/jira/browse/HBASE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197703#comment-15197703
]
stack commented on HBASE-15398:
---
Thanks [~yangzhe1991]
Yes, lets warn users against joined
[
https://issues.apache.org/jira/browse/HBASE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197477#comment-15197477
]
stack commented on HBASE-15398:
---
In your list, #3 is the optional. #1 and #2 are required/f
[
https://issues.apache.org/jira/browse/HBASE-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15360:
--
Resolution: Fixed
Assignee: Duo Zhang (was: Mikhail Antonov)
Hadoop Flags: Reviewed
Fix Ve
stack created HBASE-15477:
-
Summary: Do not save 'next block header' when we cache hfileblocks
Key: HBASE-15477
URL: https://issues.apache.org/jira/browse/HBASE-15477
Project: HBase
Issue Type: Sub-t
[
https://issues.apache.org/jira/browse/HBASE-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199772#comment-15199772
]
stack commented on HBASE-15349:
---
[~ashish singhi] I don't think so but could back this out
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15477:
--
Attachment: 15477.patch
First cut. Below is the commit message. This patch actually overdoes it. I'm
going to
[
https://issues.apache.org/jira/browse/HBASE-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199778#comment-15199778
]
stack commented on HBASE-15349:
---
We don't seem to get the timeouts when we build trunk, jus
[
https://issues.apache.org/jira/browse/HBASE-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202361#comment-15202361
]
stack commented on HBASE-15477:
---
RB won't let me update. The difference from RB is adding t
[
https://issues.apache.org/jira/browse/HBASE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197333#comment-15197333
]
stack commented on HBASE-15398:
---
bq. Is it a good idea that adding a new flag in protocol o
[
https://issues.apache.org/jira/browse/HBASE-15481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15481:
--
Attachment: HBASE-15481-v1.patch
Retry to see if timeouts this time around.
+1 on patch.
We should commit HBA
[
https://issues.apache.org/jira/browse/HBASE-15360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197312#comment-15197312
]
stack commented on HBASE-15360:
---
Lets commit. Our tests are in a sorry state while this is
[
https://issues.apache.org/jira/browse/HBASE-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-15349:
---
Reopening. Let me revert to see if this has anything to do w/ the timeouts we
are seeing frequently on hadoopqa.
501 - 600 of 37919 matches
Mail list logo
