-
Notifications
You must be signed in to change notification settings - Fork 25.9k
String settings leniently accept lists #33135
Copy link
Copy link
Open
Labels
:Core/Infra/SettingsSettings infrastructure and APIsSettings infrastructure and APIs>bugTeam:Core/InfraMeta label for core/infra teamMeta label for core/infra teamgood first issuelow hanging fruitlow hanging fruitteam-discusstriagedIssue has been looked at, and is being left openIssue has been looked at, and is being left open
Metadata
Metadata
Assignees
Labels
:Core/Infra/SettingsSettings infrastructure and APIsSettings infrastructure and APIs>bugTeam:Core/InfraMeta label for core/infra teamMeta label for core/infra teamgood first issuelow hanging fruitlow hanging fruitteam-discusstriagedIssue has been looked at, and is being left openIssue has been looked at, and is being left open
Type
Fields
Give feedbackNo fields configured for issues without a type.
If you got here from the
good first issuelabel, see this comment.For example, the following
elasticsearch.yml...... starts up a node called
[node-a, node-b]:In fact this is what's happening in #30946. The following API call...
... sets
cluster.routing.allocation.exclude._nameto the string[elasticsearch-data-0], which then does not match the node calledelasticsearch-data-0so the allocation is not filtered as expected.