[jira] [Commented] (PHOENIX-4732) Improve config defaults for async secondary index MR jobs

2018-05-08 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468325#comment-16468325
 ] 

Hudson commented on PHOENIX-4732:
-

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1881 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1881/])
PHOENIX-4732 Improve config defaults for async secondary index MR jobs 
(jtaylor: rev 0482c539a16d3b404f65ad9ccd9664d0d479e3cc)
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/util/PhoenixMRJobUtil.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/automation/PhoenixMRJobSubmitter.java


> Improve config defaults for async secondary index MR jobs
> -
>
> Key: PHOENIX-4732
> URL: https://issues.apache.org/jira/browse/PHOENIX-4732
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Attachments: PHOENIX-4732_v1.patch
>
>
> Our defaults for the MR job that builds secondary indexes should be changed 
> to better support larger tables.
>  * Increased the number of hbase client retries to 10
>  * Increased the hbase scanner time out, map reduce task timeout, hbase rpc 
> timeout to 10 minutes instead of 1 min
>  * Added ability to control MR job concurrently running mapper tasks to 20 by 
> default and a phoenix property phoenix.mr.concurrent.map.limit using which 
> one can configure the same.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4726) save index build timestamp -- for SYNC case only.

2018-05-08 Thread Vincent Poon (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468196#comment-16468196
 ] 

Vincent Poon commented on PHOENIX-4726:
---

I think we can call it "INDEX_CREATED_DATE", or even just "CREATED_DATE" to 
keep with the existing naming convention.  This is the base case, and async 
differentiates with prepending ASYNC_

> save index build timestamp -- for SYNC case only.
> -
>
> Key: PHOENIX-4726
> URL: https://issues.apache.org/jira/browse/PHOENIX-4726
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Xu Cang
>Priority: Minor
> Attachments: PHOENIX-4726.patch.1, PHOENIX-4726.patch.2
>
>
> save index build timestamp, similar to ASYNC_REBUILD_TIMESTAMP,  or 
> ASYNC_CREATED_DATE
> ("SYNC_INDEX_CREATED_DATE" is my proposed name for SYNC case.)
>  
> Check IndexUtil.java for related code.
> The reason this can be useful is: We saw a case index state stuck in 'b' for 
> quite some long time. And without a timestamp to indicate where it started, 
> it's hard to tell if this is a legit running task or stuck...
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-3431) Generate DDL from an existing Phoenix Schema

2018-05-08 Thread William Shen (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468113#comment-16468113
 ] 

William Shen commented on PHOENIX-3431:
---

Thanks [~jamestaylor] for the speedy reply.

The tool was created for internal use, so it was not created with automated 
tests and it is currently on Phoenix 4.10. Can you guide us regarding how to 
bring this into the project? Specifically,
 * Do we need to add tests to meet coverage level
 * Do we need to bring this up to speed to a given version of phoenix
 * Do we add this as a new module to the main project?

Thank you!

> Generate DDL from an existing Phoenix Schema
> 
>
> Key: PHOENIX-3431
> URL: https://issues.apache.org/jira/browse/PHOENIX-3431
> Project: Phoenix
>  Issue Type: New Feature
>Affects Versions: 4.6.0, 4.8.0
>Reporter: Kumar Palaniappan
>Assignee: Kumar Palaniappan
>Priority: Minor
> Fix For: 4.8.1
>
>
> A tool to generate DDLs for Phoenix tables and indices from an existing 
> schema.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4724) Efficient Equi-Depth histogram for streaming data

2018-05-08 Thread Vincent Poon (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent Poon updated PHOENIX-4724:
--
Attachment: PHOENIX-4724.v2.patch

> Efficient Equi-Depth histogram for streaming data
> -
>
> Key: PHOENIX-4724
> URL: https://issues.apache.org/jira/browse/PHOENIX-4724
> Project: Phoenix
>  Issue Type: Sub-task
>Affects Versions: 4.15.0
>Reporter: Vincent Poon
>Assignee: Vincent Poon
>Priority: Major
> Attachments: PHOENIX-4724.v1.patch, PHOENIX-4724.v2.patch
>
>
> Equi-Depth histogram from 
> http://web.cs.ucla.edu/~zaniolo/papers/Histogram-EDBT2011-CamReady.pdf, but 
> without the sliding window - we assume a single window over the entire data 
> set.
> Used to generate the bucket boundaries of a histogram where each bucket has 
> the same # of items.
> This is useful, for example, for pre-splitting an index table, by feeding in 
> data from the indexed column.
> Works on streaming data - the histogram is dynamically updated for each new 
> value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4623) Inconsistent physical view index name

2018-05-08 Thread James Taylor (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor updated PHOENIX-4623:
--
Attachment: PHOENIX-4623_v1.patch

> Inconsistent physical view index name
> -
>
> Key: PHOENIX-4623
> URL: https://issues.apache.org/jira/browse/PHOENIX-4623
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>Reporter: Akshita Malhotra
>Assignee: James Taylor
>Priority: Major
>  Labels: easyfix
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4623_v1.patch
>
>
> The physical view indexes are incorrectly named when table has a schema. For 
> instance, if a table name is "SCH.TABLE", during creation the physical index 
> table is named as "_IDX_SCH.TABLE" which doesn't look right. In case 
> namespaces are enabled, the physical index table is named as "SCH:_IDX_TABLE"
> The client APIs on the other hand such as 
> MetaDataUtil.getViewIndexName(String schemaName, String tableName) API to 
> retrieve the phyisical view index name returns "SCH._IDX_TABLE" which as per 
> convention returns the right name but functionally leads to wrong results as 
> this is not how the physical indexes are named during construction.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-3431) Generate DDL from an existing Phoenix Schema

2018-05-08 Thread James Taylor (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468105#comment-16468105
 ] 

James Taylor commented on PHOENIX-3431:
---

That's great, [~willshen]. I think both would be good.

> Generate DDL from an existing Phoenix Schema
> 
>
> Key: PHOENIX-3431
> URL: https://issues.apache.org/jira/browse/PHOENIX-3431
> Project: Phoenix
>  Issue Type: New Feature
>Affects Versions: 4.6.0, 4.8.0
>Reporter: Kumar Palaniappan
>Assignee: Kumar Palaniappan
>Priority: Minor
> Fix For: 4.8.1
>
>
> A tool to generate DDLs for Phoenix tables and indices from an existing 
> schema.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-3431) Generate DDL from an existing Phoenix Schema

2018-05-08 Thread William Shen (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468103#comment-16468103
 ] 

William Shen commented on PHOENIX-3431:
---

[~jamestaylor], we have created a standalone tool to create DDL for 
table/indices from an existing schema. Would this be something that the 
community would be interested in taking in? Or would the project be interested 
only in integrating the functionality into something like a SHOW CREATE TABLE?

The interface to our tool looks like:
- Once built using {{mvn clean install}}, this tool can be run from the command 
line using {{java -jar path/to/ddl-generator.jar}}.  Run with the -h or --help 
flags for usage instructions.
- The DDL Generator takes the following command-line arguments
{quote} --connection  The JDBC connection string the generator should use to 
connect to Phoenix.  
 --schema  The schema to generate DDLs for.  
 --tables  An optional comma-delimited list of tables to generate DDLs for. 
 
 --indices An optional comma-delimited list of base tables to generate 
index DDLs for.  
 --newSchema   Optionally, the schema name to use in the generated DDLs instead 
of --schema.  
 --indicesOnly If this flag is present, generate DDLs for indices only.  
 --tablesOnly  If this flag is present, generate DDLs for tables only.  
 -h, --helpPrint the usage instructions.{quote}

> Generate DDL from an existing Phoenix Schema
> 
>
> Key: PHOENIX-3431
> URL: https://issues.apache.org/jira/browse/PHOENIX-3431
> Project: Phoenix
>  Issue Type: New Feature
>Affects Versions: 4.6.0, 4.8.0
>Reporter: Kumar Palaniappan
>Assignee: Kumar Palaniappan
>Priority: Minor
> Fix For: 4.8.1
>
>
> A tool to generate DDLs for Phoenix tables and indices from an existing 
> schema.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (PHOENIX-4623) Inconsistent physical view index name

2018-05-08 Thread James Taylor (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor reassigned PHOENIX-4623:
-

Assignee: James Taylor

> Inconsistent physical view index name
> -
>
> Key: PHOENIX-4623
> URL: https://issues.apache.org/jira/browse/PHOENIX-4623
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>Reporter: Akshita Malhotra
>Assignee: James Taylor
>Priority: Major
>  Labels: easyfix
> Fix For: 4.15.0
>
>
> The physical view indexes are incorrectly named when table has a schema. For 
> instance, if a table name is "SCH.TABLE", during creation the physical index 
> table is named as "_IDX_SCH.TABLE" which doesn't look right. In case 
> namespaces are enabled, the physical index table is named as "SCH:_IDX_TABLE"
> The client APIs on the other hand such as 
> MetaDataUtil.getViewIndexName(String schemaName, String tableName) API to 
> retrieve the phyisical view index name returns "SCH._IDX_TABLE" which as per 
> convention returns the right name but functionally leads to wrong results as 
> this is not how the physical indexes are named during construction.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4732) Improve config defaults for async secondary index MR jobs

2018-05-08 Thread Andrew Purtell (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468066#comment-16468066
 ] 

Andrew Purtell commented on PHOENIX-4732:
-

+1


> Improve config defaults for async secondary index MR jobs
> -
>
> Key: PHOENIX-4732
> URL: https://issues.apache.org/jira/browse/PHOENIX-4732
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Attachments: PHOENIX-4732_v1.patch
>
>
> Our defaults for the MR job that builds secondary indexes should be changed 
> to better support larger tables.
>  * Increased the number of hbase client retries to 10
>  * Increased the hbase scanner time out, map reduce task timeout, hbase rpc 
> timeout to 10 minutes instead of 1 min
>  * Added ability to control MR job concurrently running mapper tasks to 20 by 
> default and a phoenix property phoenix.mr.concurrent.map.limit using which 
> one can configure the same.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4732) Improve config defaults for async secondary index MR jobs

2018-05-08 Thread James Taylor (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor updated PHOENIX-4732:
--
Attachment: PHOENIX-4732_v1.patch

> Improve config defaults for async secondary index MR jobs
> -
>
> Key: PHOENIX-4732
> URL: https://issues.apache.org/jira/browse/PHOENIX-4732
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
> Attachments: PHOENIX-4732_v1.patch
>
>
> Our defaults for the MR job that builds secondary indexes should be changed 
> to better support larger tables.
>  * Increased the number of hbase client retries to 10
>  * Increased the hbase scanner time out, map reduce task timeout, hbase rpc 
> timeout to 10 minutes instead of 1 min
>  * Added ability to control MR job concurrently running mapper tasks to 20 by 
> default and a phoenix property phoenix.mr.concurrent.map.limit using which 
> one can configure the same.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (PHOENIX-4732) Improve config defaults for async secondary index MR jobs

2018-05-08 Thread James Taylor (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor reassigned PHOENIX-4732:
-

Assignee: James Taylor  (was: Loknath Priyatham Teja Singamsetty )

> Improve config defaults for async secondary index MR jobs
> -
>
> Key: PHOENIX-4732
> URL: https://issues.apache.org/jira/browse/PHOENIX-4732
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
>
> Our defaults for the MR job that builds secondary indexes should be changed 
> to better support larger tables.
>  * Increased the number of hbase client retries to 10
>  * Increased the hbase scanner time out, map reduce task timeout, hbase rpc 
> timeout to 10 minutes instead of 1 min
>  * Added ability to control MR job concurrently running mapper tasks to 20 by 
> default and a phoenix property phoenix.mr.concurrent.map.limit using which 
> one can configure the same.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4685) Properly handle connection caching for Phoenix inside RegionServers

2018-05-08 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468026#comment-16468026
 ] 

Hudson commented on PHOENIX-4685:
-

FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1875 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1875/])
PHOENIX-4685 Properly handle connection caching for Phoenix inside (rajeshbabu: 
rev ea06a10a35af8eb0773b077cbbe704275bb7869c)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/util/ServerUtil.java


> Properly handle connection caching for Phoenix inside RegionServers
> ---
>
> Key: PHOENIX-4685
> URL: https://issues.apache.org/jira/browse/PHOENIX-4685
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: PHOENIX-4685.patch, PHOENIX-4685_5.x-HBase-2.0.patch, 
> PHOENIX-4685_jstack, PHOENIX-4685_v2.patch, PHOENIX-4685_v3.patch, 
> PHOENIX-4685_v4.patch, PHOENIX-4685_v5.patch
>
>
> Currently trying to write data to indexed table failing with OOME where 
> unable to create native threads. But it's working fine with 4.7.x branches. 
> Found many threads created for meta lookup and shared threads and no space to 
> create threads. This is happening even with short circuit writes enabled.
> {noformat}
> 2018-04-08 13:06:04,747 WARN  
> [RpcServer.default.FPBQ.Fifo.handler=9,queue=0,port=16020] 
> index.PhoenixIndexFailurePolicy: handleFailure failed
> java.io.IOException: java.lang.reflect.UndeclaredThrowableException
> at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:185)
> at 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy.handleFailureWithExceptions(PhoenixIndexFailurePolicy.java:217)
> at 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy.handleFailure(PhoenixIndexFailurePolicy.java:143)
> at 
> org.apache.phoenix.hbase.index.write.IndexWriter.writeAndKillYourselfOnFailure(IndexWriter.java:160)
> at 
> org.apache.phoenix.hbase.index.write.IndexWriter.writeAndKillYourselfOnFailure(IndexWriter.java:144)
> at 
> org.apache.phoenix.hbase.index.Indexer.doPostWithExceptions(Indexer.java:632)
> at org.apache.phoenix.hbase.index.Indexer.doPost(Indexer.java:607)
> at 
> org.apache.phoenix.hbase.index.Indexer.postBatchMutateIndispensably(Indexer.java:590)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$30.call(RegionCoprocessorHost.java:1037)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$30.call(RegionCoprocessorHost.java:1034)
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:540)
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:614)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.postBatchMutateIndispensably(RegionCoprocessorHost.java:1034)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation.doPostOpCleanupForMiniBatch(HRegion.java:3533)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutate(HRegion.java:3914)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3822)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3753)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:1027)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:959)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:922)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2666)
> at 
> org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:42014)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1761)
> at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:448)
> at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:429)
> at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
> at 
> 

[jira] [Updated] (PHOENIX-4732) Improve config defaults for async secondary index MR jobs

2018-05-08 Thread James Taylor (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor updated PHOENIX-4732:
--
Description: 
Our defaults for the MR job that builds secondary indexes should be changed to 
better support larger tables.
 * Increased the number of hbase client retries to 10
 * Increased the hbase scanner time out, map reduce task timeout, hbase rpc 
timeout to 10 minutes instead of 1 min
 * Added ability to control MR job concurrently running mapper tasks to 20 by 
default and a phoenix property phoenix.mr.concurrent.map.limit using which one 
can configure the same.

  was:Our defaults for the MR job that builds secondary indexes should be 
changed to better support larger tables.


> Improve config defaults for async secondary index MR jobs
> -
>
> Key: PHOENIX-4732
> URL: https://issues.apache.org/jira/browse/PHOENIX-4732
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: Loknath Priyatham Teja Singamsetty 
>Priority: Major
>
> Our defaults for the MR job that builds secondary indexes should be changed 
> to better support larger tables.
>  * Increased the number of hbase client retries to 10
>  * Increased the hbase scanner time out, map reduce task timeout, hbase rpc 
> timeout to 10 minutes instead of 1 min
>  * Added ability to control MR job concurrently running mapper tasks to 20 by 
> default and a phoenix property phoenix.mr.concurrent.map.limit using which 
> one can configure the same.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (PHOENIX-4732) Improve config defaults for async secondary index MR jobs

2018-05-08 Thread James Taylor (JIRA)
James Taylor created PHOENIX-4732:
-

 Summary: Improve config defaults for async secondary index MR jobs
 Key: PHOENIX-4732
 URL: https://issues.apache.org/jira/browse/PHOENIX-4732
 Project: Phoenix
  Issue Type: Improvement
Reporter: James Taylor
Assignee: Loknath Priyatham Teja Singamsetty 


Our defaults for the MR job that builds secondary indexes should be changed to 
better support larger tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4730) Upgrade Netty versions in 0.98 branch

2018-05-08 Thread James Taylor (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468004#comment-16468004
 ] 

James Taylor commented on PHOENIX-4730:
---

+1. Thanks, [~apurtell]!

> Upgrade Netty versions in 0.98 branch
> -
>
> Key: PHOENIX-4730
> URL: https://issues.apache.org/jira/browse/PHOENIX-4730
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4730-0.98.patch
>
>
> Upgrade Netty versions to the following:
> 3.10.6.Final
> 4.0.56.Final



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (PHOENIX-4730) Upgrade Netty versions in 0.98 branch

2018-05-08 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell updated PHOENIX-4730:

Attachment: PHOENIX-4730-0.98.patch

> Upgrade Netty versions in 0.98 branch
> -
>
> Key: PHOENIX-4730
> URL: https://issues.apache.org/jira/browse/PHOENIX-4730
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: Andrew Purtell
>Priority: Major
> Fix For: 4.15.0
>
> Attachments: PHOENIX-4730-0.98.patch
>
>
> Upgrade Netty versions to the following:
> 3.10.6.Final
> 4.0.56.Final



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (PHOENIX-4730) Upgrade Netty versions in 0.98 branch

2018-05-08 Thread Andrew Purtell (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell reassigned PHOENIX-4730:
---

Assignee: Andrew Purtell

> Upgrade Netty versions in 0.98 branch
> -
>
> Key: PHOENIX-4730
> URL: https://issues.apache.org/jira/browse/PHOENIX-4730
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Assignee: Andrew Purtell
>Priority: Major
>
> Upgrade Netty versions to the following:
> 3.10.6.Final
> 4.0.56.Final



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (PHOENIX-4730) Upgrade Netty versions in 0.98 branch

2018-05-08 Thread James Taylor (JIRA)
James Taylor created PHOENIX-4730:
-

 Summary: Upgrade Netty versions in 0.98 branch
 Key: PHOENIX-4730
 URL: https://issues.apache.org/jira/browse/PHOENIX-4730
 Project: Phoenix
  Issue Type: Improvement
Reporter: James Taylor


Upgrade Netty versions to the following:

3.10.6.Final
4.0.56.Final



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (PHOENIX-4729) Remove unused netty dependencies in 0.98 branch

2018-05-08 Thread James Taylor (JIRA)

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor resolved PHOENIX-4729.
---
Resolution: Invalid

> Remove unused netty dependencies in 0.98 branch
> ---
>
> Key: PHOENIX-4729
> URL: https://issues.apache.org/jira/browse/PHOENIX-4729
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: James Taylor
>Priority: Major
>
> Looks like netty dependencies were removed in branches other than 0.98 in 
> PHOENIX-4261. [~elserj] mentioned here[1] that it's not required for 0.98 
> since we only depend on io.netty. [~apurtell] has a patch that removes the 
> dependencies from 0.98 as well. What's the right thing to do?
> [1] 
> https://issues.apache.org/jira/browse/PHOENIX-4261?focusedCommentId=16188251=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16188251



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4685) Properly handle connection caching for Phoenix inside RegionServers

2018-05-08 Thread Vincent Poon (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467953#comment-16467953
 ] 

Vincent Poon commented on PHOENIX-4685:
---

Actually it looks like the patch is ok because 
DelegateRegionCoprocessorEnvironment was changed as well.

 

[~rajeshbabu] Do you have any more details on the circumstances under which you 
saw the OOME?

> Properly handle connection caching for Phoenix inside RegionServers
> ---
>
> Key: PHOENIX-4685
> URL: https://issues.apache.org/jira/browse/PHOENIX-4685
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: PHOENIX-4685.patch, PHOENIX-4685_5.x-HBase-2.0.patch, 
> PHOENIX-4685_jstack, PHOENIX-4685_v2.patch, PHOENIX-4685_v3.patch, 
> PHOENIX-4685_v4.patch, PHOENIX-4685_v5.patch
>
>
> Currently trying to write data to indexed table failing with OOME where 
> unable to create native threads. But it's working fine with 4.7.x branches. 
> Found many threads created for meta lookup and shared threads and no space to 
> create threads. This is happening even with short circuit writes enabled.
> {noformat}
> 2018-04-08 13:06:04,747 WARN  
> [RpcServer.default.FPBQ.Fifo.handler=9,queue=0,port=16020] 
> index.PhoenixIndexFailurePolicy: handleFailure failed
> java.io.IOException: java.lang.reflect.UndeclaredThrowableException
> at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:185)
> at 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy.handleFailureWithExceptions(PhoenixIndexFailurePolicy.java:217)
> at 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy.handleFailure(PhoenixIndexFailurePolicy.java:143)
> at 
> org.apache.phoenix.hbase.index.write.IndexWriter.writeAndKillYourselfOnFailure(IndexWriter.java:160)
> at 
> org.apache.phoenix.hbase.index.write.IndexWriter.writeAndKillYourselfOnFailure(IndexWriter.java:144)
> at 
> org.apache.phoenix.hbase.index.Indexer.doPostWithExceptions(Indexer.java:632)
> at org.apache.phoenix.hbase.index.Indexer.doPost(Indexer.java:607)
> at 
> org.apache.phoenix.hbase.index.Indexer.postBatchMutateIndispensably(Indexer.java:590)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$30.call(RegionCoprocessorHost.java:1037)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$30.call(RegionCoprocessorHost.java:1034)
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:540)
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:614)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.postBatchMutateIndispensably(RegionCoprocessorHost.java:1034)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation.doPostOpCleanupForMiniBatch(HRegion.java:3533)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutate(HRegion.java:3914)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3822)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3753)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:1027)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:959)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:922)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2666)
> at 
> org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:42014)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1761)
> at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:448)
> at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:429)
> at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at 

[jira] [Created] (PHOENIX-4729) Remove unused netty dependencies in 0.98 branch

2018-05-08 Thread James Taylor (JIRA)
James Taylor created PHOENIX-4729:
-

 Summary: Remove unused netty dependencies in 0.98 branch
 Key: PHOENIX-4729
 URL: https://issues.apache.org/jira/browse/PHOENIX-4729
 Project: Phoenix
  Issue Type: Improvement
Reporter: James Taylor


Looks like netty dependencies were removed in branches other than 0.98 in 
PHOENIX-4261. [~elserj] mentioned here[1] that it's not required for 0.98 since 
we only depend on io.netty. [~apurtell] has a patch that removes the 
dependencies from 0.98 as well. What's the right thing to do?

[1] 
https://issues.apache.org/jira/browse/PHOENIX-4261?focusedCommentId=16188251=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16188251



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [VOTE] Release of Apache Phoenix 4.14.0 RC0

2018-05-08 Thread Xavier Jodoin

I agree it's not a showstopper


On 2018-05-08 11:35 AM, James Taylor wrote:

Others are free to weigh in here too, but that seems like a minor issue,
not a showstopper.

On Tue, May 8, 2018 at 8:19 AM Xavier Jodoin  wrote:


I've tested it on PostgreSQL and this is the behavior

and if you run on phoenix -> select ARRAY_TO_STRING(array_append(null,
3), ',') it return {3}

the problem come when you operate on a column value


On 2018-05-08 11:15 AM, James Taylor wrote:

That’s not a showstopper IMHO. It’s not entirely clear it’s a bug.


On Tue, May 8, 2018 at 8:11 AM Xavier Jodoin  wrote:


-1

I've tested it with HBase 1.1 the release is working as expected but I
encountered a bug during my test but it's not a regression

https://issues.apache.org/jira/browse/PHOENIX-4728

The behavior is the same on 4.13.1

Xavier

On 2018-05-03 01:51 PM, James Taylor wrote:

Hello Everyone,

This is a call for a vote on Apache Phoenix 4.14.0 RC0. This is a patch
release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1,

1.2,

1.3 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both a
source-only release and a convenience binary release for each supported
HBase version.

This release has feature parity with supported HBase versions and

includes

the following improvements:
- Over 90 bug fixes
- Support for GRANT/REVOKE [1][2]
- Avoid server retries for mutable indexes [3]
- Pure client side transactional index maintenance [4]
- Prune local index regions scanned during query execution [5][6]
- Support NOT NULL constraint for any column for immutable table [7]

The source tarball, including signatures, digests, etc can be found at:


https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/src/

The binary artifacts can be found at:


https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/bin/

The binary parcels for CDH can be found at:


https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/parcels/

For a complete list of changes, see:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120=12342145

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/mujtaba.asc ( HBase-x.x

versions )

https://people.apache.org/keys/committer/pboado.asc ( cdh5.x versions

)

https://dist.apache.org/repos/dist/dev/phoenix/KEYS

The hash and tag to be voted upon:


https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3b45df9990648f466b987a7576e9a40974fe8c2f
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-0.98-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=190e768a671e7f1ada4c7efc28bdb1cc7db6234c
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.1-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6d994b02b51ecc09e1284d11f025ccd9193b7c06
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.2-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=166d159674155c357203af389b6ac1d0e6842b75
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.3-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=8ed7eb0f5878202d744dd3d7a08235a45adfd3bc
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.11.2-rc0

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC0

2018-05-08 Thread James Taylor
Others are free to weigh in here too, but that seems like a minor issue,
not a showstopper.

On Tue, May 8, 2018 at 8:19 AM Xavier Jodoin  wrote:

> I've tested it on PostgreSQL and this is the behavior
>
> and if you run on phoenix -> select ARRAY_TO_STRING(array_append(null,
> 3), ',') it return {3}
>
> the problem come when you operate on a column value
>
>
> On 2018-05-08 11:15 AM, James Taylor wrote:
> > That’s not a showstopper IMHO. It’s not entirely clear it’s a bug.
> >
> >
> > On Tue, May 8, 2018 at 8:11 AM Xavier Jodoin  wrote:
> >
> >> -1
> >>
> >> I've tested it with HBase 1.1 the release is working as expected but I
> >> encountered a bug during my test but it's not a regression
> >>
> >> https://issues.apache.org/jira/browse/PHOENIX-4728
> >>
> >> The behavior is the same on 4.13.1
> >>
> >> Xavier
> >>
> >> On 2018-05-03 01:51 PM, James Taylor wrote:
> >>> Hello Everyone,
> >>>
> >>> This is a call for a vote on Apache Phoenix 4.14.0 RC0. This is a patch
> >>> release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1,
> >> 1.2,
> >>> 1.3 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both a
> >>> source-only release and a convenience binary release for each supported
> >>> HBase version.
> >>>
> >>> This release has feature parity with supported HBase versions and
> >> includes
> >>> the following improvements:
> >>> - Over 90 bug fixes
> >>> - Support for GRANT/REVOKE [1][2]
> >>> - Avoid server retries for mutable indexes [3]
> >>> - Pure client side transactional index maintenance [4]
> >>> - Prune local index regions scanned during query execution [5][6]
> >>> - Support NOT NULL constraint for any column for immutable table [7]
> >>>
> >>> The source tarball, including signatures, digests, etc can be found at:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/src/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/src/
> >>> The binary artifacts can be found at:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/bin/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/bin/
> >>> The binary parcels for CDH can be found at:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/parcels/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/parcels/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/parcels/
> >>
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/parcels/
> >>> For a complete list of changes, see:
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120=12342145
> >>> Release artifacts are signed with the following key:
> >>> https://people.apache.org/keys/committer/mujtaba.asc ( HBase-x.x
> >> versions )
> >>> https://people.apache.org/keys/committer/pboado.asc ( cdh5.x versions
> )
> >>> https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >>>
> >>> The hash and tag to be voted upon:
> >>>
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3b45df9990648f466b987a7576e9a40974fe8c2f
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-0.98-rc0
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=190e768a671e7f1ada4c7efc28bdb1cc7db6234c
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.1-rc0
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6d994b02b51ecc09e1284d11f025ccd9193b7c06
> >>
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.2-rc0
> >>
> 

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC0

2018-05-08 Thread Xavier Jodoin

I've tested it on PostgreSQL and this is the behavior

and if you run on phoenix -> select ARRAY_TO_STRING(array_append(null, 
3), ',') it return {3}


the problem come when you operate on a column value


On 2018-05-08 11:15 AM, James Taylor wrote:

That’s not a showstopper IMHO. It’s not entirely clear it’s a bug.


On Tue, May 8, 2018 at 8:11 AM Xavier Jodoin  wrote:


-1

I've tested it with HBase 1.1 the release is working as expected but I
encountered a bug during my test but it's not a regression

https://issues.apache.org/jira/browse/PHOENIX-4728

The behavior is the same on 4.13.1

Xavier

On 2018-05-03 01:51 PM, James Taylor wrote:

Hello Everyone,

This is a call for a vote on Apache Phoenix 4.14.0 RC0. This is a patch
release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1,

1.2,

1.3 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both a
source-only release and a convenience binary release for each supported
HBase version.

This release has feature parity with supported HBase versions and

includes

the following improvements:
- Over 90 bug fixes
- Support for GRANT/REVOKE [1][2]
- Avoid server retries for mutable indexes [3]
- Pure client side transactional index maintenance [4]
- Prune local index regions scanned during query execution [5][6]
- Support NOT NULL constraint for any column for immutable table [7]

The source tarball, including signatures, digests, etc can be found at:


https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/src/

The binary artifacts can be found at:


https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/bin/

The binary parcels for CDH can be found at:


https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/parcels/

For a complete list of changes, see:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120=12342145

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/mujtaba.asc ( HBase-x.x

versions )

https://people.apache.org/keys/committer/pboado.asc ( cdh5.x versions )
https://dist.apache.org/repos/dist/dev/phoenix/KEYS

The hash and tag to be voted upon:


https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3b45df9990648f466b987a7576e9a40974fe8c2f
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-0.98-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=190e768a671e7f1ada4c7efc28bdb1cc7db6234c
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.1-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6d994b02b51ecc09e1284d11f025ccd9193b7c06
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.2-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=166d159674155c357203af389b6ac1d0e6842b75
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.3-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=8ed7eb0f5878202d744dd3d7a08235a45adfd3bc
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.11.2-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a769d8ab81618ae981b095b8cdead6bff63eb627
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.12.2-rc0

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC0

2018-05-08 Thread James Taylor
That’s not a showstopper IMHO. It’s not entirely clear it’s a bug.


On Tue, May 8, 2018 at 8:11 AM Xavier Jodoin  wrote:

> -1
>
> I've tested it with HBase 1.1 the release is working as expected but I
> encountered a bug during my test but it's not a regression
>
> https://issues.apache.org/jira/browse/PHOENIX-4728
>
> The behavior is the same on 4.13.1
>
> Xavier
>
> On 2018-05-03 01:51 PM, James Taylor wrote:
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.14.0 RC0. This is a patch
> > release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1,
> 1.2,
> > 1.3 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both a
> > source-only release and a convenience binary release for each supported
> > HBase version.
> >
> > This release has feature parity with supported HBase versions and
> includes
> > the following improvements:
> > - Over 90 bug fixes
> > - Support for GRANT/REVOKE [1][2]
> > - Avoid server retries for mutable indexes [3]
> > - Pure client side transactional index maintenance [4]
> > - Prune local index regions scanned during query execution [5][6]
> > - Support NOT NULL constraint for any column for immutable table [7]
> >
> > The source tarball, including signatures, digests, etc can be found at:
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/src/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/src/
> >
> > The binary artifacts can be found at:
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/bin/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/bin/
> >
> > The binary parcels for CDH can be found at:
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/parcels/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/parcels/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/parcels/
> >
> https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/parcels/
> >
> > For a complete list of changes, see:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120=12342145
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/mujtaba.asc ( HBase-x.x
> versions )
> > https://people.apache.org/keys/committer/pboado.asc ( cdh5.x versions )
> > https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >
> > The hash and tag to be voted upon:
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3b45df9990648f466b987a7576e9a40974fe8c2f
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-0.98-rc0
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=190e768a671e7f1ada4c7efc28bdb1cc7db6234c
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.1-rc0
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6d994b02b51ecc09e1284d11f025ccd9193b7c06
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.2-rc0
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=166d159674155c357203af389b6ac1d0e6842b75
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.3-rc0
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=8ed7eb0f5878202d744dd3d7a08235a45adfd3bc
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.11.2-rc0
> >
> https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a769d8ab81618ae981b095b8cdead6bff63eb627
> >
> 

Re: [VOTE] Release of Apache Phoenix 4.14.0 RC0

2018-05-08 Thread Xavier Jodoin

-1

I've tested it with HBase 1.1 the release is working as expected but I 
encountered a bug during my test but it's not a regression


https://issues.apache.org/jira/browse/PHOENIX-4728

The behavior is the same on 4.13.1

Xavier

On 2018-05-03 01:51 PM, James Taylor wrote:

Hello Everyone,

This is a call for a vote on Apache Phoenix 4.14.0 RC0. This is a patch
release of Phoenix 4.14 and is compatible with Apache HBase 0.98, 1.1, 1.2,
1.3 and CDH 5.11, 5.12, 5.13, and 5.14. The release includes both a
source-only release and a convenience binary release for each supported
HBase version.

This release has feature parity with supported HBase versions and includes
the following improvements:
- Over 90 bug fixes
- Support for GRANT/REVOKE [1][2]
- Avoid server retries for mutable indexes [3]
- Pure client side transactional index maintenance [4]
- Prune local index regions scanned during query execution [5][6]
- Support NOT NULL constraint for any column for immutable table [7]

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/src/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-0.98-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.1-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-HBase-1.3-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/bin/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/bin/

The binary parcels for CDH can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.11.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.12.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.13.2-rc0/parcels/
https://dist.apache.org/repos/dist/dev/phoenix/apache-phoenix-4.14.0-cdh5.14.2-rc0/parcels/

For a complete list of changes, see:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120=12342145

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/mujtaba.asc ( HBase-x.x versions )
https://people.apache.org/keys/committer/pboado.asc ( cdh5.x versions )
https://dist.apache.org/repos/dist/dev/phoenix/KEYS

The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3b45df9990648f466b987a7576e9a40974fe8c2f
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-0.98-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=190e768a671e7f1ada4c7efc28bdb1cc7db6234c
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.1-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=6d994b02b51ecc09e1284d11f025ccd9193b7c06
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.2-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=166d159674155c357203af389b6ac1d0e6842b75
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.14.0-HBase-1.3-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=8ed7eb0f5878202d744dd3d7a08235a45adfd3bc
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.11.2-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=a769d8ab81618ae981b095b8cdead6bff63eb627
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.12.2-rc0
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=e3cfd8dae6a780c707f7d380e932f1f82d3bc702
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.13.2-rc0

https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=ebceebdd11d097e5e3697ab8c7f565406b55443a
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=shortlog;h=refs/tags/v4.14.0-cdh5.14.2-rc0

Vote will be open for at least 72 

[jira] [Commented] (PHOENIX-4727) Parameterize transaction tests with TRANSACTION_PROVIDER

2018-05-08 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467060#comment-16467060
 ] 

Hudson commented on PHOENIX-4727:
-

SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #117 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/117/])
PHOENIX-4727 Parameterize transaction tests with TRANSACTION_PROVIDER (jtaylor: 
rev d0f98a0206bcc210c272b4fde95e0191b36c1338)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/tx/TransactionIT.java


> Parameterize transaction tests with TRANSACTION_PROVIDER
> 
>
> Key: PHOENIX-4727
> URL: https://issues.apache.org/jira/browse/PHOENIX-4727
> Project: Phoenix
>  Issue Type: Test
>Reporter: James Taylor
>Assignee: James Taylor
>Priority: Major
>
> So that we can get test coverage for both Tephra and Omid, we should tweak 
> the parameterized transaction tests to define the TRANSACTION_PROVIDER 
> property.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (PHOENIX-4685) Properly handle connection caching for Phoenix inside RegionServers

2018-05-08 Thread Rajeshbabu Chintaguntla (JIRA)

[ 
https://issues.apache.org/jira/browse/PHOENIX-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466936#comment-16466936
 ] 

Rajeshbabu Chintaguntla commented on PHOENIX-4685:
--

[~jamestaylor] The 4.7.x branch I have tried has HTables caching that's why not 
seeing this issue but now it may be problem with latest code where we have 
removed HTables caching and and creating connection for each region in the RS 
because of that when we crate HTable we are going by creating so many threads 
which add 
 lot of overhead. Mostly it will be showstopper for 4.14 branch also.

> Properly handle connection caching for Phoenix inside RegionServers
> ---
>
> Key: PHOENIX-4685
> URL: https://issues.apache.org/jira/browse/PHOENIX-4685
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: PHOENIX-4685.patch, PHOENIX-4685_5.x-HBase-2.0.patch, 
> PHOENIX-4685_jstack, PHOENIX-4685_v2.patch, PHOENIX-4685_v3.patch, 
> PHOENIX-4685_v4.patch, PHOENIX-4685_v5.patch
>
>
> Currently trying to write data to indexed table failing with OOME where 
> unable to create native threads. But it's working fine with 4.7.x branches. 
> Found many threads created for meta lookup and shared threads and no space to 
> create threads. This is happening even with short circuit writes enabled.
> {noformat}
> 2018-04-08 13:06:04,747 WARN  
> [RpcServer.default.FPBQ.Fifo.handler=9,queue=0,port=16020] 
> index.PhoenixIndexFailurePolicy: handleFailure failed
> java.io.IOException: java.lang.reflect.UndeclaredThrowableException
> at org.apache.hadoop.hbase.security.User.runAsLoginUser(User.java:185)
> at 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy.handleFailureWithExceptions(PhoenixIndexFailurePolicy.java:217)
> at 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy.handleFailure(PhoenixIndexFailurePolicy.java:143)
> at 
> org.apache.phoenix.hbase.index.write.IndexWriter.writeAndKillYourselfOnFailure(IndexWriter.java:160)
> at 
> org.apache.phoenix.hbase.index.write.IndexWriter.writeAndKillYourselfOnFailure(IndexWriter.java:144)
> at 
> org.apache.phoenix.hbase.index.Indexer.doPostWithExceptions(Indexer.java:632)
> at org.apache.phoenix.hbase.index.Indexer.doPost(Indexer.java:607)
> at 
> org.apache.phoenix.hbase.index.Indexer.postBatchMutateIndispensably(Indexer.java:590)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$30.call(RegionCoprocessorHost.java:1037)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$30.call(RegionCoprocessorHost.java:1034)
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:540)
> at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:614)
> at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.postBatchMutateIndispensably(RegionCoprocessorHost.java:1034)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$MutationBatchOperation.doPostOpCleanupForMiniBatch(HRegion.java:3533)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.doMiniBatchMutate(HRegion.java:3914)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3822)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.batchMutate(HRegion.java:3753)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:1027)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:959)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:922)
> at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2666)
> at 
> org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:42014)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
> at 
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1761)
> at 
> org.apache.hadoop.security.SecurityUtil.doAsUser(SecurityUtil.java:448)
> at 
> org.apache.hadoop.security.SecurityUtil.doAsLoginUser(SecurityUtil.java:429)
> at