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

Allow PointerWriter timeout to be configurable #3218

Merged
merged 3 commits into from
Jul 2, 2015
Merged

Conversation

otoolep
Copy link
Contributor

@otoolep otoolep commented Jul 2, 2015

This change makes the time the system will wait for the write to complete, across the cluster, configurable. Previously this was hardcoded to 5 seconds

@otoolep otoolep force-pushed the config_timeouts branch 2 times, most recently from 286215f to a24e287 Compare July 2, 2015 16:45
@otoolep
Copy link
Contributor Author

otoolep commented Jul 2, 2015

@jwilder @dgnorton @pauldix

@otoolep
Copy link
Contributor Author

otoolep commented Jul 2, 2015

Looking into test failures.

@otoolep
Copy link
Contributor Author

otoolep commented Jul 2, 2015

Green build, was missing a required change to the tests.

@dgnorton
Copy link
Contributor

dgnorton commented Jul 2, 2015

+1

@@ -48,7 +48,8 @@ reporting-disabled = false
###

[cluster]
shard-writer-timeout = "5s"
shard-writer-timeout = "5s" # The time within which a shard must respond to write.
Copy link
Member

Choose a reason for hiding this comment

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

is this for a local shard? If so it seems this should be in the data section and not cluster

otoolep added a commit that referenced this pull request Jul 2, 2015
Allow PointerWriter timeout to be configurable
@otoolep otoolep merged commit ffae1c9 into master Jul 2, 2015
@otoolep otoolep deleted the config_timeouts branch August 18, 2015 20:47
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.

3 participants