[jira] [Assigned] (PHOENIX-5754) Phoenix IT tests are failing in Precommit QA build randomly.
[ https://issues.apache.org/jira/browse/PHOENIX-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-5754: Assignee: Istvan Toth > Phoenix IT tests are failing in Precommit QA build randomly. > > > Key: PHOENIX-5754 > URL: https://issues.apache.org/jira/browse/PHOENIX-5754 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.15.1, 4.16.0 >Reporter: Neha Gupta >Assignee: Istvan Toth >Priority: Blocker > Labels: build-failure, precommit > > While running Phoenix IT tests in QA, JVM is getting killed for random tests. > QA stops the run and mark that build failed. Related [jenkins builds| > [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3520/console]] does > not give any information about the failure. We are blocked on committing > patches until this issue is fixed. > This behavior was observed in [PHOENIX-5496|#comment-17048460] and > [PHOENIX-5698|#comment-17049989] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5819) Remove unused presto-phoenix-shaded connector module
[ https://issues.apache.org/jira/browse/PHOENIX-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-5819: -- Attachment: PHOENIX-5819.master.v1.patch > Remove unused presto-phoenix-shaded connector module > > > Key: PHOENIX-5819 > URL: https://issues.apache.org/jira/browse/PHOENIX-5819 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.16.0 >Reporter: Vincent Poon >Assignee: Vincent Poon >Priority: Major > Attachments: PHOENIX-5819.master.v1.patch > > > No longer needed, as Presto is using the embedded classifier in > phoenix-client instead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5819) Remove unused presto-phoenix-shaded connector module
Vincent Poon created PHOENIX-5819: - Summary: Remove unused presto-phoenix-shaded connector module Key: PHOENIX-5819 URL: https://issues.apache.org/jira/browse/PHOENIX-5819 Project: Phoenix Issue Type: Bug Affects Versions: 4.16.0 Reporter: Vincent Poon Assignee: Vincent Poon No longer needed, as Presto is using the embedded classifier in phoenix-client instead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5818) Add documentation for query timeoutDuration attribute in Pherf scenarios
Christine Feng created PHOENIX-5818: --- Summary: Add documentation for query timeoutDuration attribute in Pherf scenarios Key: PHOENIX-5818 URL: https://issues.apache.org/jira/browse/PHOENIX-5818 Project: Phoenix Issue Type: Task Reporter: Christine Feng Assignee: Christine Feng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (PHOENIX-5817) Prepatch script is a psycho killer
Istvan Toth created PHOENIX-5817: Summary: Prepatch script is a psycho killer Key: PHOENIX-5817 URL: https://issues.apache.org/jira/browse/PHOENIX-5817 Project: Phoenix Issue Type: Bug Reporter: Istvan Toth Assignee: Istvan Toth The prepatch script assumes that it is the only test on a machine, and kills other copies of itself, as well as unrelated maven tests runs. Looking at the times, it's obvious that https://builds.apache.org/job/PreCommit-PHOENIX-Build/3712/ was killed by https://builds.apache.org/job/PreCommit-PHOENIX-Build/3713/ What's worse, it also kills ANY maven surefire/failsafe process, so not only does it sabotage other copies of itself, it also sabotages other projects' tests that share the ASF infrastructure. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5601) Add a new Coprocessor - ViewTTLAware Coprocessor
[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob Isaac resolved PHOENIX-5601. -- Resolution: Feedback Received Will be pursuing an alternate implementation using PHOENIX-5629 > Add a new Coprocessor - ViewTTLAware Coprocessor > > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task >Affects Versions: 4.15.0, 5.1.0 >Reporter: Jacob Isaac >Assignee: Jacob Isaac >Priority: Major > Fix For: 4.16.0 > > Attachments: PHOENIX-5601.4.x-HBase-1.3.008.patch, > PHOENIX-5601.master.008.patch > > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5799) Inline Index Verification Output API
[ https://issues.apache.org/jira/browse/PHOENIX-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5799: - Attachment: PHOENIX-5799-4.x.v1.patch > Inline Index Verification Output API > > > Key: PHOENIX-5799 > URL: https://issues.apache.org/jira/browse/PHOENIX-5799 > Project: Phoenix > Issue Type: Bug >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Major > Attachments: PHOENIX-5799-4.x.v1.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Followup from PHOENIX-5773 -- split out the logic in > IndexRebuildRegionScanner that writes to the output table into its own class, > plus add read methods and tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (TEPHRA-306) disable trimStackTrace
[ https://issues.apache.org/jira/browse/TEPHRA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved TEPHRA-306. Resolution: Fixed Merged. Thanks for the review [~anew] > disable trimStackTrace > -- > > Key: TEPHRA-306 > URL: https://issues.apache.org/jira/browse/TEPHRA-306 > Project: Phoenix Tephra > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Poorna Chandra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > I propose that we disable the trimStackTrace surefire/failsafe option. > See the identical PHOENIX-5814 for more information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEPHRA-306) disable trimStackTrace
[ https://issues.apache.org/jira/browse/TEPHRA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17074642#comment-17074642 ] Andreas Neumann commented on TEPHRA-306: Agreed this make sense. > disable trimStackTrace > -- > > Key: TEPHRA-306 > URL: https://issues.apache.org/jira/browse/TEPHRA-306 > Project: Phoenix Tephra > Issue Type: Improvement >Reporter: Istvan Toth >Assignee: Poorna Chandra >Priority: Major > > I propose that we disable the trimStackTrace surefire/failsafe option. > See the identical PHOENIX-5814 for more information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5811) Synchronise Phoenix dependencies to match Hbase dependency versions
[ https://issues.apache.org/jira/browse/PHOENIX-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5811: --- Attachment: PHOENIX-5811.master.v3.patch > Synchronise Phoenix dependencies to match Hbase dependency versions > --- > > Key: PHOENIX-5811 > URL: https://issues.apache.org/jira/browse/PHOENIX-5811 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5811.master.v1.patch, > PHOENIX-5811.master.v2.patch, PHOENIX-5811.master.v3.patch > > > Phoenix uses an older version of some dependencies. > We could reduce the number of dependencies by using the same versions as > Hbase. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5810) PhoenixMRJobSubmitter is not working on a cluster with a single yarn RM
[
https://issues.apache.org/jira/browse/PHOENIX-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated PHOENIX-5810:
---
Attachment: PHOENIX-5810.master.v4.patch
> PhoenixMRJobSubmitter is not working on a cluster with a single yarn RM
> ---
>
> Key: PHOENIX-5810
> URL: https://issues.apache.org/jira/browse/PHOENIX-5810
> Project: Phoenix
> Issue Type: Bug
>Reporter: Richard Antal
>Assignee: Richard Antal
>Priority: Major
> Attachments: PHOENIX-5810.master.v1.patch,
> PHOENIX-5810.master.v2.patch, PHOENIX-5810.master.v3.patch,
> PHOENIX-5810.master.v4.patch
>
>
> {code:java}
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode =
> NoNode for /yarn-leader-election{code}
> The error happens when we want to run scheduleIndexBuilds. In
> getSubmittedYarnApps, getActiveResourceManagerHost uses zookeeper to
> determine the active Resource Manager.
> But /yarn-leader-election only exists if yarn is in HA mode.
> I think this function should work well when we have single yarn RM and read
> its address from the config.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (PHOENIX-5811) Synchronise Phoenix dependencies to match Hbase dependency versions
[ https://issues.apache.org/jira/browse/PHOENIX-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5811: --- Attachment: PHOENIX-5811.master.v2.patch > Synchronise Phoenix dependencies to match Hbase dependency versions > --- > > Key: PHOENIX-5811 > URL: https://issues.apache.org/jira/browse/PHOENIX-5811 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5811.master.v1.patch, > PHOENIX-5811.master.v2.patch > > > Phoenix uses an older version of some dependencies. > We could reduce the number of dependencies by using the same versions as > Hbase. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5811) Synchronise Phoenix dependencies to match Hbase dependency versions
[ https://issues.apache.org/jira/browse/PHOENIX-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5811: --- Comment: was deleted (was: The main purpose of this patch is to use newer version of the dependencies, possible the same as the hbase master branch.) > Synchronise Phoenix dependencies to match Hbase dependency versions > --- > > Key: PHOENIX-5811 > URL: https://issues.apache.org/jira/browse/PHOENIX-5811 > Project: Phoenix > Issue Type: Task >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5811.master.v1.patch > > > Phoenix uses an older version of some dependencies. > We could reduce the number of dependencies by using the same versions as > Hbase. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5794) Create a threshold for non async index creation, that can be modified in configs
[ https://issues.apache.org/jira/browse/PHOENIX-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5794: --- Attachment: PHOENIX-5794.master.v9.patch > Create a threshold for non async index creation, that can be modified in > configs > > > Key: PHOENIX-5794 > URL: https://issues.apache.org/jira/browse/PHOENIX-5794 > Project: Phoenix > Issue Type: Improvement >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5794.master.v1.patch, > PHOENIX-5794.master.v2.patch, PHOENIX-5794.master.v3.patch, > PHOENIX-5794.master.v4.patch, PHOENIX-5794.master.v5.patch, > PHOENIX-5794.master.v6.patch, PHOENIX-5794.master.v7.patch, > PHOENIX-5794.master.v8.patch, PHOENIX-5794.master.v9.patch > > > Issue: > When user try to create an index on a huge phoenix table the region servers > crashed which led to multiple regions going in RIT state. > > Solution: > If the expected byte read size is higher than the limit we raise an exception > to notify the user that the index should be created asynchronously. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (PHOENIX-5730) Stabilize tests on master branch
[ https://issues.apache.org/jira/browse/PHOENIX-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth reassigned PHOENIX-5730: Assignee: Istvan Toth > Stabilize tests on master branch > > > Key: PHOENIX-5730 > URL: https://issues.apache.org/jira/browse/PHOENIX-5730 > Project: Phoenix > Issue Type: Task >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > > There are frequent integration test failures on the master branch, that have > no apparent rhyme or reason. > Most of the failures seem to be related to timeouts, and performance issues. > The failures seem more frequent when testing against the HBase 2.1 and HBase > 2.2 profiles. > Investigate the causes, and try to stabilise the tests. > Some ideas to start with: > * Try to copy the performance related minicluster settings from the > integration tests in the 2.2 HBase branch > * investigate the test execution times to see whether and where there is a > correlation between execution time increases and HBase profiles. > * Investigate whether the failing tests have execution times that are close > to the timeout values during successful runs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (PHOENIX-5814) disable trimStackTrace
[ https://issues.apache.org/jira/browse/PHOENIX-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved PHOENIX-5814. -- Fix Version/s: 4.x queryserver-1.0.0 connectors-1.0.0 5.1.0 Resolution: Fixed Patch has been applied to the phoenix* repositories, and I've opened clone tickets for Omid and Tephra, so there's nothing more to do here. > disable trimStackTrace > -- > > Key: PHOENIX-5814 > URL: https://issues.apache.org/jira/browse/PHOENIX-5814 > Project: Phoenix > Issue Type: Improvement > Components: connectors, core, omid, queryserver, tephra >Reporter: Istvan Toth >Assignee: Istvan Toth >Priority: Major > Fix For: 5.1.0, connectors-1.0.0, queryserver-1.0.0, 4.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The default trimStackTrace=true maven setting is quite effective at making > test output useless for all but the trivial failures. > I propose setting it to false everywhere (i.e all five repos) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OMID-155) disable trimStackTrace
Istvan Toth created OMID-155: Summary: disable trimStackTrace Key: OMID-155 URL: https://issues.apache.org/jira/browse/OMID-155 Project: Phoenix Omid Issue Type: Improvement Reporter: Istvan Toth I propose that we disable the trimStackTrace surefire/failsafe option. See the identical PHOENIX-5814 for more information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (TEPHRA-306) disable trimStackTrace
Istvan Toth created TEPHRA-306: -- Summary: disable trimStackTrace Key: TEPHRA-306 URL: https://issues.apache.org/jira/browse/TEPHRA-306 Project: Phoenix Tephra Issue Type: Improvement Reporter: Istvan Toth Assignee: Poorna Chandra I propose that we disable the trimStackTrace surefire/failsafe option. See the identical PHOENIX-5814 for more information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (PHOENIX-5794) Create a threshold for non async index creation, that can be modified in configs
[ https://issues.apache.org/jira/browse/PHOENIX-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Antal updated PHOENIX-5794: --- Attachment: PHOENIX-5794.master.v8.patch > Create a threshold for non async index creation, that can be modified in > configs > > > Key: PHOENIX-5794 > URL: https://issues.apache.org/jira/browse/PHOENIX-5794 > Project: Phoenix > Issue Type: Improvement >Reporter: Richard Antal >Assignee: Richard Antal >Priority: Major > Attachments: PHOENIX-5794.master.v1.patch, > PHOENIX-5794.master.v2.patch, PHOENIX-5794.master.v3.patch, > PHOENIX-5794.master.v4.patch, PHOENIX-5794.master.v5.patch, > PHOENIX-5794.master.v6.patch, PHOENIX-5794.master.v7.patch, > PHOENIX-5794.master.v8.patch > > > Issue: > When user try to create an index on a huge phoenix table the region servers > crashed which led to multiple regions going in RIT state. > > Solution: > If the expected byte read size is higher than the limit we raise an exception > to notify the user that the index should be created asynchronously. -- This message was sent by Atlassian Jira (v8.3.4#803005)
