Watcher and Head Plugin

alerting

(Peter Colclough) #1

Hi there,

Got watcher installed, but my favourite admin tool Head, is partially broke.

  1. Seams that the second Replicas shards are always in 'start mode' (going off to check the reality of that)
  2. The 'Browser' tab does not function at all... which is a real shame.

Also, it may be worthwhile mentioning that watcher requires ES 1.5.n , which in turn requires Java 8, if I remember correctly. This would have saved a bit f time on the setup process.


(Mark Walkom) #2

Watcher does need ES 1.5 or above, however ES 1.5 will run on Java 1.7, see the supported version matrix.

It seems unlikely that it would break Head though given they are separate plugins.


(Peter Colclough) #3

Yep.. right. I realise that.
I did add the relevant JAVA_OPTS values for 17 compatibility. I also upgraded to 1.5.2 ES. What seemed to be part of the issue, some part of this reset the 'number of replicas' to 1 on the second node I updated. Weird.. but fixed. The Browser part of head doesn't work still... but that cold be a local issue...

However, in amonst all my installing an uninstalling, I now have a .watches index that cant be deleted, but the watcher index has been deleted.
So I now get a
curl -XGET 'http://awse-devmysqlproxy01:9200/_watcher/stats?pretty'
{
"error" : "LicenseExpiredException[license expired for feature [watcher]]",
"status" : 401
}
error. Has this been reported already. Seems that the plugin cant access the watcher index (because it isn't there)... but also cant install it, because the .watches index wont go either.

I am feeling a tad foolish... which is not normal for me :frowning:


(Peter Colclough) #4

Ok.. I am there now... (Head/Browser/ still not firing.. but I can live without that). The watcher LicenseKey issue came down to not having Watcher installed on all nodes (2 node cluster). So all Ok and working fine... so I can start testing now... phew!


(system) #5