You are probably running into https://github.com/FasterXML/jackson-dataformat-smile/issues/18, which was fixed by upgrading jackson in ES with https://github.com/elasticsearch/elasticsearch/pull/7327 (version 1.4.0)
Cheers, Boaz On Tuesday, December 9, 2014 4:11:00 AM UTC+1, Lane Harris wrote: > > Hello all > > We are running Marvel 1.2.1 on ES 1.3.4/Java 1.7.55 with a separate > "logging cluster" that marvel.agent.exporter.es.hosts points to. The > logging cluster is running the same bits as our production cluster > with marvel.agent.enabled set to false. About a week ago, we stopped > seeing events for the "Cluster Pulse" and "Shard Allocation" dashboards. > Whenever one of the events tracked on these dashboards occurs, the current > master spits out the following log message: > > [2014-12-09 02:54:59,220][ERROR][marvel.agent.exporter ] [T02-C01-M03] > remote target didn't respond with 200 OK response code [500 Internal Server > Error]. content: [:) > ?error?JsonParseException[Invalid shared name reference 293; only got 0 > names in buffer (invalid content) > at [Source: > org.elasticsearch.transport.netty.ChannelBufferStreamInput@3fc84b46; line: > -1, column: 4]]?status$ ??] > > On the logging cluster, the relevant types for these pages (node_event, > shard_event, etc) dried up at the same time the errors started appearing in > the logs. I checked the both the Marvel template and the actual mappings - > no differences between the two days. Has anyone seen a similar issue? > > Lane > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/78ae2a44-7900-46c4-ad47-51698455dd76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
