Skip to content

300: Added per-statement and per-batch request timeouts#297

Merged
mikefero merged 3 commits intomasterfrom
300
Jun 20, 2016
Merged

300: Added per-statement and per-batch request timeouts#297
mikefero merged 3 commits intomasterfrom
300

Conversation

@mpenick
Copy link
Copy Markdown
Contributor

@mpenick mpenick commented Jun 10, 2016

No description provided.

Comment thread src/handler.cpp

uint64_t Handler::request_timeout_ms(const Config& config) const {
uint64_t request_timeout_ms = request_->request_timeout_ms();
if (request_timeout_ms == CASS_UINT64_MAX) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

0 might be better than CASS_UINT64_MAX to set assign the default cluster configuration timeout.

uv_start_timer indicates:

If timeout is zero, the callback fires on the next event loop iteration. If repeat is non-zero, the callback fires first after timeout milliseconds and then repeatedly after repeat milliseconds.

Reason being is a user might want to set the max timeout in order to "wait forever" and might by default set that value to the max.

@mikefero
Copy link
Copy Markdown
Contributor

Besides the one comment; 👍

Michael Penick added 2 commits June 13, 2016 09:13
 0 means no timeout and CASS_UINT64_MAX means use the cluster-level request timeout (default). Added header documentation to clarify.
@mikefero mikefero merged commit dbd9279 into master Jun 20, 2016
@mpenick mpenick deleted the 300 branch June 21, 2016 17:16
mikefero added a commit that referenced this pull request Oct 25, 2019
CPP-818 - Add configuration properties to Insights startup message
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants