hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9149) javadoc cleanup of to reflect .META. rename to hbase:meta
Date Tue, 20 May 2014 05:16:38 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002812#comment-14002812

stack commented on HBASE-9149:

That'd work.  I tried a blanket search and replace but there are legit areas where we need
to retain .META. -- i.e. where we have to migrate old data to the new, stuff we could probably
let go now we are on 0.99... but they are there at the moment still.

./bin/region_mover.rb:# Returns true if passed region is still on 'original' when we look
at .META.
./bin/region_mover.rb:# Get servername that is up in .META.; this is hostname + port + startcode
./bin/region_mover.rb:  # No prefetching on .META. This is for versions pre 0.99. Newer versions
do not prefetch.
./bin/region_status.rb:# .META. table, that is not included in our scan
./conf/log4j.properties:# and scan of .META. messages
./hbase-common/src/main/java/org/apache/hadoop/hbase/TableName.java:  public static final
String OLD_META_STR = ".META.";
./hbase-common/src/main/java/org/apache/hadoop/hbase/TableName.java:   * TableName for old
.META. table. Used in testing.
     // 2. Remove table from .META. and HDFS
  * Removes the table from .META. and archives the HDFS files.
   // NOTE: At this point we still have data on disk, but nothing in .META.
   // 2. Remove table from .META. and HDFS
./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java: * -
creates system namespace directory and move .META. table there
./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java: * renaming
.META. table to hbase:meta,
./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java:    List<String>
sysTables = Lists.newArrayList("-ROOT-",".META.", ".META");
./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java:    Path
oldMetaDir = new Path(rootDir, ".META.");
./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java:    //
Remove .tableinfo files as they refer to ".META.".
./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java:    //
rename .META. to hbase:meta
 // create a put for new .META. entry with rowkey as hbase:meta
  // This is the point of no return.  Adding subsequent edits to .META. as we
  // do below when we do the daughter opens adding each to .META. can fail in
  // still and the server shutdown fixup of .META. will point to these
 LOG.info("Got an old .META. edit, continuing with new format ");
./hbase-server/src/main/java/org/apache/hadoop/hbase/util/HFileV1Detector.java:        .getCurrentTableInfoStatus(fs,
path, false) != null) || path.toString().endsWith(".META.");
./hbase-server/src/main/java/org/apache/hadoop/hbase/util/ZKDataMigrator.java:      if (table.equals("-ROOT-")
|| table.equals(".META.")) {
     new Path(hbaseRootDir, ".META.").toString()});
./hbase-server/src/test/java/org/apache/hadoop/hbase/io/hfile/TestHFileBlock.java:    BlockType.META.write(dos);
// Let's make this a meta block.
   BlockType.META.write(dos); // Let's make this a meta block.
     p = new Put(Bytes.toBytes(".META."));
     // verify rows .META. is renamed to hbase:meta
./src/main/docbkx/book.xml:       <para>The catalog tables -ROOT- and .META. exist as
HBase tables.  They are filtered out
./src/main/docbkx/book.xml:        <para>-ROOT- keeps track of where the .META. table
is.  The -ROOT- table structure is as follows:
./src/main/docbkx/book.xml:              <listitem><para>.META. region key (<code>.META.,,1</code>)</para></listitem>
./src/main/docbkx/book.xml:               instance of .META.)</para></listitem>
./src/main/docbkx/book.xml:              <listitem><para><code>info:server</code>
(server:port of the RegionServer holding .META.)</para></listitem>
./src/main/docbkx/book.xml:              <listitem><para><code>info:serverstartcode</code>
(start-time of the RegionServer process holding .META.)</para></listitem>
./src/main/docbkx/book.xml:        <para>The .META. table keeps a list of all regions
in the system. The .META. table structure is as follows:
./src/main/docbkx/book.xml:         the <code>.META.</code> and <code>-ROOT-</code>
catalog tables
./src/main/docbkx/book.xml:           <para>Periodically checks and cleans up the .META.
table.  See <xref linkend="arch.catalog.meta" /> for more information on META.</para>
./src/main/docbkx/book.xml:            <listitem><para>Catalog tables: The -ROOT-
and .META. tables are forced into the block cache and have the in-memory priority which means
that they are harder to evict. The former never uses
./src/main/docbkx/book.xml:(.regioninfo files), the region’s row in the .META. table., and
region’s deployment/assignments on
./src/main/docbkx/ops_mgt.xml:      table directory and then do an edit of the .META. table
replacing all mentions of the old
./src/main/docbkx/troubleshooting.xml:           and then the client goes back to .META. to
find the new location of the moved region.</para>
./src/main/docbkx/upgrading.xml:             hdfs://localhost:41020/myHBase/.META.
./src/main/docbkx/upgrading.xml:On startup, the <varname>.META.</varname> table
content is rewritten removing the table schema from the <varname>info:regioninfo</varname>
./src/main/docbkx/upgrading.xml:            <varname>.META.</varname> schema in
the shell.  In the past we would
./src/main/docbkx/upgrading.xml:            the current <varname>.META.</varname>
schema.  Check
./src/main/docbkx/upgrading.xml:            This will make the necessary edit to your <varname>.META.</varname>
./src/main/docbkx/upgrading.xml:            See <link xlink:href="https://issues.apache.org/jira/browse/HBASE-3499">HBASE-3499
Users upgrading to 0.90.0 need to have their .META. table updated with the right MEMSTORE_SIZE</link>
./src/main/site/xdoc/replication.xml:          .META. or -ROOT-, and did not originate in
the target slave cluster - in

Those in ./hbase-server/src/main/java/org/apache/hadoop/hbase/migration/NamespaceUpgrade.java
should probably be retained as is.

Ditto on this one: ./hbase-common/src/main/java/org/apache/hadoop/hbase/TableName.java:  
* TableName for old .META. table. Used in testing.


> javadoc cleanup of to reflect .META. rename to hbase:meta
> ---------------------------------------------------------
>                 Key: HBASE-9149
>                 URL: https://issues.apache.org/jira/browse/HBASE-9149
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Francis Liu
>            Assignee: Misty Stanley-Jones
>            Priority: Critical

This message was sent by Atlassian JIRA

View raw message