Skip to content

wasm: onLog is not always called for network streams on upstream failure #13806

New issue
New issue
Closed
Closed
wasm: onLog is not always called for network streams on upstream failure#13806
Labels
area/wasmbugstalestalebot believes this issue/PR has not been touched recently
@kyessenov

Description

@kyessenov
kyessenov
opened on Oct 28, 2020

Ref: istio/istio#24720
Validated with a flakey upstream that becomes unavailable at an interval.
Recording number of calls to onLog and onNewConnection, we see that onLog is not always called:
connection_count: 11030 log_count: 10662

/cc @PiotrSikora

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/wasmbugstalestalebot believes this issue/PR has not been touched recently

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions