add bulk index rejection test #933
Conversation
openshift-ci-robot
added
the
size/L
|
/test |
|
The motivation for doing this now is https://bugzilla.redhat.com/show_bug.cgi?id=1541429 |
|
/lgtm |
|
/retest |
|
hmm - looks like bulk index rejection test is interfering with mux test? |
|
/retest |
|
/retest The json-file test flake in mux is very strange. It looks like an extra here is an example of a raw log message from a file: notice the extra |
|
Could that be a \n that was process as “escape the n” leaving it as a ‘n’?
…On Fri, Feb 9, 2018 at 7:37 PM Richard Megginson ***@***.***> wrote:
/retest
flakes in forward and mux tests???
The json-file test flake in mux is very strange. It looks like an extra n
character is being added to the messages?
"message": "67108864 is less then the default 128m. Setting to default.n",
"message": "2018-02-09 23:12:39 +0000 [warn]: 'block' action stops input process until the buffer full is resolved. Check your pipeline this action is fit or notn",
here is an example of a raw log message from a file:
***@***.***":"2018-02-09T23:13:13Z","tags":[],"pid":66,"method":"get","statusCode":404,"req":{"url":"/bd0cf33bdd464f9f924a47c80bc877f5","method":"get","headers":{"user-agent":"curl/7.29.0","host":"localhost:5601","accept":"*/*"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1"},"res":{"statusCode":404,"responseTime":2,"contentLength":9},"message":"GET /bd0cf33bdd464f9f924a47c80bc877f5 404 2ms - 9.0B"}n","stream":"stdout","time":"2018-02-09T23:13:13.559006504Z"}
notice the extra n after the closing }
wtf? docker --log-driver=json-file bug?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#933 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA57afbes4jAjcTUCI_6FMcgvRMvmhB6ks5tTOTFgaJpZM4R-dy3>
.
|
Yes, looks like that's it. So, probably false alarm. Looks like there is a bug in |
richm
added
the
do-not-merge/work-in-progress
richm
force-pushed
the
bulk-rejection-test
branch
from
0dc1b58
to
3fd9252
Compare
richm
removed
the
do-not-merge/work-in-progress
openshift-merge-robot
removed
the
lgtm
richm
added
the
do-not-merge/work-in-progress
richm
force-pushed
the
bulk-rejection-test
branch
from
3fd9252
to
c6c4bbe
Compare
|
/retest |
1 similar comment
|
/retest |
richm
force-pushed
the
bulk-rejection-test
branch
from
c6c4bbe
to
33b64ce
Compare
richm
force-pushed
the
bulk-rejection-test
branch
from
5d36663
to
3f69f8d
Compare
|
/retest |
1 similar comment
|
/retest |
This tests the ability of fluentd to handle bulk index rejections. The test starts up several curl processes which hammer Elasticsearch with bulk index requests which causes fluentd to receive bulk rejections. The methodology is to add some messages for both projects and operations indices which should be rejected and queued and eventually resent successfully. The test will ensure that Elasticsearch is rejecting bulk requests and fluentd is receiving bulk rejections. The test has to run last because it will cause other CI tests to have test flakes due to bulk index rejections, which somehow become persistent after this test runs.
richm
force-pushed
the
bulk-rejection-test
branch
from
3f69f8d
to
9c89068
Compare
|
/lgtm |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue. |
|
/cherrypick es5.x |
|
@richm: #933 failed to apply on top of branch "es5.x": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick release-3.9 |
|
@richm: #933 failed to apply on top of branch "release-3.9": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick release-3.8 |
|
@richm: #933 failed to apply on top of branch "release-3.8": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick release-3.7 |
|
@richm: #933 failed to apply on top of branch "release-3.7": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick release-3.9 |
|
@richm: new pull request created: #997 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick release-3.8 |
|
@richm: #933 failed to apply on top of branch "release-3.8": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick release-3.7 |
|
/cherrypick release-3.6 |
|
@richm: #933 failed to apply on top of branch "release-3.7": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@richm: #933 failed to apply on top of branch "release-3.6": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
…33-to-release-3.9 Automatic merge from submit-queue. [release-3.9] add bulk index rejection test This is an automated cherry-pick of #933 /assign richm
This tests the ability of fluentd to handle bulk index rejections.
The test starts up several curl processes which hammer Elasticsearch
with bulk index requests which causes fluentd to receive bulk rejections.
The methodology is to add some messages for both projects and operations
indices which should be rejected and queued and eventually resent
successfully.
The test will ensure that Elasticsearch is rejecting bulk requests and
fluentd is receiving bulk rejections.