Tribenode masternotdiscoveredexception

Elastic Stack Elasticsearch
1

Hi,

I'm trying to set up a tribe node to look at clusters in different datacenters. When I hook up kibana and try to add visualization or a dashboard i keep hitting:

Kibana: MasterNotDiscoveredException[waited for [30s]]
Error: MasterNotDiscoveredException[waited for [30s]]
ErrorAbstract@http://host.domain.com:5601/index.js?_b=7562:83947:28
StatusCodeError@http://host.domain.com:5601/index.js?_b=7562:84096:23
respond@http://host.domain.com:5601/index.js?_b=7562:85289:33
checkRespForFailure@http://host.domain.com5601/index.js?_b=7562:85257:14
http://host.domain.com:5601/index.js?_b=7562:83895:9
wrappedErrback@http://host.domain.com:5601/index.js?_b=7562:20902:78
wrappedErrback@http://host.domain.com:5601/index.js?_b=7562:20902:78
wrappedErrback@http://host.domain.com:5601/index.js?_b=7562:20902:78
http://host.domain.com:5601/index.js?_b=7562:21035:76
$eval@http://host.domain.com:5601/index.js?_b=7562:22022:28
$digest@http://host.domain.com:5601/index.js?_b=7562:21834:36
$apply@http://host.domain.com:5601/index.js?_b=7562:22126:31
done@http://host.domain.com:5601/index.js?_b=7562:17661:51
completeRequest@http://host.domain.com:5601/index.js?_b=7562:17875:15
onreadystatechange@http://host.domain.com:5601/index.js?_b=7562:17814:26

One time I had the tribenode indexing to it's local cluster master (becuase it was hooked up as a regular kibana node), but then the next day it went back to having no master.

is there a step that i'm missing?
here is my elasticsearch.yml:
node:
data: false
master: false
name: host.domain.com
path:
data: /spotify/var/elasticsearch
logs: /spotify/log/elasticsearch
tribe:
on_conflict: perfer_tribe-sjc1
tribe-ash2:
cluster:
name: cluster-ash2
discovery:
zen:
ping:
multicast:
enabled: false
unicast:
hosts:
- list of hosts
tribe-lon6:
cluster:
name: cluster-lon6
discovery:
zen:
ping:
multicast:
enabled: false
unicast:
hosts:
- list of hosts

tribe-sjc1:
cluster:
name: cluster-sjc1
discovery:
zen:
ping:
multicast:
enabled: false
unicast:
hosts:
- list of hosts
tribe-sto3:
cluster:
name: cluster-sto3
discovery:
zen:
ping:
multicast:
enabled: false
unicast:
hosts:
- list of hosts

2

Tribe node can not create indices. It can only update them. So you will have to precreate kibana index -- .kibana in one of your downstream clusters.

Tin

3

I did that. and it initially worked, but the next day, it stopped working. the name of the index didn't change.

4

What version of ES? Did you create the kibana index in one downstream or all of them?

It might help to use tribe prefer config to control where it look for your tribe kibana index from. It's a pain..... :tired_face:

5

OH actually I think i fixed it. Puppet wrote over my kibana index and changed it. I was working off a branch before and it looks like the master overwrote it. GAH!

So hopefully this will be ok going forward.

thanks for replying!