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.

Sign up for GitHub

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

Jump to bottom

Schema update tool needs to have an option to configure request timeout #897

Closed
samarabbas opened this issue Jun 26, 2018 · 0 comments
Closed

Schema update tool needs to have an option to configure request timeout #897

samarabbas opened this issue Jun 26, 2018 · 0 comments
Labels
serviceability Improvements to servicing of Cadence Server stability Server stability issues

Comments

@samarabbas
Copy link
Contributor

Schema update tool uses a fixed timeout on 1 minute. We already see applying schema updates could take longer on big size cluster. So we need a way to pass in bigger timeouts when applying schema changes to such clusters.
@samarabbas samarabbas added stability Server stability issues serviceability Improvements to servicing of Cadence Server labels Jun 26, 2018
samarabbas added a commit to samarabbas/cadence that referenced this issue Jun 27, 2018
@samarabbas
Schema Tool option to configure request timeout for cql client
a521dd7 
fixes cadence-workflow#897
@samarabbas samarabbas mentioned this issue Jun 27, 2018
Merged
samarabbas added a commit to samarabbas/cadence that referenced this issue Jun 27, 2018
@samarabbas
Schema Tool option to configure request timeout for cql client
b3b54d6 
fixes cadence-workflow#897
samarabbas added a commit that referenced this issue Jun 27, 2018
@samarabbas
Schema Tool option to configure request timeout for cql client (#900)
d3e8f10 
fixes #897
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
serviceability Improvements to servicing of Cadence Server stability Server stability issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@samarabbas