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

Align azure timeout with s3 #1487

Merged
merged 1 commit into from
Apr 16, 2024
Merged

Align azure timeout with s3 #1487

merged 1 commit into from
Apr 16, 2024

Conversation

phoebusm
Copy link
Collaborator

Reference Issues/PRs

Fix #1026

What does this implement or fix?

Azure timeout has been incorrectly set to 60000ms. It needs to be addressed

Any other comments?

Checklist

Checklist for code changes...
  • Have you updated the relevant docstrings, documentation and copyright notice?
  • Is this contribution tested against all ArcticDB's features?
  • Do all exceptions introduced raise appropriate error messages?
  • Are API changes highlighted in the PR description?
  • Is the PR labelled as enhancement or bug so it appears in autogenerated release notes?

@phoebusm phoebusm added the bug Something isn't working label Apr 10, 2024
@phoebusm phoebusm self-assigned this Apr 10, 2024
@phoebusm phoebusm requested a review from poodlewars April 10, 2024 17:07
@@ -362,7 +362,7 @@ AzureStorage::AzureStorage(const LibraryPath &library_path, OpenMode mode, const
} else
ARCTICDB_RUNTIME_DEBUG(log::storage(), "Azure prefix not found, will use {}", root_folder_);
unsigned int max_connections = conf.max_connections() == 0 ? ConfigsMap::instance()->get_int("VersionStore.NumIOThreads", 16) : conf.max_connections();
upload_option_.TransferOptions.Concurrency = max_connections;
upload_option_.TransferOptions.Concurrency = max_connections;
Copy link
Collaborator

Choose a reason for hiding this comment

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

?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sorry it doesn't show up in my diff. 😢

Copy link
Collaborator

@poodlewars poodlewars left a comment

Choose a reason for hiding this comment

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

As discussed this is fine for now but I think we should actually drop the timeout completely - there are quite a few cases where a request might read a very large object and timeout.

@phoebusm phoebusm force-pushed the fix/increase_azure_timeout branch from 55ba79e to 15857f8 Compare April 15, 2024 09:16
@phoebusm phoebusm merged commit ff7e7b1 into master Apr 16, 2024
114 checks passed
@phoebusm phoebusm deleted the fix/increase_azure_timeout branch April 16, 2024 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reading data from Azure Blob occasionally causes InternalExeption
2 participants