<?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: Sqoop SQL to Hbase - slow after upgrade in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Sqoop-SQL-to-Hbase-slow-after-upgrade/m-p/309855#M223943</link>
    <description>&lt;P&gt;I should have responded with a bit more detail... but I couldn't figure out how to edit my initial response.&amp;nbsp; So here's a bit more info.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Interesting about turning off hbase audits.&amp;nbsp; Never tried that.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Sqoop for MSQL -&amp;gt; Hadoop is still really fast.&amp;nbsp; So I'm not suspecting hdfs configuration issues.&lt;/P&gt;&lt;P&gt;2. I did some testing with hbase pe but unfortunately I didn't get performance numbers before the upgrade.&amp;nbsp; So impossible to compare.&lt;/P&gt;&lt;P&gt;3. hdfs logs look clean&lt;/P&gt;&lt;P&gt;4. hbase logs look generally clean.&amp;nbsp; Sometimes get RPC reponseTooSlow WARNings but doesn't happen often&lt;/P&gt;&lt;P&gt;5. Have run major compaction on the hbase table in question.&amp;nbsp; The table has a number of regions spread across about 10 hbase region servers (no hot spotting)&lt;/P&gt;&lt;P&gt;6. I see minor compactions happening on the table while the sqoop is running.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since this only happened after the upgrade I was looking for changes in default values for the Cloudera Hbase configuration.&amp;nbsp; And changes in defaults from hbase 1.2.0 to hbase 2.1.2.&amp;nbsp; Tried adjusting a few values but nothing worked.&amp;nbsp; So I set them back.&amp;nbsp; I have read moving from hbase 1.2.x to hbase 2.1.x writes may be a bit slower.&amp;nbsp; But I'm talking like 100x slower for my sqoop.&amp;nbsp; So I'm pretty much sure that's not it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Another thing I noticed when I started examining the cluster more closely (I'm a developer but have been thrown into the sysadmin role for the upgrade) is that the network wasn't configured correctly.&amp;nbsp; The nodes in the clusters are supposed to know about each other (ie. the /etc/hosts file on each node should have entries for all other nodes in the cluster) and not rely on DNS to resolve other cluster hosts.&amp;nbsp; This isn't the case and the /etc/hosts only has the localhost entries.&amp;nbsp; But once again, it was this way before the upgrade.&amp;nbsp; So something to fix but probably not the cause of the hbase performance issue after the upgrade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;</description>
    <pubDate>Sun, 17 Jan 2021 12:02:35 GMT</pubDate>
    <dc:creator>Rjkoop</dc:creator>
    <dc:date>2021-01-17T12:02:35Z</dc:date>
  </channel>
</rss>

