{"action":"created","issue":{"url":"https://api.github.com/repos/influxdb/influxdb/issues/3597","labels_url":"https://api.github.com/repos/influxdb/influxdb/issues/3597/labels{/name}","comments_url":"https://api.github.com/repos/influxdb/influxdb/issues/3597/comments","events_url":"https://api.github.com/repos/influxdb/influxdb/issues/3597/events","html_url":"https://github.com/influxdb/influxdb/issues/3597","id":99899535,"number":3597,"title":"influxd db 9.2 takes too long to start ","user":{"login":"FarzinZaker","id":3818476,"avatar_url":"https://avatars.githubusercontent.com/u/3818476?v=3","gravatar_id":"","url":"https://api.github.com/users/FarzinZaker","html_url":"https://github.com/FarzinZaker","followers_url":"https://api.github.com/users/FarzinZaker/followers","following_url":"https://api.github.com/users/FarzinZaker/following{/other_user}","gists_url":"https://api.github.com/users/FarzinZaker/gists{/gist_id}","starred_url":"https://api.github.com/users/FarzinZaker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/FarzinZaker/subscriptions","organizations_url":"https://api.github.com/users/FarzinZaker/orgs","repos_url":"https://api.github.com/users/FarzinZaker/repos","events_url":"https://api.github.com/users/FarzinZaker/events{/privacy}","received_events_url":"https://api.github.com/users/FarzinZaker/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-08-09T14:13:17Z","updated_at":"2015-08-13T20:50:48Z","closed_at":null,"body":"when starting influxdb service, it **starts filling memory to reach upper than 12GB very slowly**. during startup time, cpu usage is 100%. then starts responding on port 8086! before reaching this amount of memory usage no one is listening on port 8086.\r\n\r\nThere is no way to limit memory usage of influxdb currenty. some times influxdb stops responding to write post messages for about 1hour, so I need to restart influxdb service periodically which takes about 2 hours!!!\r\n\r\nwhat is the problem?\r\n\r\nThanks in advance\r\n\r\nThis is my **data folder size**:\r\n11441272        data/\r\n\r\nI have installed influxdb 9.2 on **Red Hat Enterprise Linux Server release 6.4 (Santiago)** using instructions provided in https://influxdb.com/docs/v0.9/introduction/installation.html \r\n\r\nthis is my **influxdb.config** content\r\n\r\n```\r\n### Welcome to the InfluxDB configuration file.\r\n\r\n# Once every 24 hours InfluxDB will report anonymous data to m.influxdb.com\r\n# The data includes raft id (random 8 bytes), os, arch, version, and metadata.\r\n# We don't track ip addresses of servers reporting. This is only used\r\n# to track the number of instances running and the versions, which\r\n# is very helpful for us.\r\n# Change this option to true to disable reporting.\r\nreporting-disabled = false\r\n\r\n###\r\n### [meta]\r\n###\r\n### Controls the parameters for the Raft consensus group that stores metadata\r\n### about the InfluxDB cluster.\r\n###\r\n\r\n[meta]\r\n  dir = \"/var/opt/influxdb/meta\"\r\n  hostname = \"localhost\"\r\n  bind-address = \":8088\"\r\n  retention-autocreate = true\r\n  election-timeout = \"1s\"\r\n  heartbeat-timeout = \"1s\"\r\n  leader-lease-timeout = \"500ms\"\r\n  commit-timeout = \"50ms\"\r\n\r\n###\r\n### [data]\r\n###\r\n### Controls where the actual shard data for InfluxDB lives and how it is\r\n### flushed from the WAL. \"dir\" may need to be changed to a suitable place\r\n### for your system, but the WAL settings are an advanced configuration. The\r\n### defaults should work for most systems.\r\n###\r\n\r\n[data]\r\n  dir = \"/var/opt/influxdb/data\"\r\n  max-wal-size = 104857600 # Maximum size the WAL can reach before a flush. Defaults to 100MB.\r\n  wal-flush-interval = \"10m\" # Maximum time data can sit in WAL before a flush.\r\n  wal-partition-flush-delay = \"2s\" # The delay time between each WAL partition being flushed.\r\n\r\n###\r\n### [cluster]\r\n###\r\n### Controls non-Raft cluster behavior, which generally includes how data is\r\n### shared across shards.\r\n###\r\n\r\n[cluster]\r\n  shard-writer-timeout = \"5s\" # The time within which a shard must respond to write.\r\n  write-timeout = \"5s\" # The time within which a write operation must complete on the cluster.\r\n\r\n###\r\n### [retention]\r\n###\r\n### Controls the enforcement of retention policies for evicting old data.\r\n###\r\n\r\n[retention]\r\n  enabled = true\r\n  check-interval = \"10m\"\r\n\r\n###\r\n### [admin]\r\n###\r\n### Controls the availability of the built-in, web-based admin interface. If HTTPS is\r\n### enabled for the admin interface, HTTPS must also be enabled on the [http] service.\r\n###\r\n\r\n[admin]\r\n  enabled = true\r\n  bind-address = \":8083\"\r\n  https-enabled = false\r\n  https-certificate = \"/etc/ssl/influxdb.pem\"\r\n\r\n###\r\n### [http]\r\n###\r\n### Controls how the HTTP endpoints are configured. These are the primary\r\n### mechanism for getting data into and out of InfluxDB.\r\n###\r\n\r\n[http]\r\n  enabled = true\r\n  bind-address = \":8086\"\r\n  auth-enabled = false\r\n  log-enabled = true\r\n  write-tracing = false\r\n  pprof-enabled = false\r\n  https-enabled = false\r\n  https-certificate = \"/etc/ssl/influxdb.pem\"\r\n\r\n###\r\n### [[graphite]]\r\n###\r\n### Controls one or many listeners for Graphite data.\r\n###\r\n\r\n[[graphite]]\r\n  enabled = false\r\n  # bind-address = \":2003\"\r\n  # protocol = \"tcp\"\r\n  # consistency-level = \"one\"\r\n  # name-separator = \".\"\r\n\r\n  ## \"name-schema\" configures tag names for parsing the metric name from graphite protocol;\r\n  ## separated by `name-separator`.\r\n  ## The \"measurement\" tag is special and the corresponding field will become\r\n  ## the name of the metric.\r\n  ## e.g. \"type.host.measurement.device\" will parse \"server.localhost.cpu.cpu0\" as\r\n  ## {\r\n  ##     measurement: \"cpu\",\r\n  ##     tags: {\r\n  ##         \"type\": \"server\",\r\n  ##         \"host\": \"localhost,\r\n  ##         \"device\": \"cpu0\"\r\n  ##     }\r\n  ## }\r\n  # name-schema = \"type.host.measurement.device\"\r\n\r\n  ## If set to true, when the input metric name has more fields than `name-schema` specified,\r\n  ## the extra fields will be ignored.\r\n  ## Otherwise an error will be logged and the metric rejected.\r\n  # ignore-unnamed = true\r\n\r\n###\r\n### [collectd]\r\n###\r\n### Controls the listener for collectd data.\r\n###\r\n\r\n[collectd]\r\n  enabled = false\r\n  # bind-address = \"\"\r\n  # database = \"\"\r\n  # typesdb = \"\"\r\n\r\n###\r\n### [opentsdb]\r\n###\r\n### Controls the listener for OpenTSDB data.\r\n###\r\n\r\n[opentsdb]\r\n  enabled = false\r\n  # bind-address = \"\"\r\n  # database = \"\"\r\n  # retention-policy = \"\"\r\n\r\n###\r\n### [udp]\r\n###\r\n### Controls the listener for InfluxDB line protocol data via UDP.\r\n###\r\n\r\n[udp]\r\n  enabled = false\r\n  # bind-address = \"\"\r\n  # database = \"\"\r\n  # batch-size = 0\r\n  # batch-timeout = \"0\"\r\n\r\n###\r\n### [monitoring]\r\n###\r\n\r\n[monitoring]\r\n  enabled = true\r\n  write-interval = \"24h\"\r\n\r\n###\r\n### [continuous_queries]\r\n###\r\n### Controls how continuous queries are run within InfluxDB.\r\n###\r\n\r\n[continuous_queries]\r\n  enabled = true\r\n  recompute-previous-n = 2\r\n  recompute-no-older-than = \"10m\"\r\n  compute-runs-per-interval = 10\r\n  compute-no-more-than = \"2m\"\r\n\r\n###\r\n### [hinted-handoff]\r\n###\r\n### Controls the hinted handoff feature, which allows nodes to temporarily\r\n### store queued data when one node of a cluster is down for a short period\r\n### of time.\r\n###\r\n\r\n[hinted-handoff]\r\n  enabled = true\r\n  dir = \"/var/opt/influxdb/hh\"\r\n  max-size = 1073741824\r\n  max-age = \"168h\"\r\n  retry-rate-limit = 0\r\n  retry-interval = \"1s\"\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/influxdb/influxdb/issues/comments/130838860","html_url":"https://github.com/influxdb/influxdb/issues/3597#issuecomment-130838860","issue_url":"https://api.github.com/repos/influxdb/influxdb/issues/3597","id":130838860,"user":{"login":"FarzinZaker","id":3818476,"avatar_url":"https://avatars.githubusercontent.com/u/3818476?v=3","gravatar_id":"","url":"https://api.github.com/users/FarzinZaker","html_url":"https://github.com/FarzinZaker","followers_url":"https://api.github.com/users/FarzinZaker/followers","following_url":"https://api.github.com/users/FarzinZaker/following{/other_user}","gists_url":"https://api.github.com/users/FarzinZaker/gists{/gist_id}","starred_url":"https://api.github.com/users/FarzinZaker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/FarzinZaker/subscriptions","organizations_url":"https://api.github.com/users/FarzinZaker/orgs","repos_url":"https://api.github.com/users/FarzinZaker/repos","events_url":"https://api.github.com/users/FarzinZaker/events{/privacy}","received_events_url":"https://api.github.com/users/FarzinZaker/received_events","type":"User","site_admin":false},"created_at":"2015-08-13T20:50:48Z","updated_at":"2015-08-13T20:50:48Z","body":"would disabling new shard creation on every 10 minutes help?"}}