-
Notifications
You must be signed in to change notification settings - Fork 126
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
fix: multiplexed session metrics were not included in refactor move #3088
Conversation
The metrics for multiplexed sessions were not included in the refactoring that moved multiplexed sessions out of the session pool. This change re-adds those metrics based on the new client for multiplexed sessions.
@@ -3143,7 +3153,7 @@ boolean isValid() { | |||
|
|||
/** | |||
* Returns a multiplexed session. The method fallbacks to a regular session if {@link | |||
* SessionPoolOptions#useMultiplexedSession} is not set. | |||
* SessionPoolOptions#getUseMultiplexedSession} is not set. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reference was wrong, and showed up as a warning in IntelliJ
@@ -68,7 +68,6 @@ | |||
import com.google.common.base.Function; | |||
import com.google.common.base.MoreObjects; | |||
import com.google.common.base.Preconditions; | |||
import com.google.common.base.Supplier; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not directly related to this change, but we should start to replace the use of com.google.common.base.Supplier
with java.util.function.Supplier
.
@@ -555,28 +551,6 @@ public void clearRequests() { | |||
mockSpanner.clearRequests(); | |||
} | |||
|
|||
@Test | |||
public void testCounter() throws InterruptedException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test was committed in a previous PR by accident. It was only intended as a test to verify that increasing an AtomicInteger
does not introduce any noticeable lock contention.
The metrics for multiplexed sessions were not included in the refactoring that moved multiplexed sessions out of the session pool. This change re-adds those metrics based on the new client for multiplexed sessions.