deepankar created HBASE-10645:
-
Summary: Fix wrapping of Requests Counts Regionserver level
metrics
Key: HBASE-10645
URL: https://issues.apache.org/jira/browse/HBASE-10645
Project: HBase
Issue
[
https://issues.apache.org/jira/browse/HBASE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-10645:
--
Description: For aggregating the metrics from all of its regions
HRegionServer is using int, while
[
https://issues.apache.org/jira/browse/HBASE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-10645:
--
Attachment: HBASE_10645-0.94.15.patch
Fix wrapping of Requests Counts Regionserver level metrics
[
https://issues.apache.org/jira/browse/HBASE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13916596#comment-13916596
]
deepankar commented on HBASE-10645:
---
patch attached
Fix wrapping of Requests Counts
deepankar created HBASE-10811:
-
Summary: StoreFile StartKey not included in Bloom Filter Meta
Key: HBASE-10811
URL: https://issues.apache.org/jira/browse/HBASE-10811
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-10811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar resolved HBASE-10811.
---
Resolution: Duplicate
StoreFile StartKey not included in Bloom Filter Meta
[
https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012085#comment-14012085
]
deepankar commented on HBASE-8369:
--
In the patch that is merged in the trunk
[
https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012422#comment-14012422
]
deepankar commented on HBASE-8369:
--
Sorry forgot to mention the class in the above
[
https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012769#comment-14012769
]
deepankar commented on HBASE-8369:
--
Sorry for the confusion, in my comment I meant that
[
https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013089#comment-14013089
]
deepankar commented on HBASE-8369:
--
will create a jira and upload a patch
MapReduce
[
https://issues.apache.org/jira/browse/HBASE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14021478#comment-14021478
]
deepankar commented on HBASE-10645:
---
It was 0.94 specific, this issue was not there as
[
https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028522#comment-14028522
]
deepankar commented on HBASE-8369:
--
sorry did not create yet, but I am working on the
deepankar created HBASE-11335:
-
Summary: Fix the TABLE_DIR param in TableSnapshotInputFormat
Key: HBASE-11335
URL: https://issues.apache.org/jira/browse/HBASE-11335
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-11335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-11335:
--
Attachment: HBASE_11335-trunk-v1.patch
HBASE_11335-0.96-v1.patch
Fix the TABLE_DIR
[
https://issues.apache.org/jira/browse/HBASE-11335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028616#comment-14028616
]
deepankar commented on HBASE-11335:
---
patches are attached, the patch for trunk and 0.98
[
https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028620#comment-14028620
]
deepankar commented on HBASE-8369:
--
created the jira HBASE-11335 and attached the patches
[
https://issues.apache.org/jira/browse/HBASE-11335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047902#comment-14047902
]
deepankar commented on HBASE-11335:
---
ping [~enis], Can you take a look, we want to put
[
https://issues.apache.org/jira/browse/HBASE-11335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048232#comment-14048232
]
deepankar commented on HBASE-11335:
---
Thanks for your help
Fix the TABLE_DIR param in
deepankar created HBASE-11484:
-
Summary: Provide a way in TableSnapshotInputFormat, not to restore
the regions to a path for running MR every time, rather reuse a already
restored path
Key: HBASE-11484
URL:
[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056598#comment-14056598
]
deepankar commented on HBASE-11484:
---
ping [~enis]
Provide a way in
[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056646#comment-14056646
]
deepankar commented on HBASE-11484:
---
Thanks for the suggestions.Yes, I know Restore is
[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-11484:
--
Description:
We are trying to back a Hive Table by the Map Reduce over snapshots and we
don't want
[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056812#comment-14056812
]
deepankar commented on HBASE-11484:
---
[~mbertozzi] Are you suggesting to remove this
[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14057805#comment-14057805
]
deepankar commented on HBASE-11484:
---
There are no cleanup hooks, I don't think the job
[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14057809#comment-14057809
]
deepankar commented on HBASE-11484:
---
Also in the case of WAL-based flush-less snapshots
[
https://issues.apache.org/jira/browse/HBASE-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-11789:
--
Attachment: HBASE-11789-0.94.patch
Attaching the patch we used for our internal branch
[
https://issues.apache.org/jira/browse/HBASE-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-11789:
--
Attachment: (was: HBASE-11789-0.94.patch)
LoadIncrementalHFiles is not picking up the -D option
[
https://issues.apache.org/jira/browse/HBASE-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-11789:
--
Attachment: HBASE-11789-0.94-v1.patch
There was small bug in the previous one, so attaching the fixed
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15080717#comment-15080717
]
deepankar commented on HBASE-15064:
---
Pinging [~ishanc] he can add anything I miss.
Our use case was
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15080749#comment-15080749
]
deepankar commented on HBASE-15064:
---
I have not seen this error again on a new machine on which I have
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15080729#comment-15080729
]
deepankar commented on HBASE-15064:
---
Hmm, that might be the reason why there was not that much decrease
[
https://issues.apache.org/jira/browse/HBASE-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076467#comment-15076467
]
deepankar commented on HBASE-15064:
---
Just also noticed that the experiment node also had hardware
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076394#comment-15076394
]
deepankar commented on HBASE-15063:
---
Ah ha, missed the rewind() call thanks for the clarification. Not
deepankar created HBASE-15064:
-
Summary: Possbile Bug in MultiByteBuffer
Key: HBASE-15064
URL: https://issues.apache.org/jira/browse/HBASE-15064
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Attachment: HBASE-15063.patch
> Bug(s) in MultiByteBuf
> --
>
>
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Attachment: (was: HBASE-15063.patch)
> Bug(s) in MultiByteBuf
> --
>
>
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Assignee: deepankar
Status: Patch Available (was: Open)
> Bug(s) in MultiByteBuf
>
deepankar created HBASE-15063:
-
Summary: Bug(s) in MultiByteBuf
Key: HBASE-15063
URL: https://issues.apache.org/jira/browse/HBASE-15063
Project: HBase
Issue Type: Bug
Components: io,
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Status: Open (was: Patch Available)
> Bug(s) in MultiByteBuf
> --
>
>
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Attachment: HBASE-15063-v1.patch
> Bug(s) in MultiByteBuf
> --
>
>
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Status: Patch Available (was: Open)
> Bug(s) in MultiByteBuf
> --
>
>
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076283#comment-15076283
]
deepankar commented on HBASE-15063:
---
between my preference is that we should go with 1 where do not use
[
https://issues.apache.org/jira/browse/HBASE-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15063:
--
Attachment: HBASE-15063-v2.patch
> Bug(s) in MultiByteBuf
> --
>
>
[
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-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15102559#comment-15102559
]
deepankar commented on HBASE-15101:
---
Ah sorry, fixed it
> Leaked References to StoreFile.Reader after
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Attachment: HBASE-15101-v3.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=15102569#comment-15102569
]
deepankar commented on HBASE-15101:
---
In StoreScanner, can the close(false) not being called lead to
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15097147#comment-15097147
]
deepankar commented on HBASE-15101:
---
I can add a basic unit test to check whether dummy scanners are
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Summary: Leaked References to StoreFile.Reader after HBASE-13082 (was:
Leak References to
deepankar created HBASE-15101:
-
Summary: Leak References to StoreFile.Reader after HBASE-13082
Key: HBASE-15101
URL: https://issues.apache.org/jira/browse/HBASE-15101
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Status: Patch Available (was: Open)
> Leaked References to StoreFile.Reader after HBASE-13082
>
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Attachment: HBASE-15101.patch
> Leaked References to StoreFile.Reader after HBASE-13082
>
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Attachment: HBASE-15101-v2.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=15098566#comment-15098566
]
deepankar commented on HBASE-15101:
---
I havent backported HBASE-15027, will backport it now. With just
[
https://issues.apache.org/jira/browse/HBASE-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
deepankar updated HBASE-15101:
--
Attachment: HBASE-15101-v1.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=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:comment-tabpanel=15098560#comment-15098560
]
deepankar commented on HBASE-15101:
---
Done.
> 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=15098603#comment-15098603
]
deepankar commented on HBASE-15101:
---
Should we also finalize the files when a region is closed (may be
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:
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
>
[
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
[
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-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-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: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
[
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-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]
>
[
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=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=15198821#comment-15198821
]
deepankar commented on HBASE-15064:
---
I think the test in your patch should fail Mbb.limit(12); because
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-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-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=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-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-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-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-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-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-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-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=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=15207082#comment-15207082
]
deepankar commented on HBASE-15064:
---
Yeah I think this will fix this issue.
> BufferUnderflowException
[
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=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=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=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=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=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-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=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-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
1 - 100 of 156 matches
Mail list logo
