[
https://issues.apache.org/jira/browse/IMPALA-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804445#comment-17804445
]
Riza Suminto commented on IMPALA-12655:
---------------------------------------
[~stigahuang] [~csringhofer] will it be more stable if we raise max connection
to the underlying HMS db? My local postgresql has 100.
{code:java}
$ grep max_connections /etc/postgresql/12/main/postgresql.conf
max_connections = 100 # (change requires restart) {code}
I see we tune "listen_addresses" already in bin/bootstrap_system.sh.
> PlannerTest.testProcessingCost seems flaky
> ------------------------------------------
>
> Key: IMPALA-12655
> URL: https://issues.apache.org/jira/browse/IMPALA-12655
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Csaba Ringhofer
> Assignee: Riza Suminto
> Priority: Major
> Attachments:
> catalogd.impala-ec2-centos79-m6i-4xlarge-ondemand-02f3.vpc.cloudera.com.jenkins.log.INFO.20231218-120036.29228.tgz,
> compute-table-stats.log, hive-metastore.log.tgz,
> impalad.impala-ec2-centos79-m6i-4xlarge-ondemand-02f3.vpc.cloudera.com.jenkins.log.INFO.20231218-120036.29280.tgz
>
>
> This is probably caused by IMPALA-12601
> https://github.com/apache/impala/commit/8661f922d3ccb21da73b9f7f8734d9113429e9bb
> The error was cause by this line:
> https://github.com/apache/impala/blob/68fe57ff8492a7afdf14a62cabd3e2b0fcade9d1/testdata/workloads/functional-planner/queries/PlannerTest/tpcds-processing-cost.test#L8185
> In the actual plan the following appeared here:
> fk/pk conjuncts: assumed fk/pk
> [~rizaon]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
