-
Notifications
You must be signed in to change notification settings - Fork 39
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
No longer using GAX batching for WriteLogEntries #632
Comments
Some important additional info: Here is the gapic yaml with the batching definition for WriteLogEntries from googleapis. It does seem to have moved around / between files over time. |
@Neenu1995 can you have a look into this issue, please. |
@jamestep we have had similar discussion in googleapis/java-logging-logback#134. Do you have additional info showing that batching does not work? |
Yes I do have some additional info:
See below when debugging, But then debugging 2.1.4, |
Thank you for this info. We need to check the problem with auto-generated code and will update you about next steps soon. |
Changes GrpcLoggingServiceV2Stub stub to make it createBatchingCallable. Modify WriteLogEntry sample to demo batching is working. See #632 for problem description
Thank you for your patience. We've confirmed the problem. Hopefully, it will be addressed in the next release. The release time will be dependent on the gapic generator fix. |
Fixed in #726 |
After some investigation, it seems like since version 2.1.4 of this library,
WriteLogEntries
is no longer using GAX batching.This is the specific line that's an issue, which changed in this commit. It switched from
createBatchingCallable
tocreateUnaryCallable
, despite keeping theBatchingCallSettings
logic.I understand the issue may not be in this library, but I'm not familiar with microgenerator / gapic / autosynth / synthtool and this seemed like a good place to start.
This issue means we are unable to update beyond 2.1.3 as we hit the GCP
WriteLogEntries
request quota very quickly.The text was updated successfully, but these errors were encountered: