Skip to content
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

Add profile event in hedged requests and change timeout from sec to ms. #21886

Merged
merged 2 commits into from
Mar 19, 2021

Conversation

Avogar
Copy link
Member

@Avogar Avogar commented Mar 18, 2021

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Changelog category (leave one):

  • Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Add profile event HedgedRequestsChangeReplica, change read data timeout from sec to ms.

Detailed description / Documentation draft:
HedgedRequestsChangeReplica event counts the total number of times when a change replica timeout has been alarmed. Change read_data_timeout timeout from sec to ms, add _ms ending to the timeouts. Add better processing the case when max_parallel_replicas > 1 but there is no way to sample data in this query.

… requests and better process receiving packets
@robot-clickhouse robot-clickhouse added the pr-improvement Pull request with some product improvements label Mar 18, 2021
@alexey-milovidov alexey-milovidov added the pr-must-backport Pull request should be backported intentionally. Use this label with great care! label Mar 18, 2021
@@ -4,8 +4,8 @@
<default>
<load_balancing>in_order</load_balancing>
<max_parallel_replicas>2</max_parallel_replicas>
<hedged_connection_timeout>100</hedged_connection_timeout>
<receive_data_timeout>2</receive_data_timeout>
<hedged_connection_timeout_ms>100</hedged_connection_timeout_ms>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one should be increased, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Connection timeout was already in ms.

@akuzm akuzm self-assigned this Mar 18, 2021
@akuzm
Copy link
Contributor

akuzm commented Mar 19, 2021

Many integration tests from test_distributed_respect_user_timeouts are flaky under tsan, can this be related?

https://clickhouse-test-reports.s3.yandex.net/21886/055242fe95d8f8750355fe68d6453e0abc305957/integration_tests_(thread).html#fail1

@Avogar
Copy link
Member Author

Avogar commented Mar 19, 2021

Many integration tests from test_distributed_respect_user_timeouts are flaky under tsan, can this be related?

https://clickhouse-test-reports.s3.yandex.net/21886/055242fe95d8f8750355fe68d6453e0abc305957/integration_tests_(thread).html#fail1

I see the same problem on master, I think it's not related to this PR.

@akuzm
Copy link
Contributor

akuzm commented Mar 19, 2021

OK, let's merge then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-improvement Pull request with some product improvements pr-must-backport Pull request should be backported intentionally. Use this label with great care!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants