<?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: Solution for &amp;quot;slow readprocessor&amp;quot; warnings in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Solution-for-quot-slow-readprocessor-quot-warnings/m-p/122047#M84803</link>
    <description>&lt;P&gt;Right now I can think of 3 possible scenario which might create this issue.&lt;/P&gt;&lt;P&gt;1. Check the datanode logs corresponding to that block id, If there is any issue with the disks then probably you will see some messages like below. In case you can't find these messages then you still need take a look at disks IO&lt;/P&gt;&lt;PRE&gt;WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Slow BlockReceiver write data to disk cost:200ms (threshold=15ms)&lt;/PRE&gt;&lt;P&gt;OR&lt;/P&gt;&lt;PRE&gt;WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Slow BlockReceiver write packet to mirror took 986ms (threshold=300ms)&lt;/PRE&gt;&lt;P&gt;2. check datanode logs and it's GC pattern because a long GC pause can also cause this issue.&lt;/P&gt;&lt;P&gt;3. If datanode doesn't show any disk and GC issues  then the networks latency b/w client and datanode could be a culprit, you can use iperf or other network tool to check latency.&lt;/P&gt;</description>
    <pubDate>Fri, 11 Mar 2016 01:21:35 GMT</pubDate>
    <dc:creator>jyadav</dc:creator>
    <dc:date>2016-03-11T01:21:35Z</dc:date>
  </channel>
</rss>

