[
https://issues.apache.org/jira/browse/HBASE-16616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16057283#comment-16057283
]
deepankar commented on HBASE-16616:
---
Ah got it, thanks [~tomu.tsuruhara] for pointing me to that patch,
[
https://issues.apache.org/jira/browse/HBASE-16616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056554#comment-16056554
]
deepankar commented on HBASE-16616:
---
Hi, we have recently encountered this issue in our production and
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15896860#comment-15896860
]
deepankar commented on HBASE-16630:
---
Thanks guys for pushing this and dealing with my errors and
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889710#comment-15889710
]
deepankar commented on HBASE-16630:
---
Sorry guys I forgot to check for compilation and other minor
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-16630:
--
Attachment: HBASE-16630-v4-branch-1.X.patch
Updated patch fixing the compilation issue
>
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889510#comment-15889510
]
deepankar commented on HBASE-16630:
---
Created HBASE-17711 for tracking the addition of tests for this
[
https://issues.apache.org/jira/browse/HBASE-17711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-17711:
--
Summary: Add test for Bucket Cache fragmentation fix (was: Add test for
HBASE-16630 fix)
> Add test
[
https://issues.apache.org/jira/browse/HBASE-17711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-17711:
--
Description: Add tests for the fix in HBASE-16630
> Add test for HBASE-16630 fix
>
deepankar created HBASE-17711:
-
Summary: Add test for HBASE-16630 fix
Key: HBASE-17711
URL: https://issues.apache.org/jira/browse/HBASE-17711
Project: HBase
Issue Type: Task
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889149#comment-15889149
]
deepankar edited comment on HBASE-16630 at 3/1/17 12:17 AM:
Uploaded the
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-16630:
--
Attachment: HBASE-16630-v3-branch-1.X.patch
The patch for branch-1, branch-1.2, branch-1.3
>
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15861696#comment-15861696
]
deepankar commented on HBASE-16630:
---
About the unit test, I was busy past weeks trying to hunt down
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826660#comment-15826660
]
deepankar commented on HBASE-16630:
---
Sorry I forgot about the unit test, will see If I hack get
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765587#comment-15765587
]
deepankar commented on HBASE-16630:
---
Sorry for the late reply, I looked into Stack's suggestion and
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15635468#comment-15635468
]
deepankar commented on HBASE-16630:
---
Yeah I am looking into stacks suggestion to counter the problem I
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15635468#comment-15635468
]
deepankar edited comment on HBASE-16630 at 11/4/16 6:49 AM:
Yeah I am looking
[
https://issues.apache.org/jira/browse/HBASE-16878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-16878:
--
Attachment: HBASE-16878.patch
> Call Queue length enforced not accounting for the queue handler factor
deepankar created HBASE-16878:
-
Summary: Call Queue length enforced not accounting for the queue
handler factor
Key: HBASE-16878
URL: https://issues.apache.org/jira/browse/HBASE-16878
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15580415#comment-15580415
]
deepankar commented on HBASE-16630:
---
Sorry for the delayed reply, the bucket cache is not stuck as
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514299#comment-15514299
]
deepankar commented on HBASE-16630:
---
Which map are you referring to [~vrodionov] , I am constructing a
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-16630:
--
Attachment: HBASE-16630-v3.patch
Sorry for delay in adding the suggestion [~tedyu], I attached a patch
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508469#comment-15508469
]
deepankar commented on HBASE-16630:
---
I used it predominently for limiting the number of buckets we
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-16630:
--
Attachment: HBASE-16630-v2.patch
Attached v2, this patch changes the logic of defragmentation to the
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505115#comment-15505115
]
deepankar edited comment on HBASE-16630 at 9/20/16 12:17 AM:
-
Yup looks like
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505115#comment-15505115
]
deepankar commented on HBASE-16630:
---
Yup looks like this is exactly what we want, the idea is to pick a
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504536#comment-15504536
]
deepankar commented on HBASE-16630:
---
This is very good idea to make sure all the buckets have
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504518#comment-15504518
]
deepankar commented on HBASE-16630:
---
Ha, nice point, I missed this, but this would still not guarantee,
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489482#comment-15489482
]
deepankar commented on HBASE-16630:
---
It is moving data, but the storage of the data (i.e byte buffers )
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489296#comment-15489296
]
deepankar commented on HBASE-16630:
---
Commented on the comment above, SIGSEV should not be an issue as
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489291#comment-15489291
]
deepankar commented on HBASE-16630:
---
The only problem is currently some IOEngines (Ex:-
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489287#comment-15489287
]
deepankar commented on HBASE-16630:
---
This is correct, Defragmentation does not affect anything in the
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489282#comment-15489282
]
deepankar commented on HBASE-16630:
---
I'll remove the full lock, essentially the lock is to make sure
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488995#comment-15488995
]
deepankar commented on HBASE-16630:
---
ping [~stack], [~anoop.hbase], [~ram_krish], any suggestions ?
>
[
https://issues.apache.org/jira/browse/HBASE-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-16630:
--
Attachment: HBASE-16630.patch
> Fragmentation in long running Bucket Cache
>
deepankar created HBASE-16630:
-
Summary: Fragmentation in long running Bucket Cache
Key: HBASE-16630
URL: https://issues.apache.org/jira/browse/HBASE-16630
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486470#comment-15486470
]
deepankar commented on HBASE-16624:
---
Inorder to test we may need to refactor and isolate this function
[
https://issues.apache.org/jira/browse/HBASE-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486459#comment-15486459
]
deepankar edited comment on HBASE-16624 at 9/13/16 6:46 AM:
Function is
[
https://issues.apache.org/jira/browse/HBASE-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486459#comment-15486459
]
deepankar commented on HBASE-16624:
---
Function is nested deep inside the HFileScannerImpl and it was
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326841#comment-15326841
]
deepankar commented on HBASE-15525:
---
Pulled in the latest patch and deployed on one machine, working as
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273688#comment-15273688
]
deepankar commented on HBASE-15525:
---
We pulled in this patch and ran it on one of our production
[
https://issues.apache.org/jira/browse/HBASE-15691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262987#comment-15262987
]
deepankar commented on HBASE-15691:
---
Oh ok thanks for clarifying.
> Port HBASE-10205
[
https://issues.apache.org/jira/browse/HBASE-15691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262800#comment-15262800
]
deepankar commented on HBASE-15691:
---
Took a look at the patch, Is there a reason why we are changing
[
https://issues.apache.org/jira/browse/HBASE-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245080#comment-15245080
]
deepankar commented on HBASE-10205:
---
[~stack] and [~enis] Looks like this patch has not been committed
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223789#comment-15223789
]
deepankar commented on HBASE-15437:
---
Sorry for the mistake, fixed it now.
bq. Its pity that we dont
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15437:
--
Attachment: HBASE-15437-v1.patch
> Response size calculated in RPCServer for warning tooLarge
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15437:
--
Status: Patch Available (was: Open)
> Response size calculated in RPCServer for warning tooLarge
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15437:
--
Status: Open (was: Patch Available)
> Response size calculated in RPCServer for warning tooLarge
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223672#comment-15223672
]
deepankar commented on HBASE-15437:
---
Attached patch following suggestions from Anoop and Enis
>
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15437:
--
Attachment: HBASE-15437.patch
> Response size calculated in RPCServer for warning tooLarge responses
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15437:
--
Assignee: deepankar
Status: Patch Available (was: Open)
> Response size calculated in RPCServer
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15218608#comment-15218608
]
deepankar commented on HBASE-15525:
---
Sure happy to help
> OutOfMemory could occur when using
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15218605#comment-15218605
]
deepankar commented on HBASE-15437:
---
This means that responseTime warning will not contain responseSize
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217435#comment-15217435
]
deepankar commented on HBASE-15525:
---
Oh ok, sorry for the confusion thanks
> OutOfMemory could occur
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217417#comment-15217417
]
deepankar commented on HBASE-15525:
---
bq. Sure I will correct that.. One issue is that when we have
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217378#comment-15217378
]
deepankar commented on HBASE-15525:
---
A minor comment on the patch for the
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15216605#comment-15216605
]
deepankar commented on HBASE-15362:
---
Sure will create a jira
> Compression Algorithm does not respect
[
https://issues.apache.org/jira/browse/HBASE-15545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215126#comment-15215126
]
deepankar commented on HBASE-15545:
---
We also had a similar issue, it also allocates a lot of memory in
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215056#comment-15215056
]
deepankar commented on HBASE-15362:
---
But this change is very specific to LZO and specialized (hacky) ,
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215047#comment-15215047
]
deepankar commented on HBASE-15362:
---
Depends on the default block size we have a default block size of
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15525:
--
Summary: OutOfMemory could occur when using BoundedByteBufferPool during
RPC bursts (was: Fix
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209749#comment-15209749
]
deepankar commented on HBASE-13819:
---
I totally agree with your idea, but I think practically it would
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209739#comment-15209739
]
deepankar commented on HBASE-13819:
---
I agree with you but what I feel is in the ideal scenario the
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209736#comment-15209736
]
deepankar commented on HBASE-13819:
---
bq. What you think of Anoop's idea of the BB being allocated
[
https://issues.apache.org/jira/browse/HBASE-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15525:
--
Description:
After HBASE-13819 the system some times run out of direct memory whenever there
is some
deepankar created HBASE-15525:
-
Summary: Fix OutOfMemory that could occur when using
BoundedByteBufferPool during RPC bursts
Key: HBASE-15525
URL: https://issues.apache.org/jira/browse/HBASE-15525
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209425#comment-15209425
]
deepankar commented on HBASE-13819:
---
Attached image of the metric over time. we are running bucket
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-13819:
--
Attachment: q.png
> Make RPC layer CellBlock buffer a DirectByteBuffer
>
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209414#comment-15209414
]
deepankar commented on HBASE-13819:
---
bq. In description above though, talk is of Responder queue backed
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209409#comment-15209409
]
deepankar commented on HBASE-13819:
---
bq. Which Q we talking? The is config to put bounds on the call
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209401#comment-15209401
]
deepankar commented on HBASE-13819:
---
bq. Because we are not returning BB to the pool? The pool is
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208009#comment-15208009
]
deepankar commented on HBASE-13819:
---
What [~anoop.hbase] said is correct, in our case avg response
[
https://issues.apache.org/jira/browse/HBASE-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207822#comment-15207822
]
deepankar commented on HBASE-13819:
---
Hi,
We recently pulled this patch internally and are seeing some
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15207082#comment-15207082
]
deepankar commented on HBASE-15064:
---
Yeah I think this will fix this issue.
> BufferUnderflowException
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198794#comment-15198794
]
deepankar commented on HBASE-15064:
---
pressed add too early i mean like this
{code}
public
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198793#comment-15198793
]
deepankar commented on HBASE-15064:
---
What if we remove the equality in the if clause in the limit and
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar reopened HBASE-15064:
---
> BufferUnderflowException after last Cell fetched from an HFile Block served
> from L2 offheap cache
>
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198752#comment-15198752
]
deepankar commented on HBASE-15064:
---
Is there something wrong with my reasoning there ? or am i missing
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199100#comment-15199100
]
deepankar commented on HBASE-15064:
---
Yeah something like that which was what [~anoop.hbase] was
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198858#comment-15198858
]
deepankar commented on HBASE-15064:
---
No I was saying, when you have done mbb1.get() for 4 times and
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198821#comment-15198821
]
deepankar commented on HBASE-15064:
---
I think the test in your patch should fail Mbb.limit(12); because
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198751#comment-15198751
]
deepankar commented on HBASE-15064:
---
yeah I think that will work, but what about the other bug in
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198796#comment-15198796
]
deepankar commented on HBASE-15064:
---
Also the hasRemaining method [~anoop.hbase] suggested should also
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198473#comment-15198473
]
deepankar commented on HBASE-15064:
---
I am still seeing this exception on our servers, I think I found
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188500#comment-15188500
]
deepankar commented on HBASE-15437:
---
In that case should the values of queueTime, processingTime be
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188288#comment-15188288
]
deepankar commented on HBASE-15437:
---
ping [~stack]
> Response size calculated in RPCServer for warning
[
https://issues.apache.org/jira/browse/HBASE-15437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188285#comment-15188285
]
deepankar commented on HBASE-15437:
---
ping [~saint@gmail.com] [~anoopsamjohn] [~ram_krish]
>
deepankar created HBASE-15437:
-
Summary: Response size calculated in RPCServer for warning
tooLarge responses does count CellScanner payload
Key: HBASE-15437
URL: https://issues.apache.org/jira/browse/HBASE-15437
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15174292#comment-15174292
]
deepankar commented on HBASE-15362:
---
I was trying to set {{io.compression.codec.lzo.buffersize}}, the
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15362:
--
Attachment: HBASE-15362.patch
> Compression Algorithm does not respect config params from hbase-site
>
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15362:
--
Status: Patch Available (was: In Progress)
> Compression Algorithm does not respect config params
deepankar created HBASE-15362:
-
Summary: Compression Algorithm does not respect config params from
hbase-site
Key: HBASE-15362
URL: https://issues.apache.org/jira/browse/HBASE-15362
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-15362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-15362 started by deepankar.
-
> Compression Algorithm does not respect config params from hbase-site
>
deepankar created HBASE-15361:
-
Summary: Remove unnecessary or Document constraints on
BucketCache possible bucket sizes
Key: HBASE-15361
URL: https://issues.apache.org/jira/browse/HBASE-15361
Project:
[
https://issues.apache.org/jira/browse/HBASE-15361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172708#comment-15172708
]
deepankar commented on HBASE-15361:
---
I can put up a patch based on the direction community suggests
>
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110224#comment-15110224
]
deepankar commented on HBASE-15101:
---
It is on on branch-1 only. ( But I have ported other patches also
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106413#comment-15106413
]
deepankar commented on HBASE-15101:
---
I thought before HBASE-13082, when a compaction starts and before
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Attachment: HBASE-15101-v4.patch
> Leaked References to StoreFile.Reader after HBASE-13082
>
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108017#comment-15108017
]
deepankar commented on HBASE-15101:
---
Attached patch with close calls also.
> Leaked References to
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108013#comment-15108013
]
deepankar commented on HBASE-15101:
---
Should I add the close calls before return statement as I
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108036#comment-15108036
]
deepankar commented on HBASE-15101:
---
Adding the close did not help before, but I thought it should
1 - 100 of 156 matches
Mail list logo
