logstash-input-exec 3.3.2 → 3.3.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/CONTRIBUTORS +1 -0
- data/docs/index.asciidoc +6 -0
- data/logstash-input-exec.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 6572d99615f87ace8db0908a038f652de0e5c97c5bf0792f2f195ed6191243e5
|
|
4
|
+
data.tar.gz: c716f2124922141458bb4ace432389adbdf45dd9fe18a1eddec3aa29b9960b3e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 7d940aee8ca85ceee0baba1feda840ceb8f0cf1bf17977393692f3ba4ad8c2b1523a82e4b3bea5df0d17ad7b402c1e7b0f6d10741d7b4c459bcc869bc2c57090
|
|
7
|
+
data.tar.gz: 27ce9c58c67b1bdd8093851bbe9d0b20852fcff2ec5fe4c05dbd358cc296400e5e6abcca9a021594931cf342b3ea72805e3d8d42f38b63ce5c0d8d978e105979
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,6 @@
|
|
|
1
|
+
## 3.3.3
|
|
2
|
+
- Docs: improved doc on memory usage [#27](https://github.com/logstash-plugins/logstash-input-exec/pull/27)
|
|
3
|
+
|
|
1
4
|
## 3.3.2
|
|
2
5
|
- Fixed issue where certain log entries were incorrectly writing 'jdbc input' instead of 'exec input' [#21](https://github.com/logstash-plugins/logstash-input-exec/pull/21)
|
|
3
6
|
|
data/CONTRIBUTORS
CHANGED
data/docs/index.asciidoc
CHANGED
|
@@ -28,6 +28,12 @@ Notes:
|
|
|
28
28
|
* The `command` field of this event will be the command run.
|
|
29
29
|
* The `message` field of this event will be the entire stdout of the command.
|
|
30
30
|
|
|
31
|
+
===== IMPORTANT
|
|
32
|
+
|
|
33
|
+
The exec input ultimately uses `fork` to spawn a child process.
|
|
34
|
+
Using fork duplicates the parent process address space (in our case, **logstash and the JVM**); this is mitigated with OS copy-on-write but ultimately you can end up allocating lots of memory just for a "simple" executable.
|
|
35
|
+
If the exec input fails with errors like `ENOMEM: Cannot allocate memory` it is an indication that there is not enough non-JVM-heap physical memory to perform the fork.
|
|
36
|
+
|
|
31
37
|
|
|
32
38
|
Example:
|
|
33
39
|
|
data/logstash-input-exec.gemspec
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
Gem::Specification.new do |s|
|
|
2
2
|
|
|
3
3
|
s.name = 'logstash-input-exec'
|
|
4
|
-
s.version = '3.3.
|
|
4
|
+
s.version = '3.3.3'
|
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
|
6
6
|
s.summary = "Captures the output of a shell command as an event"
|
|
7
7
|
s.description = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: logstash-input-exec
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 3.3.
|
|
4
|
+
version: 3.3.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Elastic
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2019-09-10 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|