Thanks to visit codestin.com
Credit goes to github.com

Skip to content

dsosql Alternative Fail for a Missing Cluster #74

@bschwal

Description

@bschwal

When trying to use dsosql I have a cluster configuration file which directs the query to search across several nodes. If one of these nodes is down, the query will fail with something like:

Attaching to cluster ...Error creating client 12
The cluster defined in '' is not available

I would prefer that the query give a notification that there is a cluster it is unable to communicate with and then continue the query on nodes it can communicate with. Currently, I need to change all of my configuration files manually if a node goes down even though maestro is rebalancing the sets to non-down nodes.

Could we add an option for the query to do this? Doesn't necessarily need to be default behavior.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions