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.

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

Deleting Kafka works but shows an error message #1171

Closed
bernd opened this Issue May 22, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@bernd
Copy link
Member

bernd commented May 22, 2015

Deleting a Kafka input works but shows an error message in the web inteface because it runs into a timeout.

rp0odajqoeyaaaaasuvork5cyii

[error] o.g.r.l.ApiClient - REST call failed
java.util.concurrent.TimeoutException: No response received after 5000
        at com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:260) ~[async-http-client-1.8.14.jar:na]
        at org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:435) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at org.graylog2.restclient.models.Node.terminateInput(Node.java:322) [graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at controllers.InputsController.terminate(InputsController.java:370) [classes/:na]
        at Routes$$anonfun$routes$1$$anonfun$applyOrElse$51$$anonfun$apply$593.apply(routes_routing.scala:2018) [classes/:na]
[error] o.g.r.m.Node - Could not terminate input 555f0d79c830648bac67b2d9
org.graylog2.restclient.lib.APIException: API call failed DELETE http://@127.0.0.1:12900/system/inputs/555f0d79c830648bac67b2d9
        at org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:451) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at org.graylog2.restclient.models.Node.terminateInput(Node.java:322) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at controllers.InputsController.terminate(InputsController.java:370) [classes/:na]
        at Routes$$anonfun$routes$1$$anonfun$applyOrElse$51$$anonfun$apply$593.apply(routes_routing.scala:2018) [classes/:na]
        at Routes$$anonfun$routes$1$$anonfun$applyOrElse$51$$anonfun$apply$593.apply(routes_routing.scala:2018) [classes/:na]
Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: No response received after 5000
        at com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:266) ~[async-http-client-1.8.14.jar:na]
        at org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:435) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at org.graylog2.restclient.models.Node.terminateInput(Node.java:322) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at controllers.InputsController.terminate(InputsController.java:370) [classes/:na]
        at Routes$$anonfun$routes$1$$anonfun$applyOrElse$51$$anonfun$apply$593.apply(routes_routing.scala:2018) [classes/:na]
Caused by: java.util.concurrent.TimeoutException: No response received after 5000
        at com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:260) ~[async-http-client-1.8.14.jar:na]
        at org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:435) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at org.graylog2.restclient.models.Node.terminateInput(Node.java:322) ~[graylog2-rest-client-1.1.0-beta.3-SNAPSHOT.jar:na]
        at controllers.InputsController.terminate(InputsController.java:370) [classes/:na]
        at Routes$$anonfun$routes$1$$anonfun$applyOrElse$51$$anonfun$apply$593.apply(routes_routing.scala:2018) [classes/:na]

This is because the Kafka consumer threads are blocking and are only terminated after a 5 second timeout. Since the REST client also has a default timeout of 5 seconds, it is running into this.

@bernd bernd added the bug label May 22, 2015

@bernd bernd self-assigned this May 22, 2015

@bernd bernd added this to the 1.1.0 milestone May 22, 2015

bernd added a commit that referenced this issue May 22, 2015

Do not block the Kafka consumer thread but use a consumer timeout.
This makes the KafkaTransport responsive to stop requests and does not
cause a timeout.

Fixes #1171.
@bernd

This comment has been minimized.

Copy link
Member Author

bernd commented May 22, 2015

Closed via 60bfcdf.

@bernd bernd closed this May 22, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.