Docker启动单机版GreenPlum(GPDB)数据库

最新推荐文章于 2024-05-23 10:27:01 发布
最新推荐文章于 2024-05-23 10:27:01 发布
阅读量2.3k 收藏 4
点赞数 1
分类专栏： greenplum docker 文章标签： 数据库 greenplum
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_34412985/article/details/111802531
版权

下载镜像

# docker pull pivotaldata/gpdb-devel

运行容器

# docker run -it -p 15430:15432 --name gpdb0 -v /root/greenplum-db-gpdb-sandbox-tutorials-d734733/:/workspace/gpdb/tutorials -d pivotaldata/gpdb-devel

进入容器

# docker exec -it gpdb0 bash

首次切换gpadmin用户，会自动启动gp数据库

bash-4.1# su gpadmin
/workspace/gpdb/gpAux/gpdemo /workspace/gpdb
======================================================================
            ______  _____  ______  _______ _______  _____
           |  ____ |_____] |     \ |______ |  |  | |     |
           |_____| |       |_____/ |______ |  |  | |_____|

----------------------------------------------------------------------


  This is a demo of the Greenplum Database system.  We will create
  a cluster installation with master and 6 segment instances
  (3 primary & 3 mirror).

    GPHOME ................. : /usr/local/gpdb
    MASTER_DATA_DIRECTORY .. : /workspace/gpdb/gpAux/gpdemo/datadirs/qddir/demoDataDir-1

    MASTER PORT (PGPORT) ... : 15432
    SEGMENT PORTS .......... : 25432 25433 25434 25435 25436 25437 25438 25439 25440 25441 25442 25443

  NOTE(s):

    * The DB ports identified above must be available for use.
    * An environment file gpdemo-env.sh has been created for your use.

======================================================================

==========================================================================================
executing:
  /usr/local/gpdb/bin/gpinitsystem -a -c clusterConfigFile -l /workspace/gpdb/gpAux/gpdemo/datadirs/gpAdminLogs ""
==========================================================================================


。。。省略部分输出

 

            gp_opt_version             
---------------------------------------
 Server has been compiled without ORCA
(1 row)

======================================================================


/workspace/gpdb

创建用户

bash-4.1$ createuser -P dlw  
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create databases? (y/n) y
Shall the new role be allowed to create more new roles? (y/n) n
NOTICE:  resource queue required -- using default resource queue "pg_default"

创建数据库

bash-4.1$ createdb dlwdb
bash-4.1$ psql dlwdb    
psql (8.3.23)
Type "help" for help.
执行help查看命令帮助
dlwdb=# help
You are using psql, the command-line interface to PostgreSQL.
Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help with psql commands
       \g or terminate with semicolon to execute query
       \q to quit

在数据库中创建用户

dlwdb=# CREATE USER cyj WITH PASSWORD 'cyj' NOSUPERUSER;            
NOTICE:  resource queue required -- using default resource queue "pg_default"
CREATE ROLE

创建用户组并添加用户进去

dlwdb=# CREATE ROLE dcyls;
NOTICE:  resource queue required -- using default resource queue "pg_default"
CREATE ROLE
dlwdb=# GRANT dcyls TO dlw,cyj;
GRANT ROLE
dlwdb=# \du
                       List of roles
 Role name |            Attributes             | Member of
-----------+-----------------------------------+-----------
 cyj       |                                   | {dcyls}
 dcyls     | Cannot login                      | {}
 dlw       | Create DB                         | {dcyls}
 gpadmin   | Superuser, Create role, Create DB | {}

重启容器

    容器暂停后，下次启动会出现报错，提示ssh连接问题

# docker stop gpdb0
gpdb0
# docker start gpdb0
gpdb0
# docker exec -it gpdb0 bash
bash-4.1# su gpadmin
bash-4.1$ createuser -P dlw  
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) y
createuser: could not connect to database postgres: could not connect to server: Connection refused
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.15432"?

bash-4.1$ gpstart
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Starting gpstart with args:
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Gathering information and validating the environment...
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 4.3.99.00 build dev'
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Greenplum Catalog Version: '301605129'
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[WARNING]:-postmaster.pid file exists on Master, checking if recovery startup required
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Commencing recovery startup checks
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Have lock file /tmp/.s.PGSQL.15432 but no process running on port 15432
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-No Master instance process, entering recovery startup mode
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Clearing Master instance lock files
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Clearing Master instance pid file
20190827:02:42:25:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Starting Master instance in admin mode
20190827:02:42:26:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20190827:02:42:26:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Obtaining Segment details from master...
20190827:02:42:26:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Setting new master era
20190827:02:42:26:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Commencing forced instance shutdown
20190827:02:42:28:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Starting Master instance in admin mode
20190827:02:42:29:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20190827:02:42:29:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Obtaining Segment details from master...
20190827:02:42:29:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Setting new master era
20190827:02:42:29:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master Started...
20190827:02:42:29:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Shutting down master
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master instance parameters
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Database                 = template1
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master Port              = 15432
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master directory         = /workspace/gpdb/gpAux/gpdemo/datadirs/qddir/demoDataDir-1
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Timeout                  = 600 seconds
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master standby           = Off
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------------------
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Segment instances that will be started
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------------------
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Host           Datadir                                                             Port    Role
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast1/demoDataDir0          25432   Primary
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror1/demoDataDir0   25435   Mirror
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast2/demoDataDir1          25433   Primary
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror2/demoDataDir1   25436   Mirror
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast3/demoDataDir2          25434   Primary
20190827:02:42:30:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror3/demoDataDir2   25437   Mirror

Continue with Greenplum instance startup Yy|Nn (default=N):
> y
20190827:02:42:35:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Commencing parallel primary and mirror segment instance startup, please wait...
.
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Process results...
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[ERROR]:-No segment started for content: 0.
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-dumping success segments: []
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-DBID:2  FAILED  host:'3ce34f890d16' datadir:'/workspace/gpdb/gpAux/gpdemo/datadirs/dbfast1/demoDataDir0' with reason:'cmd had rc=255 completed=True halted=False
  stdout=''
  stderr='ssh: connect to host 3ce34f890d16 port 22: Connection refused
''
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-DBID:5  FAILED  host:'3ce34f890d16' datadir:'/workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror1/demoDataDir0' with reason:'cmd had rc=255 completed=True halted=False
  stdout=''
  stderr='ssh: connect to host 3ce34f890d16 port 22: Connection refused
''
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-DBID:3  FAILED  host:'3ce34f890d16' datadir:'/workspace/gpdb/gpAux/gpdemo/datadirs/dbfast2/demoDataDir1' with reason:'cmd had rc=255 completed=True halted=False
  stdout=''
  stderr='ssh: connect to host 3ce34f890d16 port 22: Connection refused
''
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-DBID:6  FAILED  host:'3ce34f890d16' datadir:'/workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror2/demoDataDir1' with reason:'cmd had rc=255 completed=True halted=False
  stdout=''
  stderr='ssh: connect to host 3ce34f890d16 port 22: Connection refused
''
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-DBID:4  FAILED  host:'3ce34f890d16' datadir:'/workspace/gpdb/gpAux/gpdemo/datadirs/dbfast3/demoDataDir2' with reason:'cmd had rc=255 completed=True halted=False
  stdout=''
  stderr='ssh: connect to host 3ce34f890d16 port 22: Connection refused
''
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-DBID:7  FAILED  host:'3ce34f890d16' datadir:'/workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror3/demoDataDir2' with reason:'cmd had rc=255 completed=True halted=False
  stdout=''
  stderr='ssh: connect to host 3ce34f890d16 port 22: Connection refused
''
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------


20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Successful segment starts                                            = 0
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[WARNING]:-Failed segment starts                                                = 6   <<<<<<<<
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Skipped segment starts (segments are marked down in configuration)   = 0
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Successfully started 0 of 6 segment instances <<<<<<<<
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[WARNING]:-Segment instance startup failures reported
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[WARNING]:-Failed start 6 of 6 segment instances <<<<<<<<
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[WARNING]:-Review /home/gpadmin/gpAdminLogs/gpstart_20190827.log
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:42:36:000018 gpstart:3ce34f890d16:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...
.
 
20190827:02:42:37:000018 gpstart:3ce34f890d16:gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the array.


    这个问题很好处理，它是ssh自己，看下ssh服务，第一次启动的时候应该是启动脚本里附带了启动sshd服务，之后再启动，需要自己手动启动下sshd服务，此处是centos6.8的系统

bash-4.1$ hostname
3ce34f890d16
bash-4.1$ ssh 3ce34f890d16         
ssh: connect to host 3ce34f890d16 port 22: Connection refused
bash-4.1$ cat /etc/redhat-release
CentOS release 6.8 (Final)
bash-4.1$ service sshd start
/etc/init.d/sshd: line 33: /etc/sysconfig/sshd: Permission denied
Starting sshd: /etc/ssh/sshd_config: Permission denied
                                                           [FAILED]
bash-4.1$ exit
exit
bash-4.1# service sshd start
Starting sshd:                                             [  OK  ]

    启动sshd后再启动数据库，正常运行

bash-4.1# su gpadmin        
bash-4.1$ gpstart                 
20190827:02:43:49:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Starting gpstart with args:
20190827:02:43:49:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Gathering information and validating the environment...
20190827:02:43:49:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 4.3.99.00 build dev'
20190827:02:43:49:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Greenplum Catalog Version: '301605129'
20190827:02:43:49:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Starting Master instance in admin mode
20190827:02:43:50:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20190827:02:43:50:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Obtaining Segment details from master...
20190827:02:43:51:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Setting new master era
20190827:02:43:51:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master Started...
20190827:02:43:51:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Shutting down master
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master instance parameters
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Database                 = template1
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master Port              = 15432
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master directory         = /workspace/gpdb/gpAux/gpdemo/datadirs/qddir/demoDataDir-1
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Timeout                  = 600 seconds
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Master standby           = Off
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------------------
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Segment instances that will be started
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:---------------------------------------
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Host           Datadir                                                             Port    Role
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast1/demoDataDir0          25432   Primary
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror1/demoDataDir0   25435   Mirror
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast2/demoDataDir1          25433   Primary
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror2/demoDataDir1   25436   Mirror
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast3/demoDataDir2          25434   Primary
20190827:02:43:52:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   3ce34f890d16   /workspace/gpdb/gpAux/gpdemo/datadirs/dbfast_mirror3/demoDataDir2   25437   Mirror

Continue with Greenplum instance startup Yy|Nn (default=N):
> y
20190827:02:43:54:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Commencing parallel primary and mirror segment instance startup, please wait...
....
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Process results...
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Successful segment starts                                            = 6
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Failed segment starts                                                = 0
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-   Skipped segment starts (segments are marked down in configuration)   = 0
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Successfully started 6 of 6 segment instances
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-----------------------------------------------------
20190827:02:43:58:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Starting Master instance 3ce34f890d16 directory /workspace/gpdb/gpAux/gpdemo/datadirs/qddir/demoDataDir-1
20190827:02:43:59:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Command pg_ctl reports Master 3ce34f890d16 instance active
20190827:02:43:59:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-No standby master configured.  skipping...
20190827:02:43:59:000169 gpstart:3ce34f890d16:gpadmin-[INFO]:-Database successfully started
bash-4.1$ createuser -P dlw
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) y
bash-4.1$
bash-4.1$ createdb dlwdb
bash-4.1$ psql dlwdb   
psql (8.3.23)
Type "help" for help.

dlwdb=#

客户端连接

连接之前需要修改pgdb的配置文件，允许客户端所在网络可以连接 配置文件目录可以在初始化pgdb的时候看到


bash-4.1$ cd /workspace/gpdb/gpAux/gpdemo/datadirs/qddir/demoDataDir-1
bash-4.1$ vi pg_hba.conf
添加 host all all 192.16.126.0/24 trust    
重启gpdb
bash-4.1$ gpstop -r

注意：网络要配置客户端的ip地址，比如我的ip地址是10.114.200.23  云主机的ip是10.114.10.33此时要配置成host all all 10.114.200.0/24 trust是可以的

下载windows客户端

https://www.postgresql.org/ftp/pgadmin/pgadmin3/v1.22.2/win32/

安装之后启动连接

成功连接

参考连接

https://yq.aliyun.com/articles/57656

qq_34412985
关注
  • 1
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
专栏目录
解决服务器重启，GreenPlum无法启动问题
MyySophia的博客
09-17 1287
一台测试服务器，由于升级glib的时候直接把系统搞死，机器无法启动，后来机器就回来之后，发现GP 启动不起来了。 gp启动时报错 home]$ gpstart -a 20210917:11:05:30:028785 gpstart:gptest01:gpadmin-[INFO]:-Starting gpstart with args: -a 20210917:11:05:30:028785 gpstart:gptest01:gpadmin-[INFO]:-Gathering information
docker制作的arm版达梦数据库镜像
07-11
一键安装，无需修改源码 docker load一键使用
gp数据库主节点故障导致数据库无法重启报错
weixin_45607571的博客
09-08 2659
由于机房电源割接失误导致所有服务器全部挂掉，导致数据库故障，重启数据库一直报错，以下是解决方法希望可以帮到有同样问题的小伙伴。 故障原因：Greenplum 由于备master节点故障导致gp无法启动处理 1、已经配置了gpstandby节点，如果gpstandby故障是不会影响Greenplum正常运行，但是如果此时关闭master主节点则无法启法需要将原gpstandby节点移除。 1、启动master节点失败 [gpadmin@gpmaster ~]$ gpstart 20200908:11:30:3
sheng的学习笔记-docker部署Greenplum
coldstarry的专栏
05-23 462
创建的默认数据库是gpadmin，密码也是这个。创建的默认数据库是gpadmin，密码也是这个。打开终端，输入代码，查看版本。
GreenPlum 启动失败Failed to start Master instance in admin mode问题
热门推荐
csdn's blog
08-01 1万+
开发同事跟我说，测试环境的greenplun突然连接不上了，于是我登陆进去服务器，发现没有greenplun进程了，问开发同事是否有对greenplumn有过改动之类的，他们说没有动过，这就奇了怪了，咋回事呢？ 自己手动尝试下gpstart启动报错 [gpadmin@00_mdw ~]$ gpstart 20170517:10:53:59:017586 gpstart:00_mdw:gpa...
Docker单机GreenPlum(GPDB)及Java连接
weixin_55565111的博客
10-12 794
GreenPlum是一个底层是多台PostgreSQL分表分库的分布式数据库，它有如下特点。· 支持标准SQL，几乎所有PostgreSQL支持的SQL，greenplum都支持。用户：gpadmin ，密码：secret。GP不是开源的，是商业版的，是开源的，支持海量数据存储，线性扩展。· 支持ACID、分布式事务。
greenplum-记录一个gp数据库segment节点双宕机问题暴力解决方式（不推荐）
qq_38195893的博客
04-03 749
首先存在一个或多个segment的primary节点掉线,致使该segment的mirror节点启动.在mirror节点启动后,在该mirror节点对应的pg_xlog文件夹下,会一直记录系统日志,以保证在该segment的primary节点启动后的数据一致性.
docker安装greenplum集群.docx
08-14
docker安装greenplum集群服务，通过dockerfile创建greenplum镜像，容器启动后，对greenplum集群进行配置
ES单机版Docker安装指导文档
09-26
docker安装es单机版，还有监控工具的安装指导说明，1.虚拟机安装建议centos7.6，5.ES监控软件cerebro安装。
docker 安装单机版redis
最新发布
07-24
docker 安装单机版redis
Docker容器启动时初始化Mysql数据库的方法
01-09
1. 前言 Docker在开发中使用的越来越多了，...能不能做到Mysql容器启动时就自己初始化数据库呢？当然可以！今天就来演示一下。全部代码见文末。 2.原理 当Mysql容器首次启动时，会在 /docker-entrypoint-initdb.d目录下
greenplum数据库集群异常FATAL","XX000","Number of freeTIDs 788079, do not match maximum free order numbe
Jun_ming的博客
11-23 3843
背景描述：greenplum生产集群晚上运行任务负载过高导致实例异常，集群资源繁忙无法正常登陆数据库无法进行恢复，清理部分任务进程后停库进行重启失败，64个实例29个失败。 现象：重启异常：[ERROR]:-gpstart error: Do not have enough valid segments to start the array. 启动过程如下： 23:13:31...
greenplum数据库无法启动 error: Do not have enough valid segments to start the array.
Jun_ming的博客
03-31 4136
greenplum数据库异常无法启动，启动报错error: Do not have enough valid segments to start the array.查看数据库日志报错FATAL","XX000","Global sequence number 20930983 less than maximum value 20930998 found in scan ('gp...
gpstart -a错误：Error occurred: non-zero rc: 1
BIG BOSS的博客
08-21 1403
[gpadmin@site92 greenplum-cc-web-6.2.0-gp6-rhel7-x86_64]$ gpstart -a 20200821:11:49:27:030822 gpstart:site92:gpadmin-[INFO]:-Starting gpstart with args: -a 20200821:11:49:27:030822 gpstart:site92:gpadmin-[INFO]:-Gathering information and validating the env
Greenplum数据库故障分析——版本升级后gpstart -a为何返回失败
肥叔菌的博客
08-04 621
从上面日志可以看出在升级前HA组件在修复standbymaster，gpinitstandby运行到从master数据目录拷贝数据到standbymaster时，升级脚本关闭了greenplum集群，导致的失败。现场项目进行Greenplum数据库小版本升级时，升级脚本报错，提示数据库启动失败。在升级前HA组件在修复standbymaster，gpinitstandby运行到从master数据目录拷贝数据到standbymaster时，升级脚本关闭了greenplum集群，导致的失败。...
master节点故障切换到standby master上
murkey的专栏
04-21 1578
下面模拟Master节点故障，切换到Standby的情况。直接关闭Master节点主机的电源，模拟Master节点故障。可以通过gpactivatestandby命令将Standby切换成Master，这个命令依赖几个环境变量，下面的测试会一一介绍。 1. 需要设置master和standby的环境变量 SDW [root@mdw ~]# su - gpadmin Last ...
Greenplum启动失败的问题定位思路及解决办法
专注数据库、大数据领域干货分享，用严谨的数据技术广交天下朋友。
01-13 2213
Greenplum是一个比较健壮的数据库产品，所以常规使用过程中，鲜有问题出现。 通常集群出现问题都是外部环境导致的，比如磁盘空间满了导致集群hang住，或者 文件系统损坏导致文件丢失等。 今天社区的小伙伴在使用官方版本gpcc后，发现data目录特别大，然后强行卸载gpcc，最终由于一些未知的原因而导致集群重启失败了。这里说一下帮他定位问题的思路： 1.清理集群环境 首先上来要清理集群所有机器上的/tmp/.s.PG.xxx相关的socket文件，清理所有机器上的残留进程ps -ef | grep
Greenplum初始化数据库时出现gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the arr
double_happiness的博客
10-18 3798
启动初始化greenplum数据库报错信息如下所示 [gpadmin@mdw gpAdminLogs]$ gpstart 20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Starting gpstart with args: 20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Ga...
Greenplum初始化gpinitsystem报错解决
你好我是李白
06-19 8530
初始化报错解决 报错Unable to resolve mdw on this host 现象 [gpadmin@sdw1~]$gpinitsystem-cgpconfigs/gpinitsystem_config-hgpconfigs/hostfile_gpinitsystem 20200618:15:33:10:010535gpinitsystem:sdw1:gpadmin-[INFO]:-Checkingconfigurationparameters,pleasew...
greenplum数据库 docker 单机安装 详细过程
03-31
以下是在单台服务器上使用Docker安装Greenplum数据库的详细步骤： 1. 安装Docker 首先需要在服务器上安装Docker。可以参考官方文档进行安装。 2. 下载Greenplum镜像 执行以下命令下载Greenplum数据库的Docker镜像： ``` docker pull pivotaldata/gpdb ``` 3. 创建Greenplum容器 执行以下命令创建一个名为“gpdb”的Greenplum容器： ``` docker run --name gpdb -p 5432:5432 -v /data/gpdata:/gpdata -d pivotaldata/gpdb ``` 其中： - `--name gpdb`：指定容器名称为“gpdb”。 - `-p 5432:5432`：将容器内部的5432端口映射到宿主机的5432端口，方便外部访问。 - `-v /data/gpdata:/gpdata`：将宿主机上的`/data/gpdata`目录挂载到容器内部的`/gpdata`目录，用于存储Greenplum数据库的数据文件。 - `-d pivotaldata/gpdb`：指定使用pivotaldata/gpdb镜像来创建容器，并在后台运行。 4. 进入Greenplum容器 执行以下命令进入名为“gpdb”的容器： ``` docker exec -it gpdb bash ``` 5. 初始化Greenplum数据库 进入容器后，执行以下命令初始化Greenplum数据库： ``` source /usr/local/greenplum-db/greenplum_path.sh initdb ``` 6. 启动Greenplum数据库 执行以下命令启动Greenplum数据库： ``` gpstart ``` 7. 创建Greenplum数据库 执行以下命令创建一个名为“testdb”的Greenplum数据库： ``` createdb testdb ``` 至此，Greenplum数据库的单机安装就完成了。可以使用以下命令查看数据库状态： ``` gpstate ``` 可以使用以下命令退出容器： ``` exit ``` 可以使用以下命令停止并删除容器： ``` docker stop gpdb docker rm gpdb ``` 可以使用以下命令删除Greenplum镜像： ``` docker rmi pivotaldata/gpdb ``` 注意事项： - 在使用Greenplum数据库之前，需要先熟悉Greenplum数据库的基本概念和操作方法。 - 在使用Docker时，需要注意Docker的安全性和隔离性，避免容器中的数据受到攻击或泄露。
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值