[jira] [Commented] (HBASE-22457) Harden the HBase HFile reader reference counting

[ https://issues.apache.org/jira/browse/HBASE-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846161#comment-16846161 ] Lars Hofhansl commented on HBASE-22457: --- Oh, it's a hack for sure and, as you point out, might

[jira] [Commented] (HBASE-22457) Harden the HBase HFile reader reference counting

[ https://issues.apache.org/jira/browse/HBASE-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846075#comment-16846075 ] Lars Hofhansl commented on HBASE-22457: --- One idea is: Are there any "safepoints"? I.e. points

[jira] [Updated] (HBASE-22457) Harden the HBase HFile reader reference counting

[ https://issues.apache.org/jira/browse/HBASE-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-22457: -- Summary: Harden the HBase HFile reader reference counting (was: Harden rhe HBase HFile

[jira] [Created] (HBASE-22457) Harden rhe HBase HFile reader reference counting

Lars Hofhansl created HBASE-22457: - Summary: Harden rhe HBase HFile reader reference counting Key: HBASE-22457 URL: https://issues.apache.org/jira/browse/HBASE-22457 Project: HBase Issue

[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=16846057#comment-16846057 ] Lars Hofhansl commented on HBASE-22072: --- Lemme file a separate "Discussion" issue. > High

[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=16845085#comment-16845085 ] Lars Hofhansl commented on HBASE-22072: --- > Verified in branch-1 series. This issue does not exist

[jira] [Commented] (HBASE-22385) Consider "programmatic" HFiles

[ https://issues.apache.org/jira/browse/HBASE-22385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836057#comment-16836057 ] Lars Hofhansl commented on HBASE-22385: --- In theory yes, but it would not be the goal, nor would

[jira] [Updated] (HBASE-22385) Consider "programmatic" HFiles

[ https://issues.apache.org/jira/browse/HBASE-22385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-22385: -- Description: For various use cases (among others there is mass deletes) it would be great if

[jira] [Updated] (HBASE-22385) Consider "programmatic" HFiles

[ https://issues.apache.org/jira/browse/HBASE-22385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-22385: -- Description: For various use cases (among others there is mass deletes) it would be great if

[jira] [Commented] (HBASE-22385) Consider "programmatic" HFiles

[ https://issues.apache.org/jira/browse/HBASE-22385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835763#comment-16835763 ] Lars Hofhansl commented on HBASE-22385: --- [~jisaac], what we chatted about. > Consider

[jira] [Created] (HBASE-22385) Consider "programmatic" HFiles

Lars Hofhansl created HBASE-22385: - Summary: Consider "programmatic" HFiles Key: HBASE-22385 URL: https://issues.apache.org/jira/browse/HBASE-22385 Project: HBase Issue Type: Brainstorming

[jira] [Updated] (HBASE-11811) Use binary search for seeking into a block

[ https://issues.apache.org/jira/browse/HBASE-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-11811: -- Resolution: Implemented Status: Resolved (was: Patch Available) This has been

[jira] [Commented] (HBASE-17884) Backport HBASE-16217 to branch-1

[ https://issues.apache.org/jira/browse/HBASE-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826655#comment-16826655 ] Lars Hofhansl commented on HBASE-17884: --- This is probably another case where Phoenix reaches too

[jira] [Comment Edited] (HBASE-17884) Backport HBASE-16217 to branch-1

[ https://issues.apache.org/jira/browse/HBASE-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826651#comment-16826651 ] Lars Hofhansl edited comment on HBASE-17884 at 4/26/19 5:25 AM: Locally

[jira] [Commented] (HBASE-17884) Backport HBASE-16217 to branch-1

[ https://issues.apache.org/jira/browse/HBASE-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826651#comment-16826651 ] Lars Hofhansl commented on HBASE-17884: --- Locally reverted for now. This is for Phoenix which

[jira] [Commented] (HBASE-17884) Backport HBASE-16217 to branch-1

[ https://issues.apache.org/jira/browse/HBASE-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826645#comment-16826645 ] Lars Hofhansl commented on HBASE-17884: --- Does this break binary compatability?! {code:java}

[jira] [Commented] (HBASE-22235) OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors

[ https://issues.apache.org/jira/browse/HBASE-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819480#comment-16819480 ] Lars Hofhansl commented on HBASE-22235: --- +1 > OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not

[jira] [Comment Edited] (HBASE-22235) OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors

[ https://issues.apache.org/jira/browse/HBASE-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819389#comment-16819389 ] Lars Hofhansl edited comment on HBASE-22235 at 4/16/19 6:42 PM: The

[jira] [Commented] (HBASE-22235) OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors

[ https://issues.apache.org/jira/browse/HBASE-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16819389#comment-16819389 ] Lars Hofhansl commented on HBASE-22235: --- The constants need to be the public in OperationStatus.

[jira] [Commented] (HBASE-22235) OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors

[ https://issues.apache.org/jira/browse/HBASE-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817220#comment-16817220 ] Lars Hofhansl commented on HBASE-22235: --- I found a different (and better) way to solve TEPHRA-299,

[jira] [Updated] (HBASE-22235) OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors

[ https://issues.apache.org/jira/browse/HBASE-22235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-22235: -- Description: preBatchMutate is useless for some operation due to this. See also TEPHRA-299.

[jira] [Created] (HBASE-22235) OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors

Lars Hofhansl created HBASE-22235: - Summary: OperationStatus.{SUCCESS|FAILURE|NOT_RUN} are not visible to 3rd party coprocessors Key: HBASE-22235 URL: https://issues.apache.org/jira/browse/HBASE-22235

[jira] [Commented] (HBASE-22057) Impose upper-bound on size of ZK ops sent in a single multi()

[ https://issues.apache.org/jira/browse/HBASE-22057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815821#comment-16815821 ] Lars Hofhansl commented on HBASE-22057: --- As long as "real" multi calls are still guaranteed to be

[jira] [Commented] (HBASE-20724) Sometimes some compacted storefiles are still opened after region failover

[ https://issues.apache.org/jira/browse/HBASE-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775753#comment-16775753 ] Lars Hofhansl commented on HBASE-20724: --- [~zghaobac] thanks for taking this on. Can you explain

[jira] [Updated] (HBASE-21856) Consider Causal Replication Ordering

[ https://issues.apache.org/jira/browse/HBASE-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21856: -- Summary: Consider Causal Replication Ordering (was: Consider Causal Replication) > Consider

[jira] [Updated] (HBASE-21856) Consider Causal Replication

[ https://issues.apache.org/jira/browse/HBASE-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21856: -- Description: We've had various efforts to improve the ordering guarantees for HBase

[jira] [Updated] (HBASE-21856) Consider Causal Replication

[ https://issues.apache.org/jira/browse/HBASE-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21856: -- Description: We've had various efforts to improve the ordering guarantees for HBase, most

[jira] [Updated] (HBASE-21856) Consider Causal Replication

[ https://issues.apache.org/jira/browse/HBASE-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21856: -- Description: We've had various efforts to improve the ordering guarantees for HBase

[jira] [Updated] (HBASE-21856) Consider Causal Replication

[ https://issues.apache.org/jira/browse/HBASE-21856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21856: -- Description: We've had various efforts to improve the ordering guarantees for HBase

[jira] [Created] (HBASE-21856) Consider Causal Replication

Lars Hofhansl created HBASE-21856: - Summary: Consider Causal Replication Key: HBASE-21856 URL: https://issues.apache.org/jira/browse/HBASE-21856 Project: HBase Issue Type: Brainstorming

[jira] [Commented] (HBASE-20928) Rewrite calculation of midpoint in binarySearch functions to prevent overflow

[ https://issues.apache.org/jira/browse/HBASE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742420#comment-16742420 ] Lars Hofhansl commented on HBASE-20928: --- In a microbenchmark I actually found that >>> is slightly

[jira] [Commented] (HBASE-20928) Rewrite calculation of midpoint in binarySearch functions to prevent overflow

[ https://issues.apache.org/jira/browse/HBASE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741823#comment-16741823 ] Lars Hofhansl commented on HBASE-20928: --- Hey [~bashrc-real], I'm not saying that this is causing

[jira] [Comment Edited] (HBASE-20928) Rewrite calculation of midpoint in binarySearch functions to prevent overflow

[ https://issues.apache.org/jira/browse/HBASE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741782#comment-16741782 ] Lars Hofhansl edited comment on HBASE-20928 at 1/14/19 6:15 AM: The

[jira] [Comment Edited] (HBASE-20928) Rewrite calculation of midpoint in binarySearch functions to prevent overflow

[ https://issues.apache.org/jira/browse/HBASE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741782#comment-16741782 ] Lars Hofhansl edited comment on HBASE-20928 at 1/14/19 6:20 AM: The

[jira] [Commented] (HBASE-20928) Rewrite calculation of midpoint in binarySearch functions to prevent overflow

[ https://issues.apache.org/jira/browse/HBASE-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741782#comment-16741782 ] Lars Hofhansl commented on HBASE-20928: --- The cited article _explicitly_ states that {{int mid =

[jira] [Commented] (HBASE-21679) Port HBASE-6028 (Start/Stop compactions at region server level) to branch-1

[ https://issues.apache.org/jira/browse/HBASE-21679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741448#comment-16741448 ] Lars Hofhansl commented on HBASE-21679: --- Sorry [~apurtell], no time to review last week. > Port

[jira] [Comment Edited] (HBASE-21573) More sensible client default timeout values

[ https://issues.apache.org/jira/browse/HBASE-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730948#comment-16730948 ] Lars Hofhansl edited comment on HBASE-21573 at 12/30/18 11:20 AM: -- I

[jira] [Commented] (HBASE-21573) More sensible client default timeout values

[ https://issues.apache.org/jira/browse/HBASE-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730948#comment-16730948 ] Lars Hofhansl commented on HBASE-21573: --- I have long thought that all these config options are a

[jira] [Commented] (HBASE-21657) PrivateCellUtil#estimatedSerializedSizeOf has been the bottleneck in 100% scan case.

[ https://issues.apache.org/jira/browse/HBASE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730681#comment-16730681 ] Lars Hofhansl commented on HBASE-21657: --- This is interesting. I think this method is only called

[jira] [Comment Edited] (HBASE-21657) PrivateCellUtil#estimatedSerializedSizeOf has been the bottleneck in 100% scan case.

[ https://issues.apache.org/jira/browse/HBASE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730673#comment-16730673 ] Lars Hofhansl edited comment on HBASE-21657 at 12/29/18 12:40 PM: --

[jira] [Commented] (HBASE-21657) PrivateCellUtil#estimatedSerializedSizeOf has been the bottleneck in 100% scan case.

[ https://issues.apache.org/jira/browse/HBASE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730673#comment-16730673 ] Lars Hofhansl commented on HBASE-21657: --- HBASE-20459 > PrivateCellUtil#estimatedSerializedSizeOf

[jira] [Commented] (HBASE-21657) PrivateCellUtil#estimatedSerializedSizeOf has been the bottleneck in 100% scan case.

[ https://issues.apache.org/jira/browse/HBASE-21657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730672#comment-16730672 ] Lars Hofhansl commented on HBASE-21657: --- Didn't I fix a case like this a while ago (can't find the

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721993#comment-16721993 ] Lars Hofhansl commented on HBASE-21590: --- Sorry about the checkstyle stuff, and thanks for fixing

[jira] [Commented] (HBASE-21607) HBase Region server read fails in case of datanode disk error.

[ https://issues.apache.org/jira/browse/HBASE-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721916#comment-16721916 ] Lars Hofhansl commented on HBASE-21607: --- I guess the question I have: Why is there a NULL-checksum

[jira] [Commented] (HBASE-21607) HBase Region server read fails in case of datanode disk error.

[ https://issues.apache.org/jira/browse/HBASE-21607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721914#comment-16721914 ] Lars Hofhansl commented on HBASE-21607: --- This of course is rare case... Choosing 0 read from a

[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=16720909#comment-16720909 ] Lars Hofhansl commented on HBASE-19863: --- Looks back on this... Isn't it cheaper to just detect the

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720647#comment-16720647 ] Lars Hofhansl commented on HBASE-21590: --- Committed to branch-1.4 as well. > Optimize

[jira] [Updated] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21590: -- Fix Version/s: 1.4.10 > Optimize trySkipToNextColumn in StoreScanner a bit >

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720601#comment-16720601 ] Lars Hofhansl commented on HBASE-21590: --- I'll also look for other places where this applicable -

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720553#comment-16720553 ] Lars Hofhansl commented on HBASE-21590: --- And what about branch-2.0 and branch-2.1. > Optimize

[jira] [Updated] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21590: -- Resolution: Fixed Fix Version/s: 2.2.0 1.5.0

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720539#comment-16720539 ] Lars Hofhansl commented on HBASE-21590: --- [~stack] In fact this triggers in many/most cases.

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719567#comment-16719567 ] Lars Hofhansl commented on HBASE-21590: --- Going to commit later, unless I hear objections. >

[jira] [Comment Edited] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719560#comment-16719560 ] Lars Hofhansl edited comment on HBASE-21590 at 12/12/18 11:53 PM: --

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719560#comment-16719560 ] Lars Hofhansl commented on HBASE-21590: --- TestMultiColumnScanner passes locally finishes in about

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719553#comment-16719553 ] Lars Hofhansl commented on HBASE-21590: --- TestMultiColumnScanner is at least suspicious. Looking at

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719561#comment-16719561 ] Lars Hofhansl commented on HBASE-21590: --- So this is good to go it seems. > Optimize

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719548#comment-16719548 ] Lars Hofhansl commented on HBASE-21590: --- Mater patch. > Optimize trySkipToNextColumn in

[jira] [Updated] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21590: -- Attachment: HBASE-21590-master.txt > Optimize trySkipToNextColumn in StoreScanner a bit >

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719537#comment-16719537 ] Lars Hofhansl commented on HBASE-21590: --- Yeah. branch-1, branch-2, and master was my plan. Was

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719386#comment-16719386 ] Lars Hofhansl commented on HBASE-21590: --- This shaves off 30% or more of scan time from some scans.

[jira] [Assigned] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned HBASE-21590: - Assignee: Lars Hofhansl > Optimize trySkipToNextColumn in StoreScanner a bit >

[jira] [Commented] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719384#comment-16719384 ] Lars Hofhansl commented on HBASE-21590: --- Here's a patch against branch one. Based on an idea from

[jira] [Updated] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[ https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21590: -- Attachment: 21590-1.5.txt > Optimize trySkipToNextColumn in StoreScanner a bit >

[jira] [Created] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

Lars Hofhansl created HBASE-21590: - Summary: Optimize trySkipToNextColumn in StoreScanner a bit Key: HBASE-21590 URL: https://issues.apache.org/jira/browse/HBASE-21590 Project: HBase Issue

[jira] [Resolved] (HBASE-19034) Implement "optimize SEEK to SKIP" in storefile scanner

[ https://issues.apache.org/jira/browse/HBASE-19034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved HBASE-19034. --- Resolution: Won't Fix Closing as "Won't Fix" as it turns out that the doing this

[jira] [Commented] (HBASE-17958) Avoid passing unexpected cell to ScanQueryMatcher when optimize SEEK to SKIP

[ https://issues.apache.org/jira/browse/HBASE-17958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719329#comment-16719329 ] Lars Hofhansl commented on HBASE-17958: --- I do like the address compare idea above, lemme try that.

[jira] [Commented] (HBASE-17958) Avoid passing unexpected cell to ScanQueryMatcher when optimize SEEK to SKIP

[ https://issues.apache.org/jira/browse/HBASE-17958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719318#comment-16719318 ] Lars Hofhansl commented on HBASE-17958: --- Looking at this one again... Since it popped up in the

[jira] [Comment Edited] (HBASE-17958) Avoid passing unexpected cell to ScanQueryMatcher when optimize SEEK to SKIP

[ https://issues.apache.org/jira/browse/HBASE-17958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719318#comment-16719318 ] Lars Hofhansl edited comment on HBASE-17958 at 12/12/18 7:12 PM: -

[jira] [Commented] (HBASE-21464) Splitting blocked with meta NSRE during split transaction

[ https://issues.apache.org/jira/browse/HBASE-21464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709033#comment-16709033 ] Lars Hofhansl commented on HBASE-21464: --- +1 Questions: * What if we have 1000's of clients? Would

[jira] [Commented] (HBASE-21464) Splitting blocked with meta NSRE during split transaction

[ https://issues.apache.org/jira/browse/HBASE-21464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704076#comment-16704076 ] Lars Hofhansl commented on HBASE-21464: --- +1 (as a small comment: Will this remove us even further

[jira] [Commented] (HBASE-21418) Reduce a number of reseek operations in MemstoreScanner when seek point is close to the current row.

[ https://issues.apache.org/jira/browse/HBASE-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684460#comment-16684460 ] Lars Hofhansl commented on HBASE-21418: --- I'll look this evening (bit busy throughout the day) >

[jira] [Commented] (HBASE-21418) Reduce a number of reseek operations in MemstoreScanner when seek point is close to the current row.

[ https://issues.apache.org/jira/browse/HBASE-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671944#comment-16671944 ] Lars Hofhansl commented on HBASE-21418: --- Thanks for looking into this [~Jeongdae Kim]! Generally

[jira] [Commented] (HBASE-21418) Reduce a number of reseek operations in MemstoreScanner when seek point is close to the current row.

[ https://issues.apache.org/jira/browse/HBASE-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671928#comment-16671928 ] Lars Hofhansl commented on HBASE-21418: --- (Sorry about the re-assign, hit some keyboard combination

[jira] [Assigned] (HBASE-21418) Reduce a number of reseek operations in MemstoreScanner when seek point is close to the current row.

[ https://issues.apache.org/jira/browse/HBASE-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned HBASE-21418: - Assignee: Jeongdae Kim (was: Lars Hofhansl) > Reduce a number of reseek operations in

[jira] [Assigned] (HBASE-21418) Reduce a number of reseek operations in MemstoreScanner when seek point is close to the current row.

[ https://issues.apache.org/jira/browse/HBASE-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned HBASE-21418: - Assignee: Lars Hofhansl (was: Jeongdae Kim) > Reduce a number of reseek operations in

[jira] [Commented] (HBASE-18228) HBCK improvements

[ https://issues.apache.org/jira/browse/HBASE-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653811#comment-16653811 ] Lars Hofhansl commented on HBASE-18228: --- Just coming across this 7 months later. :( In what way

[jira] [Commented] (HBASE-21229) Add a nightly check that client-server wire compatibility works

[ https://issues.apache.org/jira/browse/HBASE-21229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629232#comment-16629232 ] Lars Hofhansl commented on HBASE-21229: --- It would actually quite helpful (but a *lot* of work) to

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629227#comment-16629227 ] Lars Hofhansl commented on HBASE-20993: --- I'd like to point that it is not Phoenix to was broken by

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624450#comment-16624450 ] Lars Hofhansl commented on HBASE-20993: --- I assume the server "hangs" waiting to read the

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624447#comment-16624447 ] Lars Hofhansl commented on HBASE-20993: --- Thanks [~reidchan]. I think this should happen with a

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624417#comment-16624417 ] Lars Hofhansl commented on HBASE-20993: --- Here's the trace: {code} Object.wait(long) line: not

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624404#comment-16624404 ] Lars Hofhansl commented on HBASE-20993: --- It's from the Phoenix 4.x-HBase-1.4 branch, which pulls

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624333#comment-16624333 ] Lars Hofhansl commented on HBASE-20993: --- In the debugger I see that the Phoenix client hangs when

[jira] [Reopened] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reopened HBASE-20993: --- > [Auth] IPC client fallback to simple auth allowed doesn't work >

[jira] [Commented] (HBASE-20993) [Auth] IPC client fallback to simple auth allowed doesn't work

[ https://issues.apache.org/jira/browse/HBASE-20993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624316#comment-16624316 ] Lars Hofhansl commented on HBASE-20993: --- Turns out this breaks Phoenix (all defaults for both).

[jira] [Comment Edited] (HBASE-13082) Coarsen StoreScanner locks to RegionScanner

[ https://issues.apache.org/jira/browse/HBASE-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623041#comment-16623041 ] Lars Hofhansl edited comment on HBASE-13082 at 9/21/18 4:27 AM:

[jira] [Comment Edited] (HBASE-13082) Coarsen StoreScanner locks to RegionScanner

[ https://issues.apache.org/jira/browse/HBASE-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623041#comment-16623041 ] Lars Hofhansl edited comment on HBASE-13082 at 9/21/18 4:27 AM:

[jira] [Commented] (HBASE-13082) Coarsen StoreScanner locks to RegionScanner

[ https://issues.apache.org/jira/browse/HBASE-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623041#comment-16623041 ] Lars Hofhansl commented on HBASE-13082: --- [~ram_krish] Above sounded a bit more whiny than

[jira] [Commented] (HBASE-20704) Sometimes some compacted storefiles are not archived on region close

[ https://issues.apache.org/jira/browse/HBASE-20704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623039#comment-16623039 ] Lars Hofhansl commented on HBASE-20704: --- We should add the same to the "Can't archive..." message,

[jira] [Comment Edited] (HBASE-13082) Coarsen StoreScanner locks to RegionScanner

[ https://issues.apache.org/jira/browse/HBASE-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16621508#comment-16621508 ] Lars Hofhansl edited comment on HBASE-13082 at 9/20/18 4:51 AM:

[jira] [Commented] (HBASE-13082) Coarsen StoreScanner locks to RegionScanner

[ https://issues.apache.org/jira/browse/HBASE-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16621508#comment-16621508 ] Lars Hofhansl commented on HBASE-13082: --- Interestingly we just upgraded one of our clusters to

[jira] [Commented] (HBASE-10342) RowKey Prefix Bloom Filter

[ https://issues.apache.org/jira/browse/HBASE-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617095#comment-16617095 ] Lars Hofhansl commented on HBASE-10342: --- I want to pick this up again. Perhaps all that's needed

[jira] [Commented] (HBASE-16594) ROW_INDEX_V2 DBE

[ https://issues.apache.org/jira/browse/HBASE-16594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608319#comment-16608319 ] Lars Hofhansl commented on HBASE-16594: --- Did this get abandoned? > ROW_INDEX_V2 DBE >

[jira] [Updated] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

[ https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21166: -- Fix Version/s: 1.2.7 1.4.8 1.3.3 > Creating a

[jira] [Commented] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

[ https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607752#comment-16607752 ] Lars Hofhansl commented on HBASE-21166: --- Pushed to branch-1.2, branch-1.3, and branch-1.4 as well.

[jira] [Updated] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

[ https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21166: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Creating a

[jira] [Commented] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

[ https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607723#comment-16607723 ] Lars Hofhansl commented on HBASE-21166: --- Tests are unrelated. Committing. branch-1 only. Can

[jira] [Updated] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

[ https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-21166: -- Attachment: HBASE-21166.branch-1.001.patch > Creating a CoprocessorHConnection re-retrieves

[jira] [Commented] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

[ https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607469#comment-16607469 ] Lars Hofhansl commented on HBASE-21166: --- I'll get the test-run to execute eventually. > Creating

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