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

Inconsistent timeout methodologies on operations [JIRA: CLIENTS-561] #228

Open
nerophon opened this issue Aug 28, 2015 · 0 comments
Open

Comments

@nerophon
Copy link

From customer ticket 11806:

get/put/delete/list_keys etc can all take Timeout as an argument when invoking the operations.

fetch_type, update_type etc does not. Instead they rely on application configuration in riakc with keys 'put_timeout' and 'get_timeout'. if these are not found it will silently fallback on using hard coded macro timeout of 60 seconds (see default_timeout/1 in riakc_pb_socket).

This opens up to potential configuration errors where one needs to make sure all sys.configs set 'get_timeout' and 'put_timeout' accordingly; otherwise one would see very different characteristics of nodes in production and it wouldn't be noticed since they silently use hard coded default values as fallback.

@nerophon nerophon added the Issue label Aug 28, 2015
@Basho-JIRA Basho-JIRA changed the title Inconsistent timeout methodologies on operations Inconsistent timeout methodologies on operations [JIRA: CLIENTS-561] Aug 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants