[jira] [Commented] (PHOENIX-3869) Keep index failure policies the same for 4.x branches

[ https://issues.apache.org/jira/browse/PHOENIX-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020634#comment-16020634 ] Lars Hofhansl commented on PHOENIX-3869: Thanks [~jamestaylor]. +1 > Keep index failure

Re:Why Index.preWALRestore method just use RecoveryIndexWriter.write method to write the indexUpdates? It is a bug?

Could someone help me review this problem? At 2017-05-13 12:10:55, "程磊" wrote: Sorry, the code format of previous email is error , I reedit the code format : When I look the code of Index.preWALRestore method, I find RecoveryIndexWriter.write method is used to

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020571#comment-16020571 ] Samarth Jain commented on PHOENIX-3655: --- The idea behind the metrics APIs provided by Phoenix

[jira] [Commented] (PHOENIX-3869) Keep index failure policies the same for 4.x branches

[ https://issues.apache.org/jira/browse/PHOENIX-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020523#comment-16020523 ] Thomas D'Silva commented on PHOENIX-3869: - +1 > Keep index failure policies the same for 4.x

[jira] [Commented] (PHOENIX-3811) Do not disable index on write failure by default

[ https://issues.apache.org/jira/browse/PHOENIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020490#comment-16020490 ] James Taylor commented on PHOENIX-3811: --- FYI, I filed PHOENIX-3869 to keep the default behavior

[jira] [Commented] (PHOENIX-3869) Keep index failure policies the same for 4.x branches

[ https://issues.apache.org/jira/browse/PHOENIX-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020488#comment-16020488 ] James Taylor commented on PHOENIX-3869: --- Please review, [~tdsilva]. This just maintains our

[jira] [Updated] (PHOENIX-3869) Keep index failure policies the same for 4.x branches

[ https://issues.apache.org/jira/browse/PHOENIX-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3869: -- Attachment: PHOENIX-3869.patch > Keep index failure policies the same for 4.x branches >

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020446#comment-16020446 ] James Taylor commented on PHOENIX-3655: --- There are both global metrics and per statement metrics

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020440#comment-16020440 ] Rahul Shrivastava commented on PHOENIX-3655: [~jamestaylor] Phoenix metrics provide

[jira] [Commented] (PHOENIX-3872) Increase default for index metadata expiration

[ https://issues.apache.org/jira/browse/PHOENIX-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020420#comment-16020420 ] James Taylor commented on PHOENIX-3872: --- Another explanation for the cache expiration might be a

[jira] [Commented] (PHOENIX-3874) Push through client-side timeouts for server-side cross region server operations

[ https://issues.apache.org/jira/browse/PHOENIX-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020399#comment-16020399 ] James Taylor commented on PHOENIX-3874: --- FYI, [~apurtell] > Push through client-side timeouts for

[jira] [Created] (PHOENIX-3874) Push through client-side timeouts for server-side cross region server operations

James Taylor created PHOENIX-3874: - Summary: Push through client-side timeouts for server-side cross region server operations Key: PHOENIX-3874 URL: https://issues.apache.org/jira/browse/PHOENIX-3874

[jira] [Created] (PHOENIX-3873) Surface metric for tracking size of region server global cache

James Taylor created PHOENIX-3873: - Summary: Surface metric for tracking size of region server global cache Key: PHOENIX-3873 URL: https://issues.apache.org/jira/browse/PHOENIX-3873 Project: Phoenix

[jira] [Updated] (PHOENIX-3872) Increase default for index metadata expiration

[ https://issues.apache.org/jira/browse/PHOENIX-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3872: -- Description: The default timeout is 30 minutes. We should increase it substantially to ride

[jira] [Updated] (PHOENIX-3872) Increase default for index metadata expiration

[ https://issues.apache.org/jira/browse/PHOENIX-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3872: -- Attachment: PHOENIX-3872.patch > Increase default for index metadata expiration >

[jira] [Commented] (PHOENIX-3872) Increase default for index metadata expiration

[ https://issues.apache.org/jira/browse/PHOENIX-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020388#comment-16020388 ] Sergey Soldatov commented on PHOENIX-3872: -- [~jamestaylor] Do you have a scenario when 2hr may

[jira] [Commented] (PHOENIX-3871) Incremental stats collection

[ https://issues.apache.org/jira/browse/PHOENIX-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020365#comment-16020365 ] Sergey Soldatov commented on PHOENIX-3871: -- We collect statistic on all compactions that have

[jira] [Commented] (PHOENIX-3872) Increase default for index metadata expiration

[ https://issues.apache.org/jira/browse/PHOENIX-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020348#comment-16020348 ] James Taylor commented on PHOENIX-3872: --- FYI, [~mvanwely]. > Increase default for index metadata

[jira] [Commented] (PHOENIX-3767) Prevent spurious tracing spans from Hadoop being written in Phoenix Trace tables

[ https://issues.apache.org/jira/browse/PHOENIX-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020342#comment-16020342 ] Hadoop QA commented on PHOENIX-3767: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-3767) Prevent spurious tracing spans from Hadoop being written in Phoenix Trace tables

[ https://issues.apache.org/jira/browse/PHOENIX-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3767: - Attachment: PHOENIX-3767.003.patch > Prevent spurious tracing spans from Hadoop being written

[jira] [Commented] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020325#comment-16020325 ] Hadoop QA commented on PHOENIX-3248: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3752) Remove hadoop metrics integration from the tracing framework

[ https://issues.apache.org/jira/browse/PHOENIX-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020321#comment-16020321 ] Hadoop QA commented on PHOENIX-3752: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020274#comment-16020274 ] Karan Mehta commented on PHOENIX-3248: -- Rebased the patch with master branch. Also changed the

[jira] [Updated] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3248: - Attachment: (was: PHOENIX-3248.002.patch) > Enable HBase server-side scan metrics to be

[jira] [Updated] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3248: - Attachment: PHOENIX-3248.002.patch > Enable HBase server-side scan metrics to be returned to

[jira] [Updated] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3248: - Attachment: PHOENIX-3248.002.patch > Enable HBase server-side scan metrics to be returned to

[jira] [Updated] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3248: - Attachment: (was: PHOENIX-3248.002.patch) > Enable HBase server-side scan metrics to be

[jira] [Updated] (PHOENIX-3248) Enable HBase server-side scan metrics to be returned to client and surfaced through metrics

[ https://issues.apache.org/jira/browse/PHOENIX-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3248: - Attachment: PHOENIX-3248.002.patch > Enable HBase server-side scan metrics to be returned to

[jira] [Commented] (PHOENIX-3843) Improve logging for UNION ALL errors

[ https://issues.apache.org/jira/browse/PHOENIX-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020218#comment-16020218 ] Hudson commented on PHOENIX-3843: - SUCCESS: Integrated in Jenkins build Phoenix-master #1617 (See

[jira] [Commented] (PHOENIX-3752) Remove hadoop metrics integration from the tracing framework

[ https://issues.apache.org/jira/browse/PHOENIX-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020204#comment-16020204 ] Karan Mehta commented on PHOENIX-3752: -- Thanks for the review, [~samarthjain]. I have updated the

[jira] [Updated] (PHOENIX-3752) Remove hadoop metrics integration from the tracing framework

[ https://issues.apache.org/jira/browse/PHOENIX-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3752: - Attachment: PHOENIX-3752.003.patch > Remove hadoop metrics integration from the tracing

[jira] [Created] (PHOENIX-3871) Incremental stats collection

Eli Levine created PHOENIX-3871: --- Summary: Incremental stats collection Key: PHOENIX-3871 URL: https://issues.apache.org/jira/browse/PHOENIX-3871 Project: Phoenix Issue Type: Improvement

[jira] [Commented] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020125#comment-16020125 ] Rahul Shrivastava commented on PHOENIX-3654: I have done the rebase, squash and removing the

[jira] [Commented] (PHOENIX-3784) Chunk commit data using lower of byte-based and row-count limits

[ https://issues.apache.org/jira/browse/PHOENIX-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020012#comment-16020012 ] James Taylor commented on PHOENIX-3784: --- This seems like an important one to get into 4.11.0 and a

[jira] [Updated] (PHOENIX-3784) Chunk commit data using lower of byte-based and row-count limits

[ https://issues.apache.org/jira/browse/PHOENIX-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3784: -- Fix Version/s: 4.11.0 > Chunk commit data using lower of byte-based and row-count limits >

[jira] [Commented] (PHOENIX-3853) Local Index - Writes to local index are twice as slow as global and get exponentially slower with PHOENIX-3827_v2 patch

[ https://issues.apache.org/jira/browse/PHOENIX-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020010#comment-16020010 ] James Taylor commented on PHOENIX-3853: --- [~lhofhansl] - see the very nice graph that Mujtaba put

[jira] [Assigned] (PHOENIX-3870) Backward compatibility fails between v4.9.0 and head of 4.x (4.11-SNAPSHOT)

[ https://issues.apache.org/jira/browse/PHOENIX-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan reassigned PHOENIX-3870: --- Assignee: Thomas D'Silva > Backward compatibility fails between v4.9.0 and head of

[jira] [Created] (PHOENIX-3870) Backward compatibility fails between v4.9.0 and head of 4.x (4.11-SNAPSHOT)

Mujtaba Chohan created PHOENIX-3870: --- Summary: Backward compatibility fails between v4.9.0 and head of 4.x (4.11-SNAPSHOT) Key: PHOENIX-3870 URL: https://issues.apache.org/jira/browse/PHOENIX-3870

[jira] [Commented] (PHOENIX-3788) GLOBAL_MUTATION_BATCH_SIZE should reflect size of chunked batches

[ https://issues.apache.org/jira/browse/PHOENIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019998#comment-16019998 ] James Taylor commented on PHOENIX-3788: --- We track metrics on the client to track for a given

[jira] [Comment Edited] (PHOENIX-3788) GLOBAL_MUTATION_BATCH_SIZE should reflect size of chunked batches

[ https://issues.apache.org/jira/browse/PHOENIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019998#comment-16019998 ] James Taylor edited comment on PHOENIX-3788 at 5/22/17 6:46 PM:

[jira] [Commented] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019947#comment-16019947 ] Andrew Purtell commented on PHOENIX-3654: - Ok, looks like somewhere in the branch there is a

[jira] [Commented] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019945#comment-16019945 ] Andrew Purtell commented on PHOENIX-3654: - Please rename this issue "PHOENIX-3654 Load Balancer

[jira] [Comment Edited] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019945#comment-16019945 ] Andrew Purtell edited comment on PHOENIX-3654 at 5/22/17 6:15 PM: --

[jira] [Commented] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019942#comment-16019942 ] ASF GitHub Bot commented on PHOENIX-3654: - Github user apurtell commented on the issue:

[GitHub] phoenix issue #236: Loadbalancer

Github user apurtell commented on the issue: https://github.com/apache/phoenix/pull/236 Also please resolve indicated conflicts. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] phoenix issue #236: Loadbalancer

Github user apurtell commented on the issue: https://github.com/apache/phoenix/pull/236 @rahulsIOT Please rename this issue "PHOENIX-3654 Load Balancer for thin client" and please squash all commits and set the commit message to "PHOENIX-3654 Load Balancer for thin client (Rahul

[jira] [Commented] (PHOENIX-3853) Local Index - Writes to local index are twice as slow as global and get exponentially slower with PHOENIX-3827_v2 patch

[ https://issues.apache.org/jira/browse/PHOENIX-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019927#comment-16019927 ] Mujtaba Chohan commented on PHOENIX-3853: - [~lhofhansl] Only issue remains is the perf.

[jira] [Updated] (PHOENIX-3178) Row count incorrect for UPSERT SELECT when auto commit is false

[ https://issues.apache.org/jira/browse/PHOENIX-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3178: -- Fix Version/s: (was: 4.8.3) 4.11.0 > Row count incorrect for UPSERT

[jira] [Created] (PHOENIX-3869) Keep index failure policies the same for 4.x branches

James Taylor created PHOENIX-3869: - Summary: Keep index failure policies the same for 4.x branches Key: PHOENIX-3869 URL: https://issues.apache.org/jira/browse/PHOENIX-3869 Project: Phoenix

[jira] [Commented] (PHOENIX-3834) Provide a way to collect stats and not use it for query parallelization

[ https://issues.apache.org/jira/browse/PHOENIX-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019873#comment-16019873 ] James Taylor commented on PHOENIX-3834: --- The approach looks good, [~samarthjain]. I think we'll

[jira] [Commented] (PHOENIX-3822) Surface byte and row estimates in a machine readable way when doing EXPLAIN PLAN

[ https://issues.apache.org/jira/browse/PHOENIX-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019852#comment-16019852 ] James Taylor commented on PHOENIX-3822: --- Thanks for the updates, [~samarthjain]. Couple of minor

[jira] [Commented] (PHOENIX-3827) Make use of HBASE-15600 to write local index mutations along with data mutations atomically

[ https://issues.apache.org/jira/browse/PHOENIX-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019847#comment-16019847 ] Rajeshbabu Chintaguntla commented on PHOENIX-3827: -- Yes we can make use of

[jira] [Commented] (PHOENIX-3655) Metrics for PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019833#comment-16019833 ] James Taylor commented on PHOENIX-3655: --- [~elserj] - I think your review comments are most

[jira] [Commented] (PHOENIX-3827) Make use of HBASE-15600 to write local index mutations along with data mutations atomically

[ https://issues.apache.org/jira/browse/PHOENIX-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019780#comment-16019780 ] James Taylor commented on PHOENIX-3827: --- If it works to using HRegion#batchMutate, let's just

[jira] [Commented] (PHOENIX-3827) Make use of HBASE-15600 to write local index mutations along with data mutations atomically

[ https://issues.apache.org/jira/browse/PHOENIX-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019765#comment-16019765 ] Rajeshbabu Chintaguntla commented on PHOENIX-3827: -- [~jamestaylor] bq. The