Skip to content

TIM Propagation Bottleneck in Logger-Kafka-Consumer #22

@dmccoystephenson

Description

@dmccoystephenson

A problem can arise during the processing of TIMs when an update request is submitted. The update may take a significant amount of time to appear in the active_tim table and within the SDX.

Upon examining the logs, it appears that TIMs often move quickly through the ode-wrapper and the ODE. However, after this point, TIMs may experience delays while waiting in line at the logger-kafka-consumer, especially when multiple messages are being written to the database simultaneously.

The logger-kafka-consumer can create a bottleneck, impacting the efficient propagation of TIMs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions