influxdata / influxdata/influxdb

OOM Error and influxDB restart issue

Open
#17,797 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

Hi Team,

We are getting OOM error but sufficient memory is showing on server and Influx service restart issue and please suggest :-

Error:-
Apr 20 18:43:14 N2VL-PA-INFL04 kernel: influxd invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
Apr 20 18:43:14 N2VL-PA-INFL04 kernel: [] oom_kill_process+0x254/0x3d0
Apr 20 18:43:14 N2VL-PA-INFL04 kernel: [] ? oom_unkillable_task+0xcd/0x120
Apr 20 18:43:14 N2VL-PA-INFL04 kernel: [ pid ] uid tgid total_vm rss nr_ptes swapents oom_score_adj name

[root@N2VL-PA-INFL04 ~]# free -h
total used free shared buff/cache available
Mem: 62G 38G 340M 33M 23G 23G
Swap: 3.9G 251M 3.7G

OS version :- Red Hat Enterprise Linux Server release 7.6 (Maipo
InfluxDb :- influxdb-1.8.0-1.x86_64

Contributor guide

Open the contributing guide

Research direction

The report provides kernel OOM logs, `free -h` output, RHEL 7.6, and InfluxDB 1.8.0, but no source file, test, or entry point. Start by examining the OOM event and InfluxDB restart behavior against the reported memory state; done would require a confirmed cause and a documented, reproducible remediation.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
databases, operating-systems
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.