forked from docs/doc-exports
Chen, Junjie
dd8a3a658b
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
17 lines
2.8 KiB
HTML
17 lines
2.8 KiB
HTML
<a name="kafka-faq-200426037"></a><a name="kafka-faq-200426037"></a>
|
|
|
|
<h1 class="topictitle1">Why Can't I Query Messages on the Console?</h1>
|
|
<div id="body1587865606409"><ul id="kafka-faq-200426037__ul15694453125218"><li id="kafka-faq-200426037__li76941853195211"><strong id="kafka-faq-200426037__b36740953614">Possible cause 1</strong>: The message has been aged.<p id="kafka-faq-200426037__p961118414489"><strong id="kafka-faq-200426037__b15623112143615">Solution</strong>: <a href="kafka-ug-200506001.html">Change the aging time</a>.</p>
|
|
</li><li id="kafka-faq-200426037__li76262171533"><strong id="kafka-faq-200426037__b12346215183614">Possible cause 2</strong>: The createTime timestamp of the message is incorrect.<p id="kafka-faq-200426037__p172361918537">On the console, messages are queried based on the timestamp, which is generated by the client. Different clients have different processing policies. The default value may be <strong id="kafka-faq-200426037__b1147013911239">0</strong> or <strong id="kafka-faq-200426037__b147543932314">-1</strong>. As a result, message may fail to be queried.</p>
|
|
<p id="kafka-faq-200426037__p184989391161"><strong id="kafka-faq-200426037__b12920858203514">Solution</strong>: Check whether the value of createTime is correctly configured.</p>
|
|
</li><li id="kafka-faq-200426037__li98724181784"><strong id="kafka-faq-200426037__b17701521143617">Possible cause 3</strong>: The disk usage exceeds 95%, and <strong id="kafka-faq-200426037__b94062388366">Capacity Threshold Policy</strong> is set to <strong id="kafka-faq-200426037__b918814063619">Automatically delete</strong>.<p id="kafka-faq-200426037__p1430683611012">If <strong id="kafka-faq-200426037__b1456918573377">Capacity Threshold Policy</strong> is set to <strong id="kafka-faq-200426037__b155251144388">Automatically delete</strong>, the earliest 10% of messages will be deleted when 95% of the disk capacity is used, to ensure sufficient disk space. In this case, the messages that do not reach the aging time are also deleted and cannot be queried.</p>
|
|
<p id="kafka-faq-200426037__p2164238125419"><strong id="kafka-faq-200426037__b164731352103811">Solution</strong>: <a href="kafka-ug-180604017.html">Modify the capacity threshold policy</a>. If <strong id="kafka-faq-200426037__b1623123615">Capacity Threshold Policy</strong> is set to <strong id="kafka-faq-200426037__b42303217">Stop production</strong>, new messages will no longer be created when the disk usage reaches the disk capacity threshold (95%), but existing messages can still be retrieved until the aging time arrives. This policy is suitable for scenarios where no data losses can be tolerated.</p>
|
|
</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="kafka-faq-190416001.html">Messages</a></div>
|
|
</div>
|
|
</div>
|
|
|