首页 > 编程知识 正文

mongodb启动命令,mongodb集群启动很慢

时间:2023-05-06 11:11:02 阅读:17272 作者:1149

另一方面,启动mongodb 1,根据命令行方式获取MongoDB # mongod-- dbpath=/data/mongo data/rs1-- log path=/data/mongo data/rs1 .启动log不足的grepmongodtcp0.0.0. 03360270170.0.0.0: * listen 5062/mongo D2,基于配置文件的命令行启动VI/var/lib mongo data/rs2/rs2.logsmallfiles=true fork=truepidfilepath=/var/run/mongo.path rs2.conf # # # author : les netstat-nltp|grep 27000 TCP0.0.0listen 5356/mongod 3,守护程序方式为MongoDB # mongod---dbpath=/data/mongo data/rs3 RSS1grepmongodtcp0.0.0. 0:28000.0.0.0: * listen 5465/mongodtcp0.0.0. 0:270170.0.03: * mongod4,使用系统服务启动/隐藏mogodb启动脚本# vi /etc/init.d/mongod#的未来/sh # chkconfig 336023459318 # mogodbhomediredired mongodbcommandmongodb _ zy mongodbconfigfilemongodb _ conf=$ MongoDB _ home/conf/MongoDB.conf # mongodbpidmongodb _ codb exitfistart () ulimit-hsn $ system _ maxfd $ MongoDB _ zy DDS-- config=' $ MongoDB _ conf '-fork # # added @ 2000 if then action $ ' starting $ MongoDB _ name : ' /看不见的未来/truelseaction $ ' starting $ MongoDB _ name 3360 ' /看不见的未来/fff then action $ ' stopping $ MongoDB _ name : ' /看不见的未来/falseexitfikill-hup ` cat $ MongoDB _ PID ` ret=$? if [ $ret -eq 0 ]; then action $ ' stopping $ MongoDB _ name : ' /看不见的未来/true rm -f $MONGODB_PID else action $"Stopping $MONGODB_NAME: " /隐形的未来/false fi}restart() { stop sleep 2 start}case "$1" in start) start ;; stop) stop ;; status) status $prog ;; restart) restart ;; *) echo $"Usage: $0 {start|stop|status|restart}"esac# chmod u+x /etc/init.d/mongod# service mongod startabout to fork child process, waiting until server is ready for connections.forked process: 5543child process started successfully, parent exitingStarting mongodb: [ OK ] 二、停止mongoDB 1、向mongod进程发送信号###SIGINT信号# ps -ef|grep mongod|grep rs1root 5435 4914 1 19:13 pts/2 00:00:14 mongod --dbpath=/data/mongodata/rs1 --logpath=/data/mongodata/rs1/rs1.log# kill -2 54352016-08-30T17:02:00.528+0800 I CONTROL[signalProcessingThread] got signal 2(Interrupt), will terminate after current cmd ends2016-08-30T17:02:00.530+0800 I REPL [signalProcessingThread] Stopping replication applier threads2016-08-30T17:02:00.554+0800 I STORAGE [conn1253] got request after shutdown()2016-08-30T17:02:00.774+0800 I CONTROL [signalProcessingThread] now exiting2016-08-30T17:02:00.774+0800 I NETWORK [signalProcessingThread] shutdown: going to close listening sockets...2016-08-30T17:02:00.774+0800 I NETWORK [signalProcessingThread] closing listening socket: 62016-08-30T17:02:00.775+0800 I NETWORK [signalProcessingThread] closing listening socket: 72016-08-30T17:02:00.775+0800 I NETWORK [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock2016-08-30T17:02:00.775+0800 I NETWORK [signalProcessingThread] shutdown: going to flush diaglog...2016-08-30T17:02:00.775+0800 I NETWORK [signalProcessingThread] shutdown: going to close sockets...2016-08-30T17:02:00.775+0800 I STORAGE [signalProcessingThread] shutdown: waiting for fs preallocator...2016-08-30T17:02:00.775+0800 I STORAGE [signalProcessingThread] shutdown: final commit...2016-08-30T17:02:00.775+0800 I JOURNAL [signalProcessingThread] journalCleanup...2016-08-30T17:02:00.775+0800 I JOURNAL [signalProcessingThread] removeJournalFiles2016-08-30T17:02:00.777+0800 I NETWORK [conn1254] end connection 192.168.1.247:58349 (0 connections now open)2016-08-30T17:02:00.779+0800 I JOURNAL [signalProcessingThread] Terminating durability thread ...2016-08-30T17:02:00.881+0800 I JOURNAL [journal writer] Journal writer thread stopped2016-08-30T17:02:00.882+0800 I JOURNAL [durability] Durability thread stopped2016-08-30T17:02:00.882+0800 I STORAGE [signalProcessingThread] shutdown: closing all files...2016-08-30T17:02:00.884+0800 I STORAGE [signalProcessingThread] closeAllFiles() finished2016-08-30T17:02:00.884+0800 I STORAGE [signalProcessingThread] shutdown: removing fs lock...2016-08-30T17:02:00.885+0800 I CONTROL [signalProcessingThread] dbexit: rc: 0###SIGTERM信号# ps -ef|grep mongod|grep rs3# ps -ef|grep mongod|grep rs3root 5465 1 1 19:14 ? 00:00:13 mongod --dbpath=/data/mongodata/rs3 --logpath=/data/mongodata/rs1/rs3.log --fork --port 28000# kill -4 5465信号 产生方式 sigint 通过ctrl+c将会对当进程发送此信号 sigterm kill命令不加参数就是发送这个信号 对进程的影响 sigint 信号被当前进程树接收到,也就是说,不仅当前进程会收到信号,它的子进程也会收到 sigterm只有当前进程收到信号,子进程不会收到。如果当前进程被kill了,那么它的子进程的父进程将会是init,也就是pid为1的进程上述信号在发出后 不再接受新的连接请求 等待现有的连接处理完毕 关闭所有打开的连接 将内存的数据写出到磁盘 安全停止2、使用系统服务脚本方式停止mongod # ps -ef|grep mongod root 5675 1 3 19:33 ? 00:00:00 /var/lib/mongodb/隐形的未来/mongod --config=/var/lib/mongodb/conf/rs2.conf root 5689 4950 0 19:33 pts/3 00:00:00 grep mongod [root@node3 conf]# [root@node3 conf]# service mongod stop Stopping mongodb: [ OK ]3、db.shutdownServer()方式 # mongo localhost:27000 > use admin > db.shutdownServer()4、使用命令行方式关闭(补充@20160901) # mongod -f /etc/mongo-m.conf --shutdown5、强制关闭mongod # kill -9 5675 缺点: 数据库直接关闭 数据丢失 数据文件容易损坏(需要进行修复)

 

 

 

 

 

 

 

版权声明:该文观点仅代表作者本人。处理文章:请发送邮件至 三1五14八八95#扣扣.com 举报,一经查实,本站将立刻删除。