{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/logstash/issues/4000","repository_url":"https://api.github.com/repos/elastic/logstash","labels_url":"https://api.github.com/repos/elastic/logstash/issues/4000/labels{/name}","comments_url":"https://api.github.com/repos/elastic/logstash/issues/4000/comments","events_url":"https://api.github.com/repos/elastic/logstash/issues/4000/events","html_url":"https://github.com/elastic/logstash/issues/4000","id":110309659,"number":4000,"title":"Add byte-based flush setting for ES","user":{"login":"drewr","id":6202,"avatar_url":"https://avatars.githubusercontent.com/u/6202?v=3","gravatar_id":"","url":"https://api.github.com/users/drewr","html_url":"https://github.com/drewr","followers_url":"https://api.github.com/users/drewr/followers","following_url":"https://api.github.com/users/drewr/following{/other_user}","gists_url":"https://api.github.com/users/drewr/gists{/gist_id}","starred_url":"https://api.github.com/users/drewr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drewr/subscriptions","organizations_url":"https://api.github.com/users/drewr/orgs","repos_url":"https://api.github.com/users/drewr/repos","events_url":"https://api.github.com/users/drewr/events{/privacy}","received_events_url":"https://api.github.com/users/drewr/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/elastic/logstash/labels/enhancement","name":"enhancement","color":"009800"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-07T20:28:26Z","updated_at":"2016-03-04T00:03:54Z","closed_at":null,"body":"Currently `flush_size` is the only knob to control how much data a worker sends to ES, but if data varies in size, this can range from annoying (inconsistent heap use) to catastrophic on a low-margin system.\r\n\r\nThere should be some kind of `flush_bytes` setting as well, where each time a message is slated to be added to a pending bulk request the total bytes of the docs are considered."},"comment":{"url":"https://api.github.com/repos/elastic/logstash/issues/comments/192028748","html_url":"https://github.com/elastic/logstash/issues/4000#issuecomment-192028748","issue_url":"https://api.github.com/repos/elastic/logstash/issues/4000","id":192028748,"user":{"login":"jordansissel","id":131818,"avatar_url":"https://avatars.githubusercontent.com/u/131818?v=3","gravatar_id":"","url":"https://api.github.com/users/jordansissel","html_url":"https://github.com/jordansissel","followers_url":"https://api.github.com/users/jordansissel/followers","following_url":"https://api.github.com/users/jordansissel/following{/other_user}","gists_url":"https://api.github.com/users/jordansissel/gists{/gist_id}","starred_url":"https://api.github.com/users/jordansissel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jordansissel/subscriptions","organizations_url":"https://api.github.com/users/jordansissel/orgs","repos_url":"https://api.github.com/users/jordansissel/repos","events_url":"https://api.github.com/users/jordansissel/events{/privacy}","received_events_url":"https://api.github.com/users/jordansissel/received_events","type":"User","site_admin":false},"created_at":"2016-03-04T00:03:54Z","updated_at":"2016-03-04T00:03:54Z","body":"Just an update - we are planning to implement this in some way -- at least to make the ES output aware of the bytesize of its request and splitting it (somehow) if too large."}}