Skip to content

Conversation

@sushanb
Copy link
Contributor

@sushanb sushanb commented Oct 17, 2025

expose a metric to track the number of outstanding rpcs (unary , streaming) in channel pool

@sushanb sushanb requested review from a team as code owners October 17, 2025 21:39
@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: bigtable Issues related to the googleapis/java-bigtable API. labels Oct 17, 2025
@sushanb sushanb added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Oct 17, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Oct 17, 2025
@product-auto-label product-auto-label bot added size: l Pull request size is large. and removed size: m Pull request size is medium. labels Oct 20, 2025
@sushanb sushanb added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Oct 22, 2025
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Oct 22, 2025
@sushanb sushanb changed the title feat(bigtable): add bookkeeping per unary/streaming rpcs feat(bigtable): expose a metric to track the number of outstanding rpcs (unary , streaming) in channel pool Oct 22, 2025
@sushanb sushanb requested a review from mutianf October 22, 2025 19:06

@Override
public int getOutstandingStreamingRpcs() {
return 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

return outstandingStreamingRpcs.get(); ?

And maybe add a test case? I'm a little concerned that this is not caught by any tests :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no tests for ChannelPool. added a test

@product-auto-label product-auto-label bot added size: xl Pull request size is extra large. and removed size: l Pull request size is large. labels Oct 24, 2025
Aggregation.explicitBucketHistogram(
ImmutableList.of(
0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 12.0, 14.0, 16.0, 18.0, 20.0,
25.0, 30.0, 35.0, 40.0, 45.0, 50.0, 60.0, 70.0, 80.0, 90.0, 100.0, 110.0)); // Added
Copy link
Contributor

Choose a reason for hiding this comment

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

nit, remove the // Added comment in the end?
Do we need to go over 100? cause the grpc limit is 100.
Also wondering if we should have equal size for the bucket, maybe [0, 2, 4, 6, 8 ..., 100]? or [0, 5, 10, 15 .. 100]?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i think the queuing of the stream is deep inside the http2 lib in grpc netty. so we could have more than 100 here.

@sushanb sushanb requested a review from a team as a code owner October 28, 2025 19:47
}

void checkAndSetIsAlts(ClientCall<?, ?> call) {
// TODO(populate ALTS holder)
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: do we still need the TODO?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I will add it in another PR. for now, we use false.

@sushanb sushanb merged commit 140a1ad into googleapis:main Oct 29, 2025
24 checks passed
@sushanb sushanb deleted the book_keeping branch October 29, 2025 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigtable Issues related to the googleapis/java-bigtable API. size: xl Pull request size is extra large.

3 participants