-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix TASK_SCALE_WRITERS_MAX_WRITER_COUNT in test #18276
Conversation
It relates to #18005 |
32ad7a6
to
323f7b5
Compare
@@ -61,7 +63,10 @@ protected void assertJdbcConnections(@Language("SQL") String query, int expected | |||
assertQueryFails(query, errorMessage.get()); | |||
} | |||
else { | |||
getQueryRunner().execute(query); | |||
Session querySession = Session.builder(getSession()) | |||
.setSystemProperty(TASK_SCALE_WRITERS_MAX_WRITER_COUNT, "4") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: add a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kokosing To disable scaling it might be better to set task_scale_writers_enabled
to false
.
https://trino.io/docs/current/admin/properties-writer-scaling.html#task-scale-writers-enabled
If this session property is not fixed then running this locally most likely will fail as number of writers depends on number of CPUs and so expected number of created connections will be different.
323f7b5
to
1844cd0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Fix TASK_SCALE_WRITERS_MAX_WRITER_COUNT in test
If this session property is not fixed then running this locally most
likely will fail as number of writers depends on number of CPUs and so
expected number of created connections will be different.