[ 
https://issues.apache.org/jira/browse/METRON-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347207#comment-15347207
 ] 

Nick Allen commented on METRON-243:
-----------------------------------

I have a working theory on this one. 

The 'elasticsearch' role installs Elasticsearch on each node in the 'search' 
host group.  After installation, Elasticsearch is not yet started.

In the next step, the 'metron_elasticsearch_templates' role uses Ansible's 
'run_once' functionality.  The effect of using 'run_once' is that Ansible 
chooses a single node in the 'search' host group; let's call this host ES1.  
Only on ES1, Elasticsearch is started, the index templates are installed, and 
then the index templates are validated.  We effectively have a single node 
Elasticsearch cluster at this point.

After all components have been installed, the 'monit-start' role ensures that 
all services are stopped across the cluster.  At this point the single-node 
Elasticsearch cluster, which was left running, is shutdown.  The 'monit-start' 
role then determines which services need  started and starts them.  At this 
point all of the Elasticsearch nodes are started which creates a multi-node 
cluster.

If ES1 is elected master, then the index template that was previously 
configured is propagated to the other nodes in the cluster.
If ES1 is not elected master, then the index template is forgotten as the 
master knows nothing about those index templates.

This explains why it occurs *sometimes*, but not all the time.
This would also explain why the problem never occurs on Vagrant deployments.


> Kibana Error - [unsupported_operation_exception] custom format isn't supported
> ------------------------------------------------------------------------------
>
>                 Key: METRON-243
>                 URL: https://issues.apache.org/jira/browse/METRON-243
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Nick Allen
>
> When using Metron's default dashboard in Kibana 4, the following error 
> message is sometimes shown at the top of the page.
> Error: [unsupported_operation_exception] custom format isn't supported



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to