Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

体验新版 GitCode，发现更多精彩内容 >>

提交 a6582202 编写于 作者: H Heikki Linnakangas 提交者： Xin Zhang
浏览文件
操作

Remove some more references in docs to stuff that's been removed.

上级 93d578e2
隐藏空白更改
内联 并排
Showing with 43 addition and 164 deletion
gpdb-doc/dita/GPRefGuide.ditamap
浏览文件 @ a6582202
......@@ -211,7 +211,6 @@
<topicref href="ref_guide/system_catalogs/gp_fastsequence.xml"/>
<topicref href="ref_guide/system_catalogs/gp_id.xml"/>
<topicref href="ref_guide/system_catalogs/gp_pgdatabase.xml"/>
<topicref href="ref_guide/system_catalogs/gp_relation_node.xml"/>
<topicref href="ref_guide/system_catalogs/gp_resqueue_status.xml"/>
<topicref href="ref_guide/system_catalogs/gp_segment_configuration.xml"/>
<topicref href="ref_guide/system_catalogs/gp_transaction_log.xml"/>
......
gpdb-doc/dita/admin_guide/expand/expand-initialize.xml
浏览文件 @ a6582202
......@@ -116,12 +116,12 @@
<p>Use the interactive interview process to create your own input file
unless your expansion scenario has atypical needs. </p>
<p>The format for expansion input files is:</p>
<codeblock>hostname:address:port:fselocation:dbid:content:preferred_role:replication_port</codeblock>
<codeblock>hostname:address:port:datadir:dbid:content:preferred_role</codeblock>
<p>For example:</p>
<codeblock>sdw5:sdw5-1:50011:/gpdata/primary/gp9:11:9:p:53011
sdw5:sdw5-2:50012:/gpdata/primary/gp10:12:10:p:53011
sdw5:sdw5-2:60011:/gpdata/mirror/gp9:13:9:m:63011
sdw5:sdw5-1:60012:/gpdata/mirror/gp10:14:10:m:63011</codeblock>
<codeblock>sdw5:sdw5-1:50011:/gpdata/primary/gp9:11:9:p
sdw5:sdw5-2:50012:/gpdata/primary/gp10:12:10:p
sdw5:sdw5-2:60011:/gpdata/mirror/gp9:13:9:m
sdw5:sdw5-1:60012:/gpdata/mirror/gp10:14:10:m</codeblock>
<p>For each new segment, this format of expansion input file requires the following:</p>
<table id="no165833">
<title>Data for the expansion configuration file</title>
......@@ -149,10 +149,10 @@ sdw5:sdw5-1:60012:/gpdata/mirror/gp10:14:10:m:63011</codeblock>
existing segment <i>port</i> base number. </entry>
</row>
<row>
<entry colname="col1">fselocation</entry>
<entry colname="col1">datadir</entry>
<entry colname="col2">Directory name</entry>
<entry colname="col3">The data directory (filespace) location for a segment as per
the pg_filespace_entry system catalog.</entry>
<entry colname="col3">The data directory location for a segment as per
the gp_segment_configuration system catalog.</entry>
</row>
<row>
<entry colname="col1">dbid</entry>
......@@ -181,12 +181,6 @@ sdw5:sdw5-1:60012:/gpdata/mirror/gp10:14:10:m:63011</codeblock>
<entry colname="col3">Determines whether this segment is a primary or mirror.
Specify <codeph>p</codeph> for primary and <codeph>m</codeph> for mirror.</entry>
</row>
<row>
<entry colname="col1">replication_port</entry>
<entry colname="col2">An available port number</entry>
<entry colname="col3">File replication port for the segment, incremented on the
existing segment <i>replication_port</i> base number.</entry>
</row>
</tbody>
</tgroup>
</table>
......
gpdb-doc/dita/admin_guide/monitoring.dita
浏览文件 @ a6582202
......@@ -323,18 +323,6 @@ WHERE logseverity in ('FATAL', 'ERROR')
database:<codeblock>gpcheckcat -O</codeblock></entry>
<entry>Run repair scripts for any issues detected.</entry>
</section>
</parml>
<section><title>Check persistent table catalog</title>
<parml>
<entry>Run a persistent table catalog check.<p>Recommended frequency:
monthly</p><pt>Severity</pt>
<pd>CRITICAL</pd></entry>
<entry>During a downtime, with no users on the system, run the Greenplum
<codeph>gpcheckcat</codeph> utility in each
database:<codeblock>gpcheckcat -R persistent</codeblock></entry>
<entry>If any problems are identified, contact Pivotal support for
assistance.</entry>
</section>
</parml>
<section><title></title>
<parml>
......
gpdb-doc/dita/ref_guide/ref_guide.ditamap
浏览文件 @ a6582202
......@@ -148,7 +148,6 @@
<topicref href="system_catalogs/gp_fastsequence.xml"/>
<topicref href="system_catalogs/gp_id.xml"/>
<topicref href="system_catalogs/gp_pgdatabase.xml"/>
<topicref href="system_catalogs/gp_relation_node.xml"/>
<topicref href="system_catalogs/gp_resgroup_config.xml"/>
<topicref href="system_catalogs/gp_resgroup_status.xml"/>
<topicref href="system_catalogs/gp_resqueue_status.xml"/>
......
gpdb-doc/dita/ref_guide/system_catalogs/catalog_ref-tables.xml
浏览文件 @ a6582202
......@@ -25,21 +25,6 @@
</li>
<li id="eu152757">gp_master_mirroring (Deprecated. See <xref
href="./pg_stat_replication.xml#topic1" type="topic" format="dita"/>.)</li>
<li id="eu150169">
<xref href="./gp_persistent_database_node.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150359">
<xref href="./gp_persistent_filespace_node.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150344">
<xref href="./gp_persistent_relation_node.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150345">
<xref href="./gp_persistent_tablespace_node.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150346">
<xref href="./gp_relation_node.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150031">
<xref href="./gp_segment_configuration.xml#topic1" type="topic" format="dita"/>
</li>
......@@ -105,12 +90,6 @@
<li id="eu150510">
<xref href="./pg_exttable.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150511">
<xref href="./pg_filespace.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150515">
<xref href="./pg_filespace_entry.xml#topic1" type="topic" format="dita"/>
</li>
<li id="eu150585">pg_foreign_data_wrapper (not supported)</li>
<li id="eu150589">pg_foreign_server (not supported)</li>
<li id="eu150593">pg_foreign_table (not supported)</li>
......
gpdb-doc/dita/ref_guide/system_catalogs/gp_relation_node.xml 已删除 100644 → 0
浏览文件 @ 93d578e2
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<topic id="topic1" xml:lang="en">
<title id="fo138336">gp_relation_node</title>
<body>
<p>The <codeph>gp_relation_node</codeph> table contains information about the file system
objects for a relation (table, view, index, and so on).</p>
<table id="fo138428">
<title>pg_catalog.gp_relation_node</title>
<tgroup cols="4">
<colspec colnum="1" colname="col1" colwidth="135pt"/>
<colspec colnum="2" colname="col2" colwidth="66.75pt"/>
<colspec colnum="3" colname="col3" colwidth="97.5pt"/>
<colspec colnum="4" colname="col4" colwidth="138pt"/>
<thead>
<row>
<entry colname="col1">column</entry>
<entry colname="col2">type</entry>
<entry colname="col3">references</entry>
<entry colname="col4">description</entry>
</row>
</thead>
<tbody>
<row>
<entry colname="col1">
<codeph>relfilenode_oid</codeph>
</entry>
<entry colname="col2">oid</entry>
<entry colname="col3">pg_class.relfilenode</entry>
<entry colname="col4">The object id of the relation file node.</entry>
</row>
<row>
<entry colname="col1">
<codeph>segment_file_num</codeph>
</entry>
<entry colname="col2">integer</entry>
<entry colname="col3"/>
<entry colname="col4">For append-optimized tables, the append-optimized segment file
number.</entry>
</row>
<row>
<entry colname="col1">
<codeph>persistent_tid</codeph>
</entry>
<entry colname="col2">tid</entry>
<entry colname="col3"/>
<entry colname="col4">Used by Greenplum Database to internally manage
persistent representations of file system objects.</entry>
</row>
<row>
<entry colname="col1">
<codeph>persistent_serial_num</codeph>
</entry>
<entry colname="col2">bigint</entry>
<entry colname="col3"/>
<entry colname="col4">Log sequence number position in the transaction log for a file
block.</entry>
</row>
</tbody>
</tgroup>
</table>
</body>
</topic>
gpdb-doc/dita/utility_guide/admin_utilities/gpaddmirrors.xml
浏览文件 @ a6582202
......@@ -60,8 +60,7 @@ mirror1=1:sdw1-1:60001:/gpdata/mir2/gp1</codeblock>
<p>The <codeph>gp_segment_configuration</codeph> system catalog table can help you determine
your current primary segment configuration so that you can plan your mirror segment
configuration. For example, run the following query:</p>
<codeblock>=# SELECT dbid, content, address as host_address, port,
   replication_port, datadir
<codeblock>=# SELECT dbid, content, address as host_address, port, datadir
   FROM gp_segment_configuration
   ORDER BY dbid;</codeblock>
<p>If creating your mirrors on alternate mirror hosts, the new mirror segment hosts must
......@@ -107,7 +106,7 @@ mirror1=1:sdw1-1:60001:/gpdata/mir2/gp1</codeblock>
the system. The format of this file is as follows (as per attributes in the
<codeph>gp_segment_configuration</codeph> catalog table):</pd>
<pd>
<codeblock>mirror[<varname>content</varname>]=<varname>content</varname>:<varname>address</varname>:<varname>port</varname>:<varname>fselocation</varname></codeblock>
<codeblock>mirror[<varname>content</varname>]=<varname>content</varname>:<varname>address</varname>:<varname>port</varname>:<varname></varname></codeblock>
</pd>
</plentry>
<plentry>
......@@ -140,15 +139,12 @@ mirror1=1:sdw1-1:60001:/gpdata/mir2/gp1</codeblock>
</plentry>
<plentry>
<pt>-p <varname>port_offset</varname></pt>
<pd>Optional. This number is used to calculate the database ports and
replication ports used for mirror segments. The default offset is 1000.
<pd>Optional. This number is used to calculate the database ports
used for mirror segments. The default offset is 1000.
Mirror port assignments are calculated as follows: </pd>
<pd>primary port + offset = mirror database port</pd>
<pd>primary port + (2 * offset) = mirror replication port</pd>
<pd>primary port + (3 * offset) = primary replication port</pd>
<pd>For example, if a primary segment has port 50001, then its mirror will use a
database port of 51001, a mirror replication port of 52001, and a primary
replication port of 53001 by default.</pd>
database port of 51001, by default.</pd>
</plentry>
<plentry>
<pt>-s (spread mirrors)</pt>
......@@ -176,7 +172,7 @@ mirror1=1:sdw1-1:60001:/gpdata/mir2/gp1</codeblock>
<section id="section5">
<title>Examples</title>
<p>Add mirroring to an existing Greenplum Database system using the same set of hosts as
your primary data. Calculate the mirror database and replication ports by adding 100
your primary data. Calculate the mirror database ports by adding 100
to the current primary segment port numbers:</p>
<codeblock>$ gpaddmirrors -p 100</codeblock>
<p>Add mirroring to an existing Greenplum Database system using a different set of hosts
......@@ -184,9 +180,9 @@ mirror1=1:sdw1-1:60001:/gpdata/mir2/gp1</codeblock>
<codeblock>$ gpaddmirrors -i mirror_config_file</codeblock>
<p>Where <codeph>mirror_config_file</codeph> looks something like this:</p>
<codeblock>mirror0=0:sdw1-1:52001:53001:54001:/gpdata/mir1/gp0
mirror1=1:sdw1-2:52002:53002:54002:/gpdata/mir2/gp1
mirror2=2:sdw2-1:52001:53001:54001:/gpdata/mir1/gp2
mirror3=3:sdw2-2:52002:53002:54002:/gpdata/mir2/gp3</codeblock>
mirror1=1:sdw1-2:52002:/gpdata/mir2/gp1
mirror2=2:sdw2-1:52001:/gpdata/mir1/gp2
mirror3=3:sdw2-2:52002:/gpdata/mir2/gp3</codeblock>
<p>Output a sample mirror configuration file to use with <codeph>gpaddmirrors
-i</codeph>:</p>
<codeblock>$ gpaddmirrors -o /home/gpadmin/sample_mirror_config</codeblock>
......
gpdb-doc/dita/utility_guide/admin_utilities/gpcheckcat.xml
浏览文件 @ a6582202
......@@ -53,12 +53,8 @@
is missing row on one segment, but other segments have this row. As another example, the
values of specific row column data are different across segments, such as table owner or
table access privileges.</li>
<li>Persistent Table inconsistencies are inconsistencies in persistence object state and
file system objects on a segment. For example, there are no running transactions, all
transactions are complete, but there is object that is marked as <codeph>creation
incomplete</codeph> in persistent tables. As another example, a file exists in
database directory, but there is no corresponding object existing in the database system
tables.</li>
<li>Inconsistency between a catalog table and the filesystem. For example, a file exists in
database directory, but there is no entry for it in the pg_class table.</li>
</ul></p>
</section>
<section id="section4">
......@@ -117,28 +113,21 @@
</pt>
<pd>Specify a test to run. Some tests can be run only when Greenplum Database is in
restricted mode.</pd>
<pd>These are the tests that can be performed:<p><codeph>acl</codeph> - Cross consistency
check for access control privileges</p><p><codeph>duplicate</codeph> - Check for
duplicate entries</p><p><codeph>duplicate_persistent</codeph> - Check for duplicate
<i>gp_persistent_relation_node</i> entries</p><p><codeph>foreign_key</codeph> -
Check foreign keys</p><p><codeph>inconsistent</codeph> - Cross consistency check for
master segment inconsistency</p><p><codeph>mirroring_matching</codeph> - Checks if
mirroring is consistent (either enabled or disabled) for the cluster and
segments.</p><p><codeph>missing_extraneous</codeph> - Cross consistency check for
missing or extraneous entries</p><p><codeph>owner</codeph> - Check table ownership
that is inconsistent with the master database</p><p><codeph>part_integrity</codeph> -
Check <i>pg_partition</i> branch integrity, partition with OIDs, partition
distribution policy</p><p><codeph>part_constraint</codeph> - Check constraints on
partitioned tables</p><p><codeph>unique_index_violation</codeph> - Check tables that
have columns with the unique index constraint for duplicate
entries</p><p><codeph>dependency</codeph> - Check for dependency on non-existent
objects (restricted mode only)</p><p><codeph>distribution_policy</codeph> - Check
constraints on randomly distributed tables (restricted mode
only)</p><p><codeph>namespace</codeph> - Check for schemas with a missing schema
definition (restricted mode only)</p><p><codeph>persistent</codeph> - Check persistent
tables (restricted mode only)</p><p><codeph>pgclass</codeph> - Check <i>pg_class</i>
entry that does not have any corresponding <i>pg_attribute</i> entry (restricted mode
only)</p></pd>
<pd>These are the tests that can be performed:
<p><codeph>acl</codeph> - Cross consistency check for access control privileges</p>
<p><codeph>duplicate</codeph> - Check for duplicate entries</p>
<p><codeph>foreign_key</codeph> - Check foreign keys</p>
<p><codeph>inconsistent</codeph> - Cross consistency check for master segment inconsistency</p>
<p><codeph>missing_extraneous</codeph> - Cross consistency check for missing or extraneous entries</p>
<p><codeph>owner</codeph> - Check table ownership that is inconsistent with the master database</p>
<p><codeph>part_integrity</codeph> - Check <i>pg_partition</i> branch integrity, partition with OIDs, partition distribution policy</p>
<p><codeph>part_constraint</codeph> - Check constraints on partitioned tables</p>
<p><codeph>unique_index_violation</codeph> - Check tables that have columns with the unique index constraint for duplicate entries</p>
<p><codeph>dependency</codeph> - Check for dependency on non-existent objects (restricted mode only)</p>
<p><codeph>distribution_policy</codeph> - Check constraints on randomly distributed tables (restricted mode only)</p>
<p><codeph>namespace</codeph> - Check for schemas with a missing schema definition (restricted mode only)</p>
<p><codeph>pgclass</codeph> - Check <i>pg_class</i> entry that does not have any corresponding <i>pg_attribute</i> entry (restricted mode only)</p>
</pd>
</plentry>
<plentry>
<pt>-S {none | only}</pt>
......
gpdb-doc/dita/utility_guide/admin_utilities/gprecoverseg.xml
浏览文件 @ a6582202
......@@ -56,15 +56,14 @@
The word <b>SPACE</b> indicates the location of a required space. Do not add additional
spaces.</p>
<codeblock>&lt;failed_host_address&gt;:&lt;port&gt;:&lt;data_directory&gt;<b>SPACE</b>
&lt;recovery_host_address&gt;:&lt;port&gt;:&lt;replication_port&gt;:&lt;data_directory&gt;
[:&lt;fselocation&gt;:...]</codeblock>
&lt;recovery_host_address&gt;:&lt;port&gt;:&lt;data_directory&gt;
</codeblock>
<p>See the <codeph>-i</codeph> option below for details and examples of a recovery
configuration file.</p>
<p>The <codeph>gp_segment_configuration</codeph> system catalog table can help you determine your
current segment configuration so that you can plan your mirror recovery configuration. For
example, run the following query:</p>
<codeblock>=# SELECT dbid, content, address, port,
   replication_port, datadir
<codeblock>=# SELECT dbid, content, address, port, datadir
   FROM gp_segment_configuration
   ORDER BY dbid;</codeblock>
<p>The new recovery segment host must be pre-installed with the Greenplum Database software
......@@ -107,8 +106,8 @@
line in the file is in the following format. The word <b>SPACE</b> indicates the
location of a required space. Do not add additional
spaces.<codeblock>&lt;failed_host_address&gt;:&lt;port&gt;:&lt;data_directory&gt;<b>SPACE</b>
&lt;recovery_host_address&gt;:&lt;port&gt;:&lt;replication_port&gt;:&lt;data_directory&gt;
[:&lt;fselocation&gt;:...]</codeblock><p><b>Comments</b></p><p>Lines
&lt;recovery_host_address&gt;:&lt;port&gt;:&lt;data_directory&gt;
</codeblock><p><b>Comments</b></p><p>Lines
beginning with <codeph>#</codeph> are treated as comments and
ignored.</p>
<p><b>Segments to Recover</b></p><p>Each line after the first specifies a segment to
......@@ -119,13 +118,13 @@
in the line. The required space is indicated by <b>SPACE</b>. Do not add additional
spaces.</p><p>
<codeblock>failedAddress:failedPort:failedDataDirectory<b>SPACE</b>newAddress:
newPort:newReplicationPort:newDataDirectory</codeblock>
newPort:newDataDirectory</codeblock>
</p><p><b>Examples</b></p><p><b>In-place
recovery of a single
mirror</b></p>
<codeblock>sdw1-1:50001:/data1/mirror/gpseg16</codeblock>
<p><b>Recovery of a single mirror to a new host</b></p>
<codeblock>sdw1-1:50001:/data1/mirror/gpseg16<b>SPACE</b>sdw4-1:50001:51001:/data1/recover1/gpseg16</codeblock>
<codeblock>sdw1-1:50001:/data1/mirror/gpseg16<b>SPACE</b>sdw4-1:50001:/data1/recover1/gpseg16</codeblock>
<p><b>Obtaining a Sample File</b></p>
<p>You can use the <codeph>-o</codeph> option to output a
sample recovery configuration file to use as a starting point.</p></pd>
......
src/test/tinc/tincrepo/mpp/lib/gprecoverseg.py
浏览文件 @ a6582202
......@@ -34,7 +34,7 @@ class GpRecoverseg():
self.stderr = None
def run_using_workerpool(self, option=''):
if not (set(option.split()) <= set(['-F' , '-r', '--persistent-check', ' '])):
if not (set(option.split()) <= set(['-F' , '-r', ' '])):
raise GpRecoversegException('Not a valid option with gprecoverseg')
rcvr_cmd = 'gprecoverseg -a %s' % option
......@@ -49,7 +49,7 @@ class GpRecoverseg():
@type option: string
@param option: gprecoverseg option (-F or -r)
'''
if not (set(option.split()) <= set(['-F' , '-r', '--persistent-check', ' '])):
if not (set(option.split()) <= set(['-F' , '-r', ' '])):
raise GpRecoversegException('Not a valid option with gprecoverseg')
rcvr_cmd = 'gprecoverseg -a %s' % option
cmd = Command(name='Run gprecoverseg', cmdStr='source %s/greenplum_path.sh;%s' % (self.gphome, rcvr_cmd))
......
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或