Tribe nodes in ES 2.2.0 breaks plugins

Unless you use the build that has the fix for the reported github reference, I think you'll still need to put in the path.* for plugins, even though it's been said "you dont have to".

When you have kibana and/or marvel running with the tribe node setup, on startup, kibana does not know which cluster it should create .kibana (default) index. The link to a post below has a reference link describing what could be done.

The new version of marvel needs kibana and it needs to create .marvel- indices. The same issue here, it needs to know which cluster it should drop the daily index. I think by creating or using a separate "monitoring cluster", following the instructions at the link below, the marvel issue can be solved. I've not done this but I think it will help addressing the issue.