Skip to content

Trino worker nodes fail to start when config.properties contain web ui specific properties #11689

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
thereisnospoon opened this issue Mar 28, 2022 · 3 comments

Comments

@thereisnospoon
Copy link

thereisnospoon commented Mar 28, 2022

Hi,

I've been trying to provision a Trino cluster on top of AWS EMR. One thing I wanted to configure is to disable auth on Web UI by setting web-ui.authentication.type to fixed in config.properties file as per https://trino.io/docs/current/admin/properties-web-interface.html.

The problem is that when setting web-ui.authentication.type property for both master and worker nodes, the worker nodes cannot start. I'm getting the following errors:

2022-03-28T10:52:08.031Z	ERROR	main	io.trino.server.Server	Configuration is invalid
==========

Errors:

1) Configuration property 'web-ui.authentication.type' was not used
2) Configuration property 'web-ui.user' was not used

The easy solution would be removing the web-ui properties from config.properties on workers, but it looks like it's not easily done on managed cloud environments like Amazon EMR or Google Dataproc.

Wouldn't it make more sense to just ignore web-ui properties in case a node acts as a worker?

@whutpencil
Copy link
Contributor

What's your trino version?

@thereisnospoon
Copy link
Author

thereisnospoon commented Mar 30, 2022

I've tested this on version 360

@dain
Copy link
Member

dain commented Dec 12, 2022

Workers don't run the UI so these configuration properties are not allowed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants