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

Cluster pending tasks always uses default master_timeout parameter #4806

Closed
javanna opened this issue Jan 20, 2014 · 0 comments
Closed

Cluster pending tasks always uses default master_timeout parameter #4806

javanna opened this issue Jan 20, 2014 · 0 comments
Assignees
@javanna
Labels
>enhancement v1.0.0

Comments

@javanna
Copy link
Member

javanna commented Jan 20, 2014

The cluster pending tasks doesn't read the input master_timeout parameter from the REST layer, although it allows to set the masterNodeTimeout through Java API.

As a result, when using the REST layer the default master_timeout (30 seconds) is always used.
@ghost ghost assigned javanna Jan 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@javanna javanna

Labels
>enhancement v1.0.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@javanna