[jira] [Updated] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-23066: --- Release Note: The configuration 'hbase.rs.cacheblocksonwrite' was used to

[jira] [Comment Edited] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992767#comment-16992767 ] ramkrishna.s.vasudevan edited comment on HBASE-23066 at 12/10/19 5:52 PM:

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992767#comment-16992767 ] ramkrishna.s.vasudevan commented on HBASE-23066: [~jacob.leblanc] - Pushed this to

[jira] [Commented] (HBASE-23349) Reader lock on compacted store files preventing archival of compacted files

[ https://issues.apache.org/jira/browse/HBASE-23349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992326#comment-16992326 ] ramkrishna.s.vasudevan commented on HBASE-23349: There is no problem. Because the

[jira] [Commented] (HBASE-23349) Reader lock on compacted store files preventing archival of compacted files

[ https://issues.apache.org/jira/browse/HBASE-23349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989545#comment-16989545 ] ramkrishna.s.vasudevan commented on HBASE-23349: Sorry for being late here. Good

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988474#comment-16988474 ] ramkrishna.s.vasudevan commented on HBASE-23066: BTW - confirmed seeing the code that it

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988473#comment-16988473 ] ramkrishna.s.vasudevan commented on HBASE-23066: [~jacob.leblanc] Thanks for your

[jira] [Created] (HBASE-23350) Make compaction files cacheonWrite configurable based on threshold

ramkrishna.s.vasudevan created HBASE-23350: -- Summary: Make compaction files cacheonWrite configurable based on threshold Key: HBASE-23350 URL: https://issues.apache.org/jira/browse/HBASE-23350

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984157#comment-16984157 ] ramkrishna.s.vasudevan commented on HBASE-23066: [~jacob.leblanc] You want to do the

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984143#comment-16984143 ] ramkrishna.s.vasudevan commented on HBASE-23066: bq.On a side note, (Not related to this

[jira] [Comment Edited] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982284#comment-16982284 ] ramkrishna.s.vasudevan edited comment on HBASE-23066 at 11/26/19 9:27 AM:

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982284#comment-16982284 ] ramkrishna.s.vasudevan commented on HBASE-23066: [~jacob.leblanc] Is the patch still

[jira] [Commented] (HBASE-23279) Switch default block encoding to ROW_INDEX_V1

[ https://issues.apache.org/jira/browse/HBASE-23279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979010#comment-16979010 ] ramkrishna.s.vasudevan commented on HBASE-23279: [~vjasani] You can try enabling other

[jira] [Commented] (HBASE-23296) Support Bucket based L1 Cache

[ https://issues.apache.org/jira/browse/HBASE-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976452#comment-16976452 ] ramkrishna.s.vasudevan commented on HBASE-23296: Good one [~javaman_chen]. We tried for

[jira] [Assigned] (HBASE-23270) Inter-cluster replication is unaware destination peer cluster's RSGroup to push the WALEdits

[ https://issues.apache.org/jira/browse/HBASE-23270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-23270: -- Assignee: Pradeep > Inter-cluster replication is unaware destination

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953614#comment-16953614 ] ramkrishna.s.vasudevan commented on HBASE-23066: [~busbey] - you want to have a look at

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952549#comment-16952549 ] ramkrishna.s.vasudevan commented on HBASE-23066: You may have to add a clear release

[jira] [Commented] (HBASE-23107) Avoid temp byte array creation when doing cacheDataOnWrite

[ https://issues.apache.org/jira/browse/HBASE-23107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950971#comment-16950971 ] ramkrishna.s.vasudevan commented on HBASE-23107: Will have a look at this later today or

[jira] [Commented] (HBASE-22608) MVCC's writeEntry didn't complete and make MVCC stuck

[ https://issues.apache.org/jira/browse/HBASE-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950963#comment-16950963 ] ramkrishna.s.vasudevan commented on HBASE-22608: [~openinx] Are you working on this

[jira] [Commented] (HBASE-23143) Region Server Crash due to 2 cells out of order ( between 2 DELETEs)

[ https://issues.apache.org/jira/browse/HBASE-23143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949159#comment-16949159 ] ramkrishna.s.vasudevan commented on HBASE-23143: Reading the Cells that you have and the

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943319#comment-16943319 ] ramkrishna.s.vasudevan commented on HBASE-23066: [~jacob.leblanc] Can you create a PR

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941735#comment-16941735 ] ramkrishna.s.vasudevan commented on HBASE-23066: bq.As time goes on, HFile will grow

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941556#comment-16941556 ] ramkrishna.s.vasudevan commented on HBASE-23066: I think [~jacob.leblanc] says for

[jira] [Commented] (HBASE-11288) Splittable Meta

[ https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940773#comment-16940773 ] ramkrishna.s.vasudevan commented on HBASE-11288: Thanks for the write up. It gives the

[jira] [Commented] (HBASE-11288) Splittable Meta

[ https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937054#comment-16937054 ] ramkrishna.s.vasudevan commented on HBASE-11288: +1 to what [~stack] says. Thanks

[jira] [Commented] (HBASE-23066) Allow cache on write during compactions when prefetching is enabled

[ https://issues.apache.org/jira/browse/HBASE-23066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937032#comment-16937032 ] ramkrishna.s.vasudevan commented on HBASE-23066: On first glance patch looks good to me

[jira] [Commented] (HBASE-23035) Retain region to the last RegionServer make the failover slower

[ https://issues.apache.org/jira/browse/HBASE-23035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936390#comment-16936390 ] ramkrishna.s.vasudevan commented on HBASE-23035: So on restart you just want to leave

[jira] [Commented] (HBASE-23035) Retain region to the last RegionServer make the failover slower

[ https://issues.apache.org/jira/browse/HBASE-23035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931193#comment-16931193 ] ramkrishna.s.vasudevan commented on HBASE-23035: We were always doing a round robin

[jira] [Resolved] (HBASE-22929) MemStoreLAB ChunkCreator may memory leak

[ https://issues.apache.org/jira/browse/HBASE-22929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan resolved HBASE-22929. Fix Version/s: 2.1.6 2.2.1 2.3.0

[jira] [Assigned] (HBASE-22929) MemStoreLAB ChunkCreator may memory leak

[ https://issues.apache.org/jira/browse/HBASE-22929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-22929: -- Assignee: ramkrishna.s.vasudevan > MemStoreLAB ChunkCreator may

[jira] [Commented] (HBASE-23006) RSGroupBasedLoadBalancer should also try to place replicas for the same region to different region servers

[ https://issues.apache.org/jira/browse/HBASE-23006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928194#comment-16928194 ] ramkrishna.s.vasudevan commented on HBASE-23006: In many of the cases the LB was not

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924202#comment-16924202 ] ramkrishna.s.vasudevan commented on HBASE-22072: [~aoxiang] Oh I missed this. Just to

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16920637#comment-16920637 ] ramkrishna.s.vasudevan commented on HBASE-22072: [~aoxiang] Yes. Now it is either

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919269#comment-16919269 ] ramkrishna.s.vasudevan commented on HBASE-22072: [~aoxiang] The patch here has gone into

[jira] [Commented] (HBASE-22862) Region Server crash with: Added a key not lexically larger than previous

[ https://issues.apache.org/jira/browse/HBASE-22862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917394#comment-16917394 ] ramkrishna.s.vasudevan commented on HBASE-22862: [~openinx] That is true. Sorry for the

[jira] [Commented] (HBASE-22862) Region Server crash with: Added a key not lexically larger than previous

[ https://issues.apache.org/jira/browse/HBASE-22862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917385#comment-16917385 ] ramkrishna.s.vasudevan commented on HBASE-22862: bq. return (0xff & left.getTypeByte())

[jira] [Commented] (HBASE-22936) Close memStoreScanners in StoreScanner#updateReaders else memory leak

[ https://issues.apache.org/jira/browse/HBASE-22936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917382#comment-16917382 ] ramkrishna.s.vasudevan commented on HBASE-22936: If any one needs to give a patch I can

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917380#comment-16917380 ] ramkrishna.s.vasudevan commented on HBASE-22072: Thanks [~stack] for filing. It is

[jira] [Commented] (HBASE-22929) MemStoreLAB ChunkCreator may memory leak

[ https://issues.apache.org/jira/browse/HBASE-22929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916549#comment-16916549 ] ramkrishna.s.vasudevan commented on HBASE-22929: [~chenyechao] Are you seeing that the

[jira] [Commented] (HBASE-22802) Avoid temp ByteBuffer allocation in FileIOEngine#read

[ https://issues.apache.org/jira/browse/HBASE-22802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913967#comment-16913967 ] ramkrishna.s.vasudevan commented on HBASE-22802: [~javaman_chen] In your case the file

[jira] [Commented] (HBASE-21879) Read HFile's block to ByteBuffer directly instead of to byte for reducing young gc purpose

[ https://issues.apache.org/jira/browse/HBASE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1694#comment-1694 ] ramkrishna.s.vasudevan commented on HBASE-21879: OOO for personal reasons. No access to

[jira] [Updated] (HBASE-22670) JDK 11 and CellComparator

[ https://issues.apache.org/jira/browse/HBASE-22670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-22670: --- Labels: jdk11 (was: ) > JDK 11 and CellComparator >

[jira] [Commented] (HBASE-22670) JDK 11 and CellComparator

[ https://issues.apache.org/jira/browse/HBASE-22670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881909#comment-16881909 ] ramkrishna.s.vasudevan commented on HBASE-22670: Though we have the

[jira] [Created] (HBASE-22671) ByteBufferUtils#findCommonPrefix() can be safely changed to ArraysSupport#mismatch()

ramkrishna.s.vasudevan created HBASE-22671: -- Summary: ByteBufferUtils#findCommonPrefix() can be safely changed to ArraysSupport#mismatch() Key: HBASE-22671 URL:

[jira] [Created] (HBASE-22670) JDK 11 and CellComparator

ramkrishna.s.vasudevan created HBASE-22670: -- Summary: JDK 11 and CellComparator Key: HBASE-22670 URL: https://issues.apache.org/jira/browse/HBASE-22670 Project: HBase Issue Type:

[jira] [Commented] (HBASE-22608) MVCC's writeEntry didn't complete and make MVCC stuck

[ https://issues.apache.org/jira/browse/HBASE-22608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868280#comment-16868280 ] ramkrishna.s.vasudevan commented on HBASE-22608: Seems an size accounting issue with

[jira] [Created] (HBASE-22602) Allow storage policy to be set per column family in PE tool

ramkrishna.s.vasudevan created HBASE-22602: -- Summary: Allow storage policy to be set per column family in PE tool Key: HBASE-22602 URL: https://issues.apache.org/jira/browse/HBASE-22602

[jira] [Commented] (HBASE-22539) Potential WAL corruption due to Unsafe.copyMemory usage when DBB are in place

[ https://issues.apache.org/jira/browse/HBASE-22539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856391#comment-16856391 ] ramkrishna.s.vasudevan commented on HBASE-22539: [~wchevreuil] Have you verified that

[jira] [Commented] (HBASE-22532) There's still too much cpu wasting on validating checksum even if buffer.size=65KB

[ https://issues.apache.org/jira/browse/HBASE-22532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855300#comment-16855300 ] ramkrishna.s.vasudevan commented on HBASE-22532: Probably we should see the size of per

[jira] [Commented] (HBASE-22531) The HFileReaderImpl#shouldUseHeap return the incorrect true when disabled BlockCache

[ https://issues.apache.org/jira/browse/HBASE-22531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854469#comment-16854469 ] ramkrishna.s.vasudevan commented on HBASE-22531: Nice one. +1. > The

[jira] [Commented] (HBASE-22483) Maybe it's better to use 65KB as the default buffer size in ByteBuffAllocator

[ https://issues.apache.org/jira/browse/HBASE-22483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852789#comment-16852789 ] ramkrishna.s.vasudevan commented on HBASE-22483: Excellent results !! Seems QPS is more

[jira] [Commented] (HBASE-22422) Retain an ByteBuff with refCnt=0 when getBlock from LRUCache

[ https://issues.apache.org/jira/browse/HBASE-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849899#comment-16849899 ] ramkrishna.s.vasudevan commented on HBASE-22422: [~openinx] I just asked a question in

[jira] [Commented] (HBASE-22480) Get block from BlockCache once and return this block to BlockCache twice make ref count error.

[ https://issues.apache.org/jira/browse/HBASE-22480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849319#comment-16849319 ] ramkrishna.s.vasudevan commented on HBASE-22480: [~aoxiang] So here there is no negative

[jira] [Commented] (HBASE-22480) Get block from BlockCache once and return this block to BlockCache twice make ref count error.

[ https://issues.apache.org/jira/browse/HBASE-22480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849089#comment-16849089 ] ramkrishna.s.vasudevan commented on HBASE-22480: So here it means that the {code}

[jira] [Commented] (HBASE-22422) Retain an ByteBuff with refCnt=0 when getBlock from LRUCache

[ https://issues.apache.org/jira/browse/HBASE-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847259#comment-16847259 ] ramkrishna.s.vasudevan commented on HBASE-22422: bq.Understand now, it's a cnocurrent

[jira] [Updated] (HBASE-22448) Scan is slow for Multiple Column prefixes

[ https://issues.apache.org/jira/browse/HBASE-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-22448: --- Attachment: org.apache.hadoop.hbase.filter.TestSlowColumnPrefix-output.zip

[jira] [Comment Edited] (HBASE-22448) Scan is slow for Multiple Column prefixes

[ https://issues.apache.org/jira/browse/HBASE-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845781#comment-16845781 ] ramkrishna.s.vasudevan edited comment on HBASE-22448 at 5/22/19 11:22 AM:

[jira] [Commented] (HBASE-22448) Scan is slow for Multiple Column prefixes

[ https://issues.apache.org/jira/browse/HBASE-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845781#comment-16845781 ] ramkrishna.s.vasudevan commented on HBASE-22448: Attached the output with some sysouts.

[jira] [Commented] (HBASE-22448) Scan is slow for Multiple Column prefixes

[ https://issues.apache.org/jira/browse/HBASE-22448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845592#comment-16845592 ] ramkrishna.s.vasudevan commented on HBASE-22448: SEems so. Previously only the list of

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845506#comment-16845506 ] ramkrishna.s.vasudevan commented on HBASE-22072: [~lhofhansl] The specific problem here

[jira] [Commented] (HBASE-22433) Corrupt hfile data

[ https://issues.apache.org/jira/browse/HBASE-22433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843720#comment-16843720 ] ramkrishna.s.vasudevan commented on HBASE-22433: Is this some how related to

[jira] [Commented] (HBASE-22412) Improve the metrics in ByteBuffAllocator

[ https://issues.apache.org/jira/browse/HBASE-22412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843679#comment-16843679 ] ramkrishna.s.vasudevan commented on HBASE-22412: [~openinx] Patch looks good to me. So

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836257#comment-16836257 ] ramkrishna.s.vasudevan commented on HBASE-22072: Verified in branch-1 series. This issue

[jira] [Updated] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-22072: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.1.5

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835679#comment-16835679 ] ramkrishna.s.vasudevan commented on HBASE-22072: Pushed to all the branch-2 lines. Need

[jira] [Commented] (HBASE-21921) Notify users if the ByteBufAllocator is always allocating ByteBuffers from heap which means the increacing GC pressure

[ https://issues.apache.org/jira/browse/HBASE-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834396#comment-16834396 ] ramkrishna.s.vasudevan commented on HBASE-21921: Good one. > Notify users if the

[jira] [Commented] (HBASE-22090) The HFileBlock#CacheableDeserializer should pass ByteBuffAllocator to the newly created HFileBlock

[ https://issues.apache.org/jira/browse/HBASE-22090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826804#comment-16826804 ] ramkrishna.s.vasudevan commented on HBASE-22090: bq. private final ByteBuffAllocator

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821671#comment-16821671 ] ramkrishna.s.vasudevan commented on HBASE-22072: bq.Also in an earlier comment I have

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821670#comment-16821670 ] ramkrishna.s.vasudevan commented on HBASE-22072: bq.But the scanner is still not over.

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819979#comment-16819979 ] ramkrishna.s.vasudevan commented on HBASE-22072: bq.Is it possible if other thread,

[jira] [Assigned] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan reassigned HBASE-22072: -- Assignee: ramkrishna.s.vasudevan > High read/write intensive regions

[jira] [Updated] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-22072: --- Status: Patch Available (was: Open) BTW I created the patch with

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818898#comment-16818898 ] ramkrishna.s.vasudevan commented on HBASE-22072: Created a patch that now creates a

[jira] [Updated] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-22072: --- Attachment: HBASE-22072.HBASE-21879-v1.patch > High read/write intensive

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818669#comment-16818669 ] ramkrishna.s.vasudevan commented on HBASE-22072: Am able to reproduce this. Will upload

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815297#comment-16815297 ] ramkrishna.s.vasudevan commented on HBASE-22072: Lets see how to take this forward. Will

[jira] [Commented] (HBASE-21879) Read HFile's block to ByteBuffer directly instead of to byte for reducing young gc purpose

[ https://issues.apache.org/jira/browse/HBASE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808685#comment-16808685 ] ramkrishna.s.vasudevan commented on HBASE-21879: OOO for personal reasons. No access to

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808390#comment-16808390 ] ramkrishna.s.vasudevan commented on HBASE-22072: May be we should have a lock for

[jira] [Commented] (HBASE-22072) High read/write intensive regions may cause long crash recovery

[ https://issues.apache.org/jira/browse/HBASE-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806496#comment-16806496 ] ramkrishna.s.vasudevan commented on HBASE-22072: bq.updateReaders and further

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.x

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785918#comment-16785918 ] ramkrishna.s.vasudevan commented on HBASE-21874: Thanks for all the reviews and

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785285#comment-16785285 ] ramkrishna.s.vasudevan commented on HBASE-21874: The test failures are unrelated and

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Attachment: HBASE-21874_V6.patch > Bucket cache on Persistent memory >

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784692#comment-16784692 ] ramkrishna.s.vasudevan commented on HBASE-21874: bq.ExclusiveMemoryMmapIOEngine extends

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Status: Open (was: Patch Available) > Bucket cache on Persistent memory >

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Status: Patch Available (was: Open) > Bucket cache on Persistent memory >

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Attachment: HBASE-21874_V5.patch > Bucket cache on Persistent memory >

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Status: Patch Available (was: Open) Patch seems to be big now due to the

[jira] [Updated] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21874: --- Attachment: HBASE-21874_V4.patch > Bucket cache on Persistent memory >

[jira] [Updated] (HBASE-21981) MMaped bucket cache IOEngine does not work with persistence

[ https://issues.apache.org/jira/browse/HBASE-21981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21981: --- Summary: MMaped bucket cache IOEngine does not work with persistence (was:

[jira] [Created] (HBASE-21981) MMaped bucket cache IOEngines does not work with persistence

ramkrishna.s.vasudevan created HBASE-21981: -- Summary: MMaped bucket cache IOEngines does not work with persistence Key: HBASE-21981 URL: https://issues.apache.org/jira/browse/HBASE-21981

[jira] [Commented] (HBASE-21879) Read HFile's block to ByteBuffer directly instead of to byte for reducing young gc purpose

[ https://issues.apache.org/jira/browse/HBASE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774760#comment-16774760 ] ramkrishna.s.vasudevan commented on HBASE-21879: bq.And you can get a ByteBuffer from a

[jira] [Commented] (HBASE-21879) Read HFile's block to ByteBuffer directly instead of to byte for reducing young gc purpose

[ https://issues.apache.org/jira/browse/HBASE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774386#comment-16774386 ] ramkrishna.s.vasudevan commented on HBASE-21879: However if at all we need netty's ref

[jira] [Commented] (HBASE-21879) Read HFile's block to ByteBuffer directly instead of to byte for reducing young gc purpose

[ https://issues.apache.org/jira/browse/HBASE-21879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774380#comment-16774380 ] ramkrishna.s.vasudevan commented on HBASE-21879: Thanks for the ping here folks. From

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773976#comment-16773976 ] ramkrishna.s.vasudevan commented on HBASE-21874: bq.sysctl -w vm.max_map_count=13

[jira] [Commented] (HBASE-21916) Abstract an ByteBuffAllocator to allocate/free ByteBuffer in ByteBufferPool

[ https://issues.apache.org/jira/browse/HBASE-21916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772643#comment-16772643 ] ramkrishna.s.vasudevan commented on HBASE-21916: [~openinx] Sorry for the time taken

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771056#comment-16771056 ] ramkrishna.s.vasudevan commented on HBASE-21874: {quote}PmemIOEngine only overrides

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770101#comment-16770101 ] ramkrishna.s.vasudevan commented on HBASE-21874: bq.Thus, main goal of setting "Direct

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769964#comment-16769964 ] ramkrishna.s.vasudevan commented on HBASE-21874: bq. Can you point the exact place in

[jira] [Commented] (HBASE-21874) Bucket cache on Persistent memory

[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769598#comment-16769598 ] ramkrishna.s.vasudevan commented on HBASE-21874: {quote}Where are your going to keep

<    1   2   3   4   5   6   7   8   9   10   >