[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Status: Open (was: Patch Available) > Split of a region with replicas

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Status: Patch Available (was: Open) Updated the checkstyle comment in test

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Status: Open (was: Patch Available) > Split of a region with replicas

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Attachment: HBASE-20741_2.patch > Split of a region with replicas creates

[jira] [Commented] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591479#comment-16591479 ] ramkrishna.s.vasudevan commented on HBASE-20741: Pls check the RB link -

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Fix Version/s: 3.0.0 Affects Version/s: 3.0.0 Status:

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Attachment: HBASE-20741_1.patch > Split of a region with replicas creates

[jira] [Commented] (HBASE-21017) Revisit the expected states for open/close

[ https://issues.apache.org/jira/browse/HBASE-21017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591226#comment-16591226 ] ramkrishna.s.vasudevan commented on HBASE-21017: bq., we should not allow assigning a

[jira] [Created] (HBASE-21102) ServerCrashProcedure should select target server where no other replicas exist for the current region

ramkrishna.s.vasudevan created HBASE-21102: -- Summary: ServerCrashProcedure should select target server where no other replicas exist for the current region Key: HBASE-21102 URL:

[jira] [Updated] (HBASE-21102) ServerCrashProcedure should select target server where no other replicas exist for the current region

[ https://issues.apache.org/jira/browse/HBASE-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-21102: --- Affects Version/s: 3.0.0 Component/s: Region Assignment >

[jira] [Commented] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590088#comment-16590088 ] ramkrishna.s.vasudevan commented on HBASE-20741: Thanks all for the comments. I missed

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Attachment: HBASE-20741.patch > Split of a region with replicas creates all

[jira] [Commented] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551009#comment-16551009 ] ramkrishna.s.vasudevan commented on HBASE-20741: Initial patch. Just doing a round robin

[jira] [Commented] (HBASE-20875) MemStoreLABImp::copyIntoCell uses 7% CPU when writing

[ https://issues.apache.org/jira/browse/HBASE-20875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546016#comment-16546016 ] ramkrishna.s.vasudevan commented on HBASE-20875: In the jitviewer also noticed that in

[jira] [Commented] (HBASE-20875) MemStoreLABImp::copyIntoCell uses 7% CPU when writing

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

[jira] [Commented] (HBASE-20674) clean up short circuit read logic and docs

[ https://issues.apache.org/jira/browse/HBASE-20674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515352#comment-16515352 ] ramkrishna.s.vasudevan commented on HBASE-20674: For SCR

[jira] [Updated] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

[ https://issues.apache.org/jira/browse/HBASE-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20741: --- Component/s: read replicas > Split of a region with replicas creates all

[jira] [Created] (HBASE-20741) Split of a region with replicas creates all daughter regions and its replica in same server

ramkrishna.s.vasudevan created HBASE-20741: -- Summary: Split of a region with replicas creates all daughter regions and its replica in same server Key: HBASE-20741 URL:

[jira] [Commented] (HBASE-20628) SegmentScanner does over-comparing when one flushing

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

[jira] [Commented] (HBASE-20601) Add multiPut support and other miscellaneous to PE

[ https://issues.apache.org/jira/browse/HBASE-20601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482191#comment-16482191 ] ramkrishna.s.vasudevan commented on HBASE-20601: [~allan163] Good to see client

[jira] [Commented] (HBASE-20564) Tighter ByteBufferKeyValue Cell Comparator

[ https://issues.apache.org/jira/browse/HBASE-20564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471636#comment-16471636 ] ramkrishna.s.vasudevan commented on HBASE-20564: As per the patch some values are taken

[jira] [Commented] (HBASE-20483) [PERFORMANCE] Flushing is 2x slower in hbase2.

[ https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468334#comment-16468334 ] ramkrishna.s.vasudevan commented on HBASE-20483: Is the above CPU usage after the PE

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Resolution: Fixed Fix Version/s: 1.4.5 1.2.7

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Attachment: HBASE-20523_branch-1.patch > PE tool should support configuring

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Attachment: HBASE-20523_branch-1.2.patch > PE tool should support

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Attachment: HBASE-20523_branch-1.4.patch > PE tool should support

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Hadoop Flags: Reviewed Status: Patch Available (was: Open)

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Attachment: HBASE-20523_1.patch > PE tool should support configuring client

[jira] [Commented] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463799#comment-16463799 ] ramkrishna.s.vasudevan commented on HBASE-20523: I followed the YCSB naming here where it

[jira] [Commented] (HBASE-20520) Failed effort upping default HDFS blocksize, hbase.regionserver.hlog.blocksize

[ https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462036#comment-16462036 ] ramkrishna.s.vasudevan commented on HBASE-20520: bq.Example please ramkrishna.s.vasudevan

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Attachment: HBASE-20523.patch > PE tool should support configuring client

[jira] [Commented] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462000#comment-16462000 ] ramkrishna.s.vasudevan commented on HBASE-20523: Patch based on branch-2. Tested the

[jira] [Updated] (HBASE-20523) PE tool should support configuring client side buffering sizes

[ https://issues.apache.org/jira/browse/HBASE-20523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20523: --- Priority: Minor (was: Major) > PE tool should support configuring client

[jira] [Created] (HBASE-20523) PE tool should support configuring client side buffering sizes

ramkrishna.s.vasudevan created HBASE-20523: -- Summary: PE tool should support configuring client side buffering sizes Key: HBASE-20523 URL: https://issues.apache.org/jira/browse/HBASE-20523

[jira] [Commented] (HBASE-20520) Failed effort upping default HDFS blocksize, hbase.regionserver.hlog.blocksize

[ https://issues.apache.org/jira/browse/HBASE-20520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16461427#comment-16461427 ] ramkrishna.s.vasudevan commented on HBASE-20520: In the logs I noticed that WAL A gets

[jira] [Commented] (HBASE-20414) TestLockProcedure#testMultipleLocks may fail on slow machine

[ https://issues.apache.org/jira/browse/HBASE-20414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460512#comment-16460512 ] ramkrishna.s.vasudevan commented on HBASE-20414: Looks good to me. I verified the test

[jira] [Created] (HBASE-20511) Set the scan's read type on the subsequent scan requests

ramkrishna.s.vasudevan created HBASE-20511: -- Summary: Set the scan's read type on the subsequent scan requests Key: HBASE-20511 URL: https://issues.apache.org/jira/browse/HBASE-20511 Project:

[jira] [Commented] (HBASE-20457) Return immediately for a scan rpc call when we want to switch from pread to stream

[ https://issues.apache.org/jira/browse/HBASE-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459474#comment-16459474 ] ramkrishna.s.vasudevan commented on HBASE-20457: Tested the patch. The normal full table

[jira] [Commented] (HBASE-20457) Return immediately for a scan rpc call when we want to switch from pread to stream

[ https://issues.apache.org/jira/browse/HBASE-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458328#comment-16458328 ] ramkrishna.s.vasudevan commented on HBASE-20457: Patch LGTM. Will test it in a small

[jira] [Commented] (HBASE-20457) Return immediately for a scan rpc call when we want to switch from pread to stream

[ https://issues.apache.org/jira/browse/HBASE-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458034#comment-16458034 ] ramkrishna.s.vasudevan commented on HBASE-20457: Thanks [~Apache9]. I will take a look at

[jira] [Commented] (HBASE-20457) Return immediately for a scan rpc call when we want to switch from pread to stream

[ https://issues.apache.org/jira/browse/HBASE-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449676#comment-16449676 ] ramkrishna.s.vasudevan commented on HBASE-20457: If not I can take this up. > Return

[jira] [Commented] (HBASE-20457) Return immediately for a scan rpc call when we want to switch from pread to stream

[ https://issues.apache.org/jira/browse/HBASE-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16449542#comment-16449542 ] ramkrishna.s.vasudevan commented on HBASE-20457: [~Apache9] Have you started working on

[jira] [Commented] (HBASE-20414) TestLockProcedure#testMultipleLocks may fail on slow machine

[ https://issues.apache.org/jira/browse/HBASE-20414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447580#comment-16447580 ] ramkrishna.s.vasudevan commented on HBASE-20414: I haven't checked the test case in

[jira] [Commented] (HBASE-19024) Configurable default durability for synchronous WAL

[ https://issues.apache.org/jira/browse/HBASE-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447560#comment-16447560 ] ramkrishna.s.vasudevan commented on HBASE-19024: So one question regarding the

[jira] [Commented] (HBASE-20457) Return immediately for a scan rpc call when we want to switch from pread to stream

[ https://issues.apache.org/jira/browse/HBASE-20457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16445329#comment-16445329 ] ramkrishna.s.vasudevan commented on HBASE-20457: One more thing to consider.  One case

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443856#comment-16443856 ] ramkrishna.s.vasudevan commented on HBASE-20188: Exactly. this could happen in other

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443760#comment-16443760 ] ramkrishna.s.vasudevan commented on HBASE-20188: [~Apache9] I did get some more info on

[jira] [Comment Edited] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442439#comment-16442439 ] ramkrishna.s.vasudevan edited comment on HBASE-20188 at 4/18/18 12:56 PM:

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442450#comment-16442450 ] ramkrishna.s.vasudevan commented on HBASE-20188: bq.So this is a bug we need to fix, not

[jira] [Comment Edited] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442439#comment-16442439 ] ramkrishna.s.vasudevan edited comment on HBASE-20188 at 4/18/18 12:53 PM:

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442439#comment-16442439 ] ramkrishna.s.vasudevan commented on HBASE-20188: I am not before system now.  For 2.0

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442258#comment-16442258 ] ramkrishna.s.vasudevan commented on HBASE-20188: I did that setMaxResultSize(2MB). It did

[jira] [Comment Edited] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442213#comment-16442213 ] ramkrishna.s.vasudevan edited comment on HBASE-20188 at 4/18/18 10:03 AM:

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442213#comment-16442213 ] ramkrishna.s.vasudevan commented on HBASE-20188: In this case there is no offheap cache.

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442184#comment-16442184 ] ramkrishna.s.vasudevan commented on HBASE-20188: Just noting down based on offline

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16440409#comment-16440409 ] ramkrishna.s.vasudevan commented on HBASE-19893: LGTM. Since this patch solves

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433458#comment-16433458 ] ramkrishna.s.vasudevan commented on HBASE-20188: bq.If it is a long scan then we will

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426488#comment-16426488 ] ramkrishna.s.vasudevan commented on HBASE-20188: The latest results with 8G cache are

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424993#comment-16424993 ] ramkrishna.s.vasudevan commented on HBASE-20188: What was the config that was missing for

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423788#comment-16423788 ] ramkrishna.s.vasudevan commented on HBASE-20188: The previous results were not apple to

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423585#comment-16423585 ] ramkrishna.s.vasudevan commented on HBASE-20188: I just reran the experiment with loading

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423581#comment-16423581 ] ramkrishna.s.vasudevan commented on HBASE-20188: bq.None really. Tried with data cached

[jira] [Commented] (HBASE-20259) hbase.systemtables.compacting.memstore.type=NONE does not do as expected

[ https://issues.apache.org/jira/browse/HBASE-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421949#comment-16421949 ] ramkrishna.s.vasudevan commented on HBASE-20259: [~saint@gmail.com] I think you need

[jira] [Updated] (HBASE-20197) Review of ByteBufferWriterOutputStream.java

[ https://issues.apache.org/jira/browse/HBASE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20197: --- Resolution: Fixed Fix Version/s: 2.1.0 3.0.0

[jira] [Comment Edited] (HBASE-20197) Review of ByteBufferWriterOutputStream.java

[ https://issues.apache.org/jira/browse/HBASE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420222#comment-16420222 ] ramkrishna.s.vasudevan edited comment on HBASE-20197 at 3/30/18 6:57 AM:

[jira] [Commented] (HBASE-20197) Review of ByteBufferWriterOutputStream.java

[ https://issues.apache.org/jira/browse/HBASE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420222#comment-16420222 ] ramkrishna.s.vasudevan commented on HBASE-20197: [~belugabehr] Thanks for the patch.

[jira] [Commented] (HBASE-20259) hbase.systemtables.compacting.memstore.type=NONE does not do as expected

[ https://issues.apache.org/jira/browse/HBASE-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420219#comment-16420219 ] ramkrishna.s.vasudevan commented on HBASE-20259: This config is only for system tables

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418822#comment-16418822 ] ramkrishna.s.vasudevan commented on HBASE-20188: In other tests where we tried R + W

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418812#comment-16418812 ] ramkrishna.s.vasudevan commented on HBASE-20188: I just tried loading 50G with 100

[jira] [Commented] (HBASE-20003) WALLess HBase on Persistent Memory

[ https://issues.apache.org/jira/browse/HBASE-20003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418502#comment-16418502 ] ramkrishna.s.vasudevan commented on HBASE-20003: bq.And also, in the first version, I

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418486#comment-16418486 ] ramkrishna.s.vasudevan commented on HBASE-20188: Also pure read workload should not be

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418437#comment-16418437 ] ramkrishna.s.vasudevan commented on HBASE-20188: [~saint@gmail.com] What is the

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409869#comment-16409869 ] ramkrishna.s.vasudevan commented on HBASE-20188: [~stack] You can better set the

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404418#comment-16404418 ] ramkrishna.s.vasudevan commented on HBASE-20188: bq.I dont think here the issue is perf

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404406#comment-16404406 ] ramkrishna.s.vasudevan commented on HBASE-20188: With this load, lets try with Default

[jira] [Commented] (HBASE-20197) Review of ByteBufferWriterOutputStream.java

[ https://issues.apache.org/jira/browse/HBASE-20197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404399#comment-16404399 ] ramkrishna.s.vasudevan commented on HBASE-20197: the 8K or 4K change I don have an

[jira] [Commented] (HBASE-20090) Properly handle Preconditions check failure in MemStoreFlusher$FlushHandler.run

[ https://issues.apache.org/jira/browse/HBASE-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16404392#comment-16404392 ] ramkrishna.s.vasudevan commented on HBASE-20090: +1 > Properly handle Preconditions

[jira] [Commented] (HBASE-20213) [LOGGING] Aligning formatting and logging less (compactions, in-memory compactions)

[ https://issues.apache.org/jira/browse/HBASE-20213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401478#comment-16401478 ] ramkrishna.s.vasudevan commented on HBASE-20213: +1 on these changes. I think since you

[jira] [Commented] (HBASE-20211) ReadOnlyBufferException In UnsafeAccess

[ https://issues.apache.org/jira/browse/HBASE-20211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401474#comment-16401474 ] ramkrishna.s.vasudevan commented on HBASE-20211: Thanks for the analysis. I just saw the

[jira] [Commented] (HBASE-20090) Properly handle Preconditions check failure in MemStoreFlusher$FlushHandler.run

[ https://issues.apache.org/jira/browse/HBASE-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398881#comment-16398881 ] ramkrishna.s.vasudevan commented on HBASE-20090: +1. Thanks [~yuzhih...@gmail.com] for

[jira] [Commented] (HBASE-20078) MultiByteBuff : bug in reading primitives when individual buffers are too small

[ https://issues.apache.org/jira/browse/HBASE-20078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398137#comment-16398137 ] ramkrishna.s.vasudevan commented on HBASE-20078: Just see if the patch has done the same

[jira] [Commented] (HBASE-20188) [TESTING] Performance

[ https://issues.apache.org/jira/browse/HBASE-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398135#comment-16398135 ] ramkrishna.s.vasudevan commented on HBASE-20188: I can help out with the AsyncWAL testing

[jira] [Commented] (HBASE-20141) Fix TooManyFiles exception when RefreshingChannels in FileIOEngine

[ https://issues.apache.org/jira/browse/HBASE-20141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398112#comment-16398112 ] ramkrishna.s.vasudevan commented on HBASE-20141: +1 > Fix TooManyFiles exception when

[jira] [Commented] (HBASE-17528) Remove the Scan.ReadType flag introduced in HBASE-17045

[ https://issues.apache.org/jira/browse/HBASE-17528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398110#comment-16398110 ] ramkrishna.s.vasudevan commented on HBASE-17528: Atleast for now as per the existing code

[jira] [Commented] (HBASE-20090) Properly handle Preconditions check failure in MemStoreFlusher$FlushHandler.run

[ https://issues.apache.org/jira/browse/HBASE-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396552#comment-16396552 ] ramkrishna.s.vasudevan commented on HBASE-20090: I like Ted's patch may be in case where

[jira] [Commented] (HBASE-20045) When running compaction, cache recent blocks.

[ https://issues.apache.org/jira/browse/HBASE-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394811#comment-16394811 ] ramkrishna.s.vasudevan commented on HBASE-20045: bq. I see the argument above about not

[jira] [Commented] (HBASE-20045) When running compaction, cache recent blocks.

[ https://issues.apache.org/jira/browse/HBASE-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389393#comment-16389393 ] ramkrishna.s.vasudevan commented on HBASE-20045: Yes makes sense to me also. > When

[jira] [Commented] (HBASE-20045) When running compaction, cache recent blocks.

[ https://issues.apache.org/jira/browse/HBASE-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389055#comment-16389055 ] ramkrishna.s.vasudevan commented on HBASE-20045: Ideally when cache on write is enabled

[jira] [Commented] (HBASE-20090) Properly handle Preconditions check failure in MemStoreFlusher$FlushHandler.run

[ https://issues.apache.org/jira/browse/HBASE-20090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387313#comment-16387313 ] ramkrishna.s.vasudevan commented on HBASE-20090: I think the case here is valid. As

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385911#comment-16385911 ] ramkrishna.s.vasudevan commented on HBASE-19893: bq.As restore_snapshot is done offline,

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385671#comment-16385671 ] ramkrishna.s.vasudevan commented on HBASE-19893: Few questions first {code}

[jira] [Commented] (HBASE-19863) java.lang.IllegalStateException: isDelete failed when SingleColumnValueFilter is used

[ https://issues.apache.org/jira/browse/HBASE-19863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378031#comment-16378031 ] ramkrishna.s.vasudevan commented on HBASE-19863: LGTM. Just a question {code} public

[jira] [Commented] (HBASE-20086) PE randomSeekScan fails with ClassNotFoundException

[ https://issues.apache.org/jira/browse/HBASE-20086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378029#comment-16378029 ] ramkrishna.s.vasudevan commented on HBASE-20086: [~yuzhih...@gmail.com] So this change

[jira] [Commented] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

[ https://issues.apache.org/jira/browse/HBASE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377179#comment-16377179 ] ramkrishna.s.vasudevan commented on HBASE-20036: This is what I committed. Just for

[jira] [Updated] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

[ https://issues.apache.org/jira/browse/HBASE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20036: --- Attachment: HBASE-20036_1.patch > TestAvoidCellReferencesIntoShippedBlocks

[jira] [Updated] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

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

[jira] [Commented] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

[ https://issues.apache.org/jira/browse/HBASE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376489#comment-16376489 ] ramkrishna.s.vasudevan commented on HBASE-20036: bq.Seems the assert check is useless as

[jira] [Updated] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

[ https://issues.apache.org/jira/browse/HBASE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20036: --- Assignee: ramkrishna.s.vasudevan Status: Patch Available (was: Open)

[jira] [Updated] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

[ https://issues.apache.org/jira/browse/HBASE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-20036: --- Attachment: HBASE-20036.patch > TestAvoidCellReferencesIntoShippedBlocks

[jira] [Commented] (HBASE-20036) TestAvoidCellReferencesIntoShippedBlocks timed out

[ https://issues.apache.org/jira/browse/HBASE-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376468#comment-16376468 ] ramkrishna.s.vasudevan commented on HBASE-20036: The reason for the failure was that the

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