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

census: Fix retry stats data race [backport v1.40.x] #8471

Merged
merged 1 commit into from
Sep 2, 2021

Commits on Sep 2, 2021

  1. census: Fix retry stats data race (grpc#8459)

    There is data race in `CensusStatsModule. CallAttemptsTracerFactory`:
    
    If client call is cancelled while an active stream on the transport is not committed, then a [noop substream](https://github.com/grpc/grpc-java/blob/v1.40.0/core/src/main/java/io/grpc/internal/RetriableStream.java#L486) will be committed and the active stream will be cancelled. Because the active stream cancellation triggers the stream listener closed() on the _transport_ thread, the closed() method can be invoked concurrently with the call listener onClose(). Therefore, one `CallAttemptsTracerFactory.attemptEnded()` can be called concurrently with `CallAttemptsTracerFactory.callEnded()`, and there could be data race on RETRY_DELAY_PER_CALL. See also the regression test added.
    
    The same data race can happen in hedging case when one of hedges is committed and completes the call, other uncommitted hedges would cancel themselves and trigger their stream listeners closed() on the transport_thread concurrently. 
    
    Fixing the race by recording RETRY_DELAY_PER_CALL once both the conditions are met: 
    - callEnded is true 
    - number of active streams is 0.
    dapengzhang0 committed Sep 2, 2021
    Configuration menu
    Copy the full SHA
    8023457 View commit details
    Browse the repository at this point in the history