Lambda <-> Lambda invocation taking >=3sec once in every 10/15mins #1797
Labels
closed-for-staleness
guidance
Question that needs advice or information.
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 10 days.
Describe the issue
Have 2lambdas running inside vpc, when I invoke 2nd lambda from the 1st the time taken is ==3sec , this is happening only once in every 10/15mins with or without traffic. Looks like the connection is not continuously live. i attached the log, you can observe the line 37, 40 which took 3secs to invoke lambda, initially we are using aws version 1.11.647 but as per suggestion by aws support enginneer we updated to aws sdk version to 2.13.5 , but we still see the lambda invocation is still taking 3sec EVEN AFTER UPGRADING.
**The total duration in the second lambda is around 600ms, but the invocation time between Lambda1 & Lambda2 is 3sec **
piece of log from attached: - observe the time stamp for -->Start & -->End
-->Start DmpSegments L2 invoking : 2020-04-29 17:42:13.226
2020-04-29 17:42:13.246 - DEBUG [main] com.abnamro.nl.solution.polar.application.utils.AwsLambdaInvokeUtil.invoke(AwsLambdaInvokeUtil.java:79): -->Start invoke:dmpGetLambda: 2020-04-29 17:42:13.246
2020-04-29 17:42:15.825 - DEBUG [main] com.abnamro.nl.solution.polar.application.utils.AwsLambdaInvokeUtil.invoke(AwsLambdaInvokeUtil.java:83): -->END invoke:dmpGetLambda: 2020-04-29 17:42:15.825
-->END DmpSegments L2 invoke: 2020-04-29 17:42:15.826
Attached the full log.
Attached the Aws lamdba invoke util java code
Steps to Reproduce
Create 2lambdas inside VPC & invoke from L1 <-> L2 & observe the lambda to lambda invocation time.
Current Behavior
The invocation time is taking longer than expected (3sec) where the 2nd lambda total duration is only 600ms, the expected total invocation time should be less than 1sec.
Your Environment
Attached the full log.
Attached the Aws lamdba invoke util java code
lambdainvoke_awsv2sdk.log.zip
AwsLambdaInvokeUtil.java.zip
The text was updated successfully, but these errors were encountered: