Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update logstash_forwarder.md #15

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update logstash_forwarder.md #15

wants to merge 1 commit into from

Conversation

gnuhpc
Copy link
Contributor

@gnuhpc gnuhpc commented Aug 3, 2015

No description provided.

@chenryn
Copy link
Owner

chenryn commented Aug 3, 2015

no，你的写法有问题。这个issue讲的是LogStash::Pipeline如果堵塞(可能因为filter不行也可能因为output不行)，会影响到LogStash::Input::Tcp以及lumberjack等基于tcp的插件，因为sizedqueue不会通知前面给客户端发ack。所以input插件会oom。因果你搞反了。

@gnuhpc
Copy link
Contributor Author

gnuhpc commented Aug 3, 2015

对啊，我的indexer的其中一个input是lumberjack，其余是redis或者其他的tcp，output是es。它在压力大的时候确实pipeline阻塞了，然后它挂掉了。由于它作为indexer在后端，因此所有经过它的event都无法到达es....是我哪理解错了么...

On Mon, Aug 3, 2015 at 5:03 PM, 饶琛琳 [email protected] wrote:

no，你的写法有问题。这个issue讲的是LogStash::Pipeline如果堵塞(可能因为filter不行也可能因为output不行)，会影响到LogStash::Input::Tcp以及lumberjack等基于tcp的插件，因为sizedqueue不会通知前面给客户端发ack。所以input插件会oom。因果你搞反了。

—
Reply to this email directly or view it on GitHub
#15 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@gnuhpc @chenryn