Elasticsearch:no known master node

A single Elasticsearch cluster, if the following exception occurs:
You need to change the Node.master:false configuration to node.master:true

[2017-09-22 09:03:15,558] [DEBUG] [Action.admin.indices.create] [TSB] No known master node, scheduling a retry [2017-09-22 09:03:21,572][debug][ Action.admin.indices.create] [TSB] observer:timeout notification from Cluster service. Timeout setting [1m], time since start [1m] [2017-09-22 09:03:21,582][debug][action.admin.indices.create] [TSB] no known m
Aster node, scheduling a retry [2017-09-22 09:03:45,747][info][node] [TSB] stopping ... [2017-09-22 09:03:45,792] [INFO] [Node]
[TSB] stopped [2017-09-22 09:03:45,792][info][node] [TSB] closing ... [2017-09-22 09:03:45,799] [INFO] [Node] [TSB] closed [2017-09-22 09:03:48,249][info][node] [TSB] version[1.7.3], pid[12449], BUILD[05D4530/2
015-10-15t09:14:17z] [2017-09-22 09:03:48,250][info][node] [TSB] initializing ... [2017-09-22 09:03:48,326] [INFO] [Plugins] [TSB] loaded [], sites [head] [2017-09-22 09:03:50,171][warn][script] [TSB] deprecated setting [script.disable_dynamic] is set, replace with F                     ine-grained scripting settings (e.g. Script.inline, script.indexed, script.file) [2017-09-22 09:03:50,349][info][node
] [TSB] initialized [2017-09-22 09:03:50,349][info][node] [TSB] starting ... [2017-09-22 09:03:50,507] [INFO] [Transport] [TSB] bound_address {inet[/0.0.0.0:9300]}, publish_address {inet[/100.126.151.40:9300]} [2017-09-22 09:03:50,518][ INFO][discovery] [TSB] TSB-BIGDATA/9MOKQPURSUWRQGKY7DBRCG [2017-09-22 09:04:05,573][debug][action.admin.i Ndices.create] [TSB] No known master node, scheduling a retry [2017-09-22 09:04:11,556][debug][ Action.admin.indices.create] [TSB] No known master node, scheduling a retry