All Products
Search

This Product

    ApsaraMQ for Kafka:When I query messages in the Message Queue for Apache Kafka console, why do the time points displayed in the Created At column of the query result greatly deviate from the time point that I specify for the query?

    Document Center

    ApsaraMQ for Kafka:When I query messages in the Message Queue for Apache Kafka console, why do the time points displayed in the Created At column of the query result greatly deviate from the time point that I specify for the query?

    Last Updated:Sep 14, 2023

    Symptoms

    Log on to the ApsaraMQ for Kafka console. On the Message Query page, select Search by Point in Time from the Search Method drop-down list, specify a time point in the Point in Time picker, and then click Search. The time points displayed in the Created At column greatly deviate from the time point specified for the query, or the time points displayed in the Created At column are null.

    image

    Causes

    • The time point specified for the query is earlier than the time point when the message at the earliest offset in the partition was sent, or later than the time point when the message at the latest offset in the partition was sent. In this case, the consumer offset is reset. The time points displayed in the Created At column are around the time point when the message at the latest offset in the partition was sent.
    • If the time points displayed in the Created At column are null, the client version does not support time attributes in messages.

    Solutions

    If the time points displayed in the Created At column are null, update the client to version 0.10.2 or later. We recommend that you use version 2.4.0.