influxdata / influxdata/influxdb

InfluxDB 2.0 - Write failed - storage-engine - unexpected end of JSON input

Open
#22,387 7 comments 1 reaction 0 assignees View on GitHub
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

Hi,

I have a problem with my influxdb (latest version)
I´m running the influx inside of a docker container (azure container instance)
Data is inserted by telegraf.
Everything is fine.

Now I implemented a second telegraf instance which sending the data to a second bucket, same org.

After a few seconds the following log messages appear.
I have no idea where this is coming from.

First of all, who is sending the message "unexpected end of JSON input", and when does this happen?
Is it related to the input data?
Or how can I enhance the debug message?

```
ts=2021-09-03T16:35:22.019827Z lvl=info msg="Series partition compaction (start)" log_id=0WN81wYG000 service=storage-engine partition=0 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/00 op_event=start
ts=2021-09-03T16:35:26.197561Z lvl=info msg="Series partition compaction (end)" log_id=0WN81wYG000 service=storage-engine partition=0 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/00 op_event=end op_elapsed=4177.741ms
ts=2021-09-03T16:35:26.477786Z lvl=info msg="Series partition compaction (end)" log_id=0WN81wYG000 service=storage-engine partition=2 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/02 op_event=end op_elapsed=5379.702ms
ts=2021-09-03T16:35:26.506912Z lvl=info msg="Series partition compaction (end)" log_id=0WN81wYG000 service=storage-engine partition=4 op_name=series_partition_compaction path=/var/lib/influxdb2/engine/data/1360cd9a8ff45dc9/_series/04 op_event=end op_elapsed=4661.029ms
ts=2021-09-03T16:35:46.184542Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T16:35:56.344869Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T16:36:05.670810Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
ts=2021-09-03T16:36:18.987579Z lvl=info msg="Write failed" log_id=0WN81wYG000 service=storage-engine service=write shard=3 error="[shard 3] unexpected end of JSON input"
```

Thx in advance
Martin

Contributor guide

Open the contributing guide

Research direction

Start with the storage-engine write path and the shard 3 failures shown in the logs. Reproduce the setup with a second Telegraf instance writing to a second bucket in the same organization, then trace where the unexpected end of JSON input originates. Done means the source is identified and the issue has an actionable fix or diagnostic improvement.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, docker
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.