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

clickhouse write s3 exception #48336

Closed
liugs0213 opened this issue Apr 3, 2023 · 1 comment
Closed

clickhouse write s3 exception #48336

liugs0213 opened this issue Apr 3, 2023 · 1 comment
Labels
potential bug To be reviewed by developers and confirmed/rejected.

Comments

@liugs0213
Copy link

You have to provide the following information whenever possible.
Describe what's wrong
Execute sql: alter table dataset_v4_test_all_2 move partition '202302' to disk 'arch';
image

The table contains 5000 columns and has about 8 GB partitions. Net Exception: Cannot assign requested address: An exception occurs when data is moved from the nvme to s3
Exception cause: This parameter must occur when the number of tcp connections reaches 28283
image
image

I want to know if there's a way to control the number of concurrent requests

A clear and concise description of what works not as it is supposed to.

A link to reproducer in https://fiddle.clickhouse.com/.

Does it reproduce on recent release?

The list of releases

Enable crash reporting

If possible, change "enabled" to true in "send_crash_reports" section in config.xml:

<send_crash_reports>
        <!-- Changing <enabled> to true allows sending crash reports to -->
        <!-- the ClickHouse core developers team via Sentry https://sentry.io -->
        <enabled>false</enabled>

How to reproduce

  • Which ClickHouse server version to use
  • Which interface to use, if matters
  • Non-default settings, if any
  • CREATE TABLE statements for all tables involved
  • Sample data for all these tables, use clickhouse-obfuscator if necessary
  • Queries to run that lead to unexpected result

Expected behavior

A clear and concise description of what you expected to happen.

Error message and/or stacktrace

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

@liugs0213 liugs0213 added the potential bug To be reviewed by developers and confirmed/rejected. label Apr 3, 2023
@Algunenano
Copy link
Member

There have been multiple improvements in connection to s3 in 24.4 by @CheSema (like #62249). Updating and testing with this version is recommended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
potential bug To be reviewed by developers and confirmed/rejected.
Projects
None yet
Development

No branches or pull requests

2 participants