Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
08969b8f
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
08969b8f
编写于
4月 26, 2019
作者:
C
Chuck Litzell
提交者:
David Yozie
4月 26, 2019
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Remove implication that transactions restart themselves after segment failure. (#7534)
上级
ee76756c
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
13 addition
and
6 deletion
+13
-6
gpdb-doc/dita/admin_guide/highavail/topics/g-overview-of-segment-mirroring.xml
...uide/highavail/topics/g-overview-of-segment-mirroring.xml
+6
-2
gpdb-doc/dita/admin_guide/managing/highavail.xml
gpdb-doc/dita/admin_guide/managing/highavail.xml
+7
-4
未找到文件。
gpdb-doc/dita/admin_guide/highavail/topics/g-overview-of-segment-mirroring.xml
浏览文件 @
08969b8f
...
...
@@ -8,8 +8,12 @@
instances:
<i>
primary
</i>
and
<i>
mirror
</i>
. Each primary segment has one corresponding
mirror segment. A primary segment instance receives requests from the master to make
changes to the segment data and then replicates those changes to the corresponding
mirror. If a primary segment becomes unavailable, database queries fail over to the
mirror segment.
</p>
mirror. If Greenplum Database detects that a primary segment has failed or become
unavailable, it changes the role of its mirror segment to primary segment and the role
of the unavailable primary segment to mirror segment. Transactions in progress when the
failure occurred roll back and must be restarted. The administrator must then recover
the mirror segment, allow the mirror to syncronize with the current primary segment, and
then exchange the primary and mirror segments so they are in their preferred roles.
</p>
<p>
If segment mirroring is not enabled, the Greenplum Database system shuts down if a
segment instance fails. Administrators must manually recover all failed segments before
Greenplum Database operations can resume.
</p>
...
...
gpdb-doc/dita/admin_guide/managing/highavail.xml
浏览文件 @
08969b8f
...
...
@@ -253,10 +253,13 @@ mirror3=3:sdw2:sdw2-2:52002:53002:54002:/gpdata/mir1/gp3
<title
id=
"ki155550"
>
Detecting a Failed Segment
</title>
<body>
<p>
With mirroring enabled, Greenplum Database automatically fails over to a mirror segment
when a primary segment goes down. Provided one segment instance is online per portion of
data, users may not realize a segment is down. If a transaction is in progress when a fault
occurs, the in-progress transaction rolls back and restarts automatically on the
reconfigured set of segments.
</p>
when a primary segment goes down. The mirror segment assumes the role of the primary segment
and the failed primary segment becomes the mirror. Transactions in progress when a fault
occurs roll back and must be restarted. When restarted the transactions run on the new
primary segment.
</p>
<p>
To return the Greenplum Database cluster to full redundancy and balance, an administrator
recovers the down mirror segment and exchanges the roles of the primary and mirror
segments so that both segments are in their preferred roles.
</p>
<p>
If the entire Greenplum Database system becomes nonoperational due to a segment failure
(for example, if mirroring is not enabled or not enough segments are online to access all
user data), users will see errors when trying to connect to a database. The errors returned
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录