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

Exception during updateCredentials #10

Open
jtruty opened this issue Jul 21, 2015 · 8 comments
Open

Exception during updateCredentials #10

jtruty opened this issue Jul 21, 2015 · 8 comments
Labels

Comments

@jtruty
Copy link

jtruty commented Jul 21, 2015

Is it possible to avoid this error when calling producer.destroy() to end the program? It doesn't seem to cause any issues, but I always see this:
[pool-1-thread-6] WARN com.amazonaws.services.kinesis.producer.Daemon - Exception during updateCredentials
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.amazonaws.services.kinesis.producer.Daemon$5.run(Daemon.java:316)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)

@kevincdeng
Copy link
Contributor

Yea that's an expected part of the termination procedure. It doesn't indicate any problems.

We'll try to get rid of the warning in the next release.

@pcurry
Copy link

pcurry commented May 17, 2016

Is this issue addressed yet?

@domenkosir
Copy link

domenkosir commented Jan 31, 2017

If anyone is still experiencing this issue, this fixed it for me:
kinesisProducerConfiguration.setCredentialsRefreshDelay(100)

As I see it, the thread running updateCredentials gets interrupted. The default delay is 5 seconds, but during shutdown the executor only waits 1 second before interrupting the thread. So setting the delay to something smaller than 1 second should fix the issue.

@pfifer pfifer added the bug label Feb 15, 2017
@pfifer
Copy link
Contributor

pfifer commented Feb 15, 2017

Thanks for reporting this. We are investigating and prioritizing the fix for this.

For other affected by this please comment, and add reactions to assist us in prioritizing the change.

@ganeshchand
Copy link

@domenkosir scalakinesisProducerConfiguration.setCredentialsRefreshDelay(100) worked for me.

@domenkosir
Copy link

@ganeshchand I'm glad it worked!

@cch1
Copy link

cch1 commented May 18, 2017

Bug still impacting me.

tzulitai pushed a commit to tzulitai/flink that referenced this issue Sep 22, 2017
…eCredentials Exception

The updateCredentials delay is an ignorable warning that occurs due to
the fact that the default credential update delay is longer than the
await termination timeout when shutting down KPL.

See awslabs/amazon-kinesis-producer#10 for
details.

This closes apache#4657.
asfgit pushed a commit to apache/flink that referenced this issue Sep 22, 2017
…eCredentials Exception

The updateCredentials delay is an ignorable warning that occurs due to
the fact that the default credential update delay is longer than the
await termination timeout when shutting down KPL.

See awslabs/amazon-kinesis-producer#10 for
details.

This closes #4657.
tzulitai pushed a commit to tzulitai/flink that referenced this issue Sep 22, 2017
…eCredentials Exception

The updateCredentials delay is an ignorable warning that occurs due to
the fact that the default credential update delay is longer than the
await termination timeout when shutting down KPL.

See awslabs/amazon-kinesis-producer#10 for
details.

This closes apache#4657.
@aromanenko-dev
Copy link

+1 to fix this issue

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

No branches or pull requests

8 participants