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

Adding support for timeout for multilang protocol, related to issue 185 #195

Merged
merged 6 commits into from
Aug 1, 2017

Conversation

sahilpalvia
Copy link
Contributor

No description provided.

@sahilpalvia sahilpalvia changed the title Adding support for timeout for multilang protocol, related to [#185](https://github.com/awslabs/amazon-kinesis-client/issues/185) Adding support for timeout for multilang protocol, related to issue 185 Aug 1, 2017
@sahilpalvia sahilpalvia merged commit e8f9ad3 into awslabs:master Aug 1, 2017
@sahilpalvia sahilpalvia deleted the multilang-stuck-fix branch August 1, 2017 18:37
@pfifer pfifer added this to the Release 1.8.1 milestone Aug 2, 2017
pfifer added a commit to pfifer/amazon-kinesis-client that referenced this pull request Aug 2, 2017
Support timeouts for calls to the MultiLang Daemon
This adds support for setting a timeout when dispatching records to
the client record processor. If the record processor doesn't respond
within the timeout the parent Java process will be terminated. This
is a temporary fix to handle cases where the KCL becomes blocked
while waiting for a client record processor.

The timeout for the this can be set by adding
  `timeoutInSeconds = <timeout value>`.
The default for this is no timeout.

Setting this can cause the KCL to exit suddenly, before using this
ensure that you have an automated restart for your application

Related awslabs#195
Related awslabs#185
@pfifer pfifer mentioned this pull request Aug 2, 2017
pfifer added a commit that referenced this pull request Aug 2, 2017
Support timeouts for calls to the MultiLang Daemon
This adds support for setting a timeout when dispatching records to
the client record processor. If the record processor doesn't respond
within the timeout the parent Java process will be terminated. This
is a temporary fix to handle cases where the KCL becomes blocked
while waiting for a client record processor.

The timeout for the this can be set by adding
  `timeoutInSeconds = <timeout value>`.
The default for this is no timeout.

Setting this can cause the KCL to exit suddenly, before using this
ensure that you have an automated restart for your application

Related #195
Related #185
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants