Where the length limitation comes from or is set up?

[evgueni (Eugene Gordienko)]

Hi,

Getting this message:

ERROR [Messages] Failed to index [1] messages. Please check the index error log in your web interface for the reason. Error: failure in bulk execution:
[7]: index [graylog_58], type [message], id [0ee956f1-f94d-11e6-a259-080027c05c11], message [java.lang.IllegalArgumentException: Document contains at least one immense term in field="msg" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped.  Please correct the analyzer to not produce such terms.  The prefix of the first immense term 

Where the limitation 32766 comes from?

Thanks,
Eugene

[jochen]

Wow, no idea where all of these are coming from today, but please refer to these topics:

Identify source and reason of bad messages

We are constantly getting errors logged in the Graylog server log indicating there are messages failing to be processed… Theses errors are what I’m seeing. How do I look up where they are coming from and why Graylog is not able to process them? 2017-02-22 12:05:52,271 ERROR: org.graylog2.indexer.messages.Messages - Failed to index [1] messages. Please check the index error log in your web interface for the reason. Error: failure in bulk execution: [355]: index [graylog_8832], type [messag…

Beats Input - bytes can be at most 32766 in length

Hi Guys I’ve deployed Graylog to use for a syslog solution. Currently using Sidecar to do the collections of winlogs only. Been running a week and started loading some more hosts … Then Pooooooof, graylog fell over. Initially I was clueless as to whats going on. After a bit of digging, I found the dreaded elasticsearch error which seems to be quite common ( bytes can be at most 32766 in length) I have found a few articles where people say update the analyser, some others that mention set…