Skip to content

logging: flowcontrol should block#2741

Merged
pongad merged 2 commits intogoogleapis:masterfrom
pongad:logging-block
Jan 6, 2018
Merged

logging: flowcontrol should block#2741
pongad merged 2 commits intogoogleapis:masterfrom
pongad:logging-block

Conversation

@pongad
Copy link
Copy Markdown
Contributor

@pongad pongad commented Jan 3, 2018

Fixes #2714.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jan 3, 2018
.setMaxOutstandingRequestBytes(10485760L)
.setLimitExceededBehavior(LimitExceededBehavior.Block)
.build())
.build());

This comment was marked as spam.

This comment was marked as spam.

@pongad
Copy link
Copy Markdown
Contributor Author

pongad commented Jan 5, 2018

@garrettjonesgoogle PTAL

@garrettjonesgoogle
Copy link
Copy Markdown
Contributor

LGTM

@pongad pongad merged commit 99e510d into googleapis:master Jan 6, 2018
@pongad pongad deleted the logging-block branch January 6, 2018 04:11
chingor13 pushed a commit that referenced this pull request Feb 20, 2026
#2741)

* chore: Update generation configuration at Sat Oct 26 02:22:52 UTC 2024

* chore: Update generation configuration at Sun Oct 27 02:27:42 UTC 2024
suztomo pushed a commit that referenced this pull request Mar 9, 2026
chingor13 pushed a commit that referenced this pull request Mar 30, 2026
#2741)

If a read is opened without a generation, we want to ensure we restart for the same generation. We have this behavior for json

This is mainly to avoid a race condition of reading an object (gen=1), that object being replaced (gen=2) then retry attempts to read it again we need to read gen=1 otherwise we will return corrupted data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants