<?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: Hbase- Eliminating empty regions with an export-import approach in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94767#M58155</link>
    <description>&lt;P&gt;Removed customer name.&lt;/P&gt;</description>
    <pubDate>Sun, 04 Oct 2015 18:35:35 GMT</pubDate>
    <dc:creator>pardeep_kumar</dc:creator>
    <dc:date>2015-10-04T18:35:35Z</dc:date>
    <item>
      <title>Hbase- Eliminating empty regions with an export-import approach</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94764#M58152</link>
      <description>&lt;P&gt;We are trying to reduce the number of empty regions in a table (informs_search). This table has around 5900 regions (includes thousands of empty regions) and 8TB worth data.&lt;/P&gt;&lt;P&gt;With an export – import approach on a sample data (16,819,569 rows).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Backup informs serach&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;disable 'informs_search'&lt;/P&gt;&lt;P&gt;snapshot 'informs_search', 'informs_search_snpsht'&lt;/P&gt;&lt;P&gt;clone_snapshot 'informs_search_snpsht', 'informs_search_backup'&lt;/P&gt;&lt;P&gt;delete_snapshot 'informs_search_snpsht'&lt;/P&gt;&lt;P&gt;enable ‘informs_search’&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Export informs_search&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;/usr/hdp/current/hbase-client/bin/hbase org.apache.hadoop.hbase.mapreduce.Export 'informs_search' /db/support/hexport/inform_search_bk  1 1 1443738964000&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Truncate informs search&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;truncate ‘informs_search’&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Import informs_search&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;hbase org.apache.hadoop.hbase.mapreduce.Import 'informs_search' /db/support/hexport/inform_search_bk&lt;/P&gt;&lt;P&gt;Observations:-&lt;/P&gt;&lt;UL&gt;
&lt;LI&gt;Before we ran these steps , we had 9 regions (6+3) across two region servers&lt;/LI&gt;&lt;LI&gt;After we ran these steps, we have 2 regions across 1 Region server&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;----------------------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;* In Production, after running the same, would that reduce to 2 regions as well?&lt;/P&gt;&lt;P&gt;* IS there anyway to predict/configure the resultant number of regions and regions servers?&lt;/P&gt;&lt;P&gt;* Also, how many major compactions will it take so that data will be distributed across the region servers (and regions)?&lt;/P&gt;</description>
      <pubDate>Sat, 03 Oct 2015 03:35:01 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94764#M58152</guid>
      <dc:creator>vwunnava</dc:creator>
      <dc:date>2015-10-03T03:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: Hbase- Eliminating empty regions with an export-import approach</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94765#M58153</link>
      <description>&lt;P&gt;The final #regions depends on the data at hand... If you want to constrain the number of regions, you should create a table with that many (pre-split) regions, and then import into that.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Oct 2015 05:26:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94765#M58153</guid>
      <dc:creator>ddas</dc:creator>
      <dc:date>2015-10-03T05:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: Hbase- Eliminating empty regions with an export-import approach</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94766#M58154</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/272/vwunnava.html" nodeid="272"&gt;@vwunnava@hortonworks.com&lt;/A&gt;&lt;P&gt;Please avoid putting customer names here as this is public facing forum. editing your question for the same.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Oct 2015 18:34:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94766#M58154</guid>
      <dc:creator>pardeep_kumar</dc:creator>
      <dc:date>2015-10-04T18:34:21Z</dc:date>
    </item>
    <item>
      <title>Re: Hbase- Eliminating empty regions with an export-import approach</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94767#M58155</link>
      <description>&lt;P&gt;Removed customer name.&lt;/P&gt;</description>
      <pubDate>Sun, 04 Oct 2015 18:35:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Hbase-Eliminating-empty-regions-with-an-export-import/m-p/94767#M58155</guid>
      <dc:creator>pardeep_kumar</dc:creator>
      <dc:date>2015-10-04T18:35:35Z</dc:date>
    </item>
  </channel>
</rss>

