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

chore: add Lambda configuration with values ported from nodejs #251

Merged
merged 3 commits into from
Nov 22, 2024

Conversation

pgautier404
Copy link
Collaborator

No description provided.

@pgautier404 pgautier404 requested a review from a team November 21, 2024 19:11
Comment on lines +39 to +40
$grpcConfig = new StaticGrpcConfiguration(1100);
$transportStrategy = new StaticStorageTransportStrategy($grpcConfig, $loggerFactory, self::$maxIdleMillis);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

iirc, the main difference in the lambda config was that keepalives were turned off. should we also add the keepalive setting to the grpc config and turn them off here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the keepalives were causing errors with infrequently invoked lambdas. If you want to add that in a future pr, we should get rid of the v1 config for now and only use latest.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know, thanks. I'll add that in.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I added the keepalive params into the gRPC config before realizing that keepalive is opt-in. The nodejs Lambda configuration just omits the keepalive parameters to use the gRPC defaults. So the Lambda config is good to go as-is and we're free to add keepalives to new configs and new versions of the existing configs in the future as we see fit.

Copy link
Contributor

@anitarua anitarua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

I was going to suggest just updating the keepalive settings in the other configs for now, but I guess that could impact existing customers and maybe would be better to do in a fix or feat commit.

@pgautier404
Copy link
Collaborator Author

lgtm!

I was going to suggest just updating the keepalive settings in the other configs for now, but I guess that could impact existing customers and maybe would be better to do in a fix or feat commit.

Yep, that was exactly what I was thinking.

@pgautier404 pgautier404 merged commit 6c9c373 into main Nov 22, 2024
9 checks passed
@pgautier404 pgautier404 deleted the add-lambda-configuration branch November 22, 2024 23:26
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.

3 participants