You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Basho-JIRA
changed the title
Inconsistent timeout methodologies on operations
Inconsistent timeout methodologies on operations [JIRA: CLIENTS-561]
Aug 28, 2015
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.
The text was updated successfully, but these errors were encountered: