Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

json_parse_exception Numeric value out of range of long #21728

Closed
max0x7ba opened this issue Nov 22, 2016 · 1 comment
Closed

json_parse_exception Numeric value out of range of long #21728

max0x7ba opened this issue Nov 22, 2016 · 1 comment

Comments

@max0x7ba
Copy link

Elasticsearch version:
elasticsearch-5.0.0
metricbeat-5.0.1

Plugins installed:
None

JVM version:
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

OS version:
Red Hat Enterprise Linux Server release 6.8 (Santiago) x86_64

Description of the problem including expected versus actual behavior:
Metricbeat sends system.filesystem.files field with value of 18446744073709551615, which is (2^64 - 1).

Steps to reproduce:

  1. Enable metricset filesystem in metricbeat.modules -> module: system,
  2. Start metricbeat.
  3. Observe the warning in the log.

Provide logs (if relevant):
2016-11-22T05:35:17-05:00 WARN Can not index event (status=400): {"type":"mapper_parsing_exception","reason":"failed to parse [system.filesystem.files]","caused_by":{"type":"json_parse_exception","reason":"Numeric value (18446744073709551615) out of range of long (-9223372036854775808 - 9223372036854775807)\n at [Source: org.elasticsearch.common.bytes.BytesReference$MarkSupportingStreamInputWrapper@39fece1e; line: 1, column: 234]"}}

@clintongormley
Copy link

Hi @max0x7ba

This looks like an issue that should be opened on the metrics beat repo. Elasticsearch doesn't have support for unsigned longs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants