A new consumer needs a starting position. Reading from the end waits for future records; reading from the beginning inspects the retained history. Neither operation removes records from Kafka. A maximum-message limit bounds the inspection so a terminal command can finish. In a real application, auto.offset.reset is used when there is no usable committed position; it does not override valid group offsets on every restart. These exercises use a new console inspection without stored group progress. Read all existing records and compare the result with the visible log. An empty output can be correct when a consumer starts at the end, so identify the starting rule before diagnosing missing messages.
Inspect the topics, partition logs and group offsets before changing the cluster.