[
https://issues.apache.org/jira/browse/IMPALA-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18096009#comment-18096009
]
ASF subversion and git services commented on IMPALA-15176:
----------------------------------------------------------
Commit 21cd965f1670580f96d0ea846d9a2e83f66a2176 in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=21cd965f1 ]
IMPALA-15176: Fix Trino tests where $HOSTNAME is fqdn
If node.id is unset, Trino uses $HOSTNAME, which can be a problem
if it is fqdn, because . is not allowed in node.id.
Fixed this by setting node.id to impala-minicluster-trino.
Also added more diagnostics to Trino cluster startup to make
investigating similar problems easier.
Assisted-by: Cloude Opus 4.8
Change-Id: I6778d8b85d3d3565a49dd88df1a4209bcde3a82b
Reviewed-on: http://gerrit.cloudera.org:8080/24580
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> test_trino_interop broken on some linuxes
> -----------------------------------------
>
> Key: IMPALA-15176
> URL: https://issues.apache.org/jira/browse/IMPALA-15176
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Csaba Ringhofer
> Assignee: Csaba Ringhofer
> Priority: Blocker
>
> trino container failed to startup, got not too informative error message:
> failed on setup with "tests.common.trino_cluster.TrinoUnavailable: Trino did
> not become ready within 180s. Last error:"
> after extracting log it turned out that the problem is with node.id property
> which defaults to $HOSTNAME, which is not good for Trino in case it has "."
> in it, which is the case our RHEL test env
> "Errors:
> 1) Invalid configuration property node.id: should match
> [A-Za-z0-9][_A-Za-z0-9-]* (for class io.airlift.node.NodeConfig.nodeId)"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
