<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: kudu scan very slow in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/kudu-scan-very-slow/m-p/85367#M11685</link>
    <description>&lt;P&gt;You might be able to find a trace of the ScanRequest RPC in the /rpcz endpoint of the web UI. Try running the scan and, if you observe it is slow, looking at /rpcz for the matching trace.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that's too difficult, you can get all the traces dumped into the INFO log using the flag -rpc_dump_all_traces. Naturally this is very verbose on a busy server, but if you use the kudu tserver set_flag command you can turn the flag on and then turn it off a few seconds later, giving just enough time to capture the scan if you coordinate running the scan with turning on tracing. It's safe to change the flag at runtime in this way.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you get a trace, please copy paste it in a reply here. It will help us understand where time is being spent.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could also try gathering a trace of the tablet server when the slow scan runs. If you upload the trace file I can take a look at it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;See&amp;nbsp;&lt;A href="https://kudu.apache.org/docs/troubleshooting.html#kudu_tracing" target="_blank"&gt;https://kudu.apache.org/docs/troubleshooting.html#kudu_tracing&lt;/A&gt; for more information on how to gather traces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jan 2019 20:10:42 GMT</pubDate>
    <dc:creator>wdberkeley</dc:creator>
    <dc:date>2019-01-23T20:10:42Z</dc:date>
  </channel>
</rss>

