dyh200896

MongoDB服务器安装及配置日志及日志使用

操作一个数据库，日志非常重要，定位问题几乎时时刻刻用到。所以如何配置，如何获取日志应该成为必备技能。以下搜集了一些参考资料，可以通过以下资料明白自己搭建MongoDB服务器如何配置日志及级别等，利于学习及备份。

举例一个稍微奇葩的应用场景，有一天某表数据莫名被删了，恢复后又莫名被删了，如果没人出来回应，有涉及到多个产品线，上百号人，那通过日志即使没人承认，也是非常快地可以知道是谁干的，是人干的还是程序干的。

其他的使用场景还有非常多，就不一一举例了。

mongod.cfg配置文件样例

#注意，缩进不对可能解析时会报错
systemLog:
#0到5，默认0
    verbosity: 1
    destination: file
    path: D:\app\tools-install\MongoDB\log\mongoserver.log
    logAppend: true
    component:
       accessControl:
        verbosity: 2
       command:
         verbosity: 2
      # COMMENT some component verbosity settings omitted for brevity
       write:
        verbosity: 2
       query:
        verbosity: 2
       index:
        verbosity: 2
       network:
        verbosity: 2
       executor:
        verbosity: 2
       control:
        verbosity: 2
storage:
    journal:
        enabled: true
    dbPath: D:\app\tools-install\MongoDB\data\db
net:
    port: 27017

#security:
    #authorization: enabled

除了在MongoDB配置文件配置外，还可以使用命令临时设置日志级别

db.getLogComponents();//查看
db.setLogLevel(2);//设置
db.setLogLevel(2, "command" );//command具体设置
db.setLogLevel(2, "query" );
db.setLogLevel(2, "write" );
db.setLogLevel(2, "index" );
db.setLogLevel(2, "network" );
db.setLogLevel(2, "executor" );
db.setLogLevel(2, "control" );
db.setLogLevel(2, "accessControl" );

几个资料的作用做下说明：

【Monogdb】MongoDB的日志系统，了解MongoDB的几类日志系统

Windows MongoDB安装配置，如何安装MongoDB，如何配置等

mongodb的配置文件详解，对MongoDB的配置文件官网说明做了中文翻译

mongo配置选项（官网），这里非常详细，参照这里学习即可

参考资料：

【Monogdb】MongoDB的日志系统

https://blog.csdn.net/stridebin/article/details/80346943

Windows MongoDB安装配置

https://www.cnblogs.com/shaosks/p/6589867.html

mongodb的配置文件详解

https://www.cnblogs.com/pbblogs/p/10178066.html

mongo配置选项（官网）

https://docs.mongodb.com/manual/reference/configuration-options/#configuration-options

mongo日志消息定义及各字段含义说明及其他延伸（官网）

https://docs.mongodb.com/manual/reference/log-messages/#log-severity-levels

获取所有日志组件及日志组件继承层次说明（官网）

https://docs.mongodb.com/manual/reference/method/db.getLogComponents/#db.getLogComponents

设置日志组件说明（官网）

https://docs.mongodb.com/manual/reference/method/db.setLogLevel/#db.setLogLevel

mongod样例systemLog日志

2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] MongoDB starting : pid=5880 port=27017 dbpath=D:\app\tools-install\MongoDB\data\db 64-bit host=helloworld
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] db version v3.6.3
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] git version: 9586e557d54ef70f9ca4b43c26892cd55257e1a5
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1u-fips  22 Sep 2016
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] allocator: tcmalloc
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] modules: enterprise 
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] build environment:
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten]     distmod: windows-64
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten]     distarch: x86_64
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten]     target_arch: x86_64
2019-07-11T11:39:40.881+0800 I CONTROL  [initandlisten] options: { config: "D:\app\tools-install\mongodb-win32-x86_64-enterprise-windows-64-3.6.3\conf\mongd.cfg", net: { port: 27017 }, storage: { dbPath: "D:\app\tools-install\MongoDB\data\db", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "D:\app\tools-install\MongoDB\log\mongoserver.log", verbosity: 1 } }
2019-07-11T11:39:40.889+0800 I -        [initandlisten] Detected data files in D:\app\tools-install\MongoDB\data\db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-07-11T11:39:40.889+0800 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3540M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2019-07-11T11:39:41.334+0800 I STORAGE  [initandlisten] WiredTiger message [1562816381:334517][5880:1997484928], txn-recover: Main recovery loop: starting at 109/24320
2019-07-11T11:39:41.556+0800 I STORAGE  [initandlisten] WiredTiger message [1562816381:556530][5880:1997484928], txn-recover: Recovering log 109 through 110
2019-07-11T11:39:41.709+0800 I STORAGE  [initandlisten] WiredTiger message [1562816381:709538][5880:1997484928], txn-recover: Recovering log 110 through 110
2019-07-11T11:39:42.298+0800 D COMMAND  [WTJournalFlusher] BackgroundJob starting: WTJournalFlusher
2019-07-11T11:39:42.299+0800 D STORAGE  [WTJournalFlusher] starting WTJournalFlusher thread
2019-07-11T11:39:42.299+0800 D COMMAND  [WTCheckpointThread] BackgroundJob starting: WTCheckpointThread
2019-07-11T11:39:42.299+0800 D STORAGE  [WTCheckpointThread] starting WTCheckpointThread thread
2019-07-11T11:39:42.431+0800 D STORAGE  [initandlisten] Slow WT transaction. Lifetime of SnapshotId 1 was 129ms
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] 
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] 
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] ** WARNING: This server is bound to localhost.
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] **          Remote systems will be unable to connect to this server. 
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] **          Start the server with --bind_ip  to specify which IP 
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] **          addresses it should serve responses from, or with --bind_ip_all to
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] **          bind to all interfaces. If this behavior is desired, start the
2019-07-11T11:39:42.475+0800 I CONTROL  [initandlisten] **          server with --bind_ip 127.0.0.1 to disable this warning.
2019-07-11T11:39:42.476+0800 I CONTROL  [initandlisten] 
2019-07-11T11:39:42.476+0800 I CONTROL  [initandlisten] Hotfix KB2731284 or later update is not installed, will zero-out data files.
2019-07-11T11:39:42.476+0800 I CONTROL  [initandlisten] 
2019-07-11T11:39:42.476+0800 I CONTROL  [initandlisten] ** WARNING: The file system cache of this machine is configured to be greater than 40% of the total memory. This can lead to increased memory pressure and poor performance.
2019-07-11T11:39:42.476+0800 I CONTROL  [initandlisten] See http://dochub.mongodb.org/core/wt-windows-system-file-cache
2019-07-11T11:39:42.476+0800 I CONTROL  [initandlisten] 
2019-07-11T11:39:42.482+0800 D COMMAND  [SNMPAgent] BackgroundJob starting: SNMPAgent
2019-07-11T11:39:42.482+0800 D NETWORK  [SNMPAgent] SNMPAgent not enabled
2019-07-11T11:39:42.484+0800 D STORAGE  [initandlisten] enter repairDatabases (to check pdfile version #)
2019-07-11T11:39:42.782+0800 D STORAGE  [initandlisten] local.startup_log: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.782+0800 D -        [initandlisten] reloading view catalog for database local
2019-07-11T11:39:42.783+0800 D STORAGE  [initandlisten]     Recovering database: admin
2019-07-11T11:39:42.784+0800 D STORAGE  [initandlisten] admin.system.users: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.784+0800 D STORAGE  [initandlisten] admin.system.version: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.784+0800 D -        [initandlisten] reloading view catalog for database admin
2019-07-11T11:39:42.785+0800 D STORAGE  [initandlisten]     Recovering database: config
2019-07-11T11:39:42.786+0800 D STORAGE  [initandlisten] config.system.sessions: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.786+0800 D -        [initandlisten] reloading view catalog for database config
2019-07-11T11:39:42.786+0800 D STORAGE  [initandlisten]     Recovering database: local
2019-07-11T11:39:42.786+0800 D STORAGE  [initandlisten]     Recovering database: sxbl
2019-07-11T11:39:42.786+0800 D STORAGE  [initandlisten] sxbl.CodeDataConfiguration: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.787+0800 D STORAGE  [initandlisten] sxbl.CsLhbsSyncData: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.788+0800 D STORAGE  [initandlisten] sxbl.CsSxslSwsxDzbzdszl: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.789+0800 D STORAGE  [initandlisten] sxbl.CsYsqSwjgConf: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.790+0800 D STORAGE  [initandlisten] sxbl.CsYsqSwsx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.790+0800 D STORAGE  [initandlisten] sxbl.CsYsqSwsxYwy: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.791+0800 D STORAGE  [initandlisten] sxbl.CsYsqSwsx_copy: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.791+0800 D STORAGE  [initandlisten] sxbl.CsZlpzPzmb: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.792+0800 D STORAGE  [initandlisten] sxbl.CsZlpzSwsxFlzl: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.792+0800 D STORAGE  [initandlisten] sxbl.CsZlpzSwsxFlzlDz: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.793+0800 D STORAGE  [initandlisten] sxbl.CsZlpzSwsxZb: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.793+0800 D STORAGE  [initandlisten] sxbl.CsZlpzTcbsYwbmFlzl: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.794+0800 D STORAGE  [initandlisten] sxbl.DmGyFlzl: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.794+0800 D STORAGE  [initandlisten] sxbl.DmGyFlzl_backup: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.795+0800 D STORAGE  [initandlisten] sxbl.DmGyFlzlbslx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.795+0800 D STORAGE  [initandlisten] sxbl.DmGyFlzlcllx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.795+0800 D STORAGE  [initandlisten] sxbl.DmGySwsx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.796+0800 D STORAGE  [initandlisten] sxbl.DmSxslSwsxSwjgSwry: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.796+0800 D STORAGE  [initandlisten] sxbl.DmSxslWsnrHqfs: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.797+0800 D STORAGE  [initandlisten] sxbl.DmYsqSxzt: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.797+0800 D STORAGE  [initandlisten] sxbl.GzlCsFlzlgl: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.798+0800 D STORAGE  [initandlisten] sxbl.aBizLogVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.798+0800 D STORAGE  [initandlisten] sxbl.applicationVerifyResultVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.799+0800 D STORAGE  [initandlisten] sxbl.arrFieldVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.800+0800 D STORAGE  [initandlisten] sxbl.auditLogVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.800+0800 D STORAGE  [initandlisten] sxbl.bizTestDataVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.800+0800 D STORAGE  [initandlisten] sxbl.bqkYhxlsVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.801+0800 D STORAGE  [initandlisten] sxbl.bqkZtVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.802+0800 D STORAGE  [initandlisten] sxbl.create_indexes_to_support_queries: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.802+0800 D STORAGE  [initandlisten] sxbl.csgySlswsxLcswsxDzbVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.803+0800 D STORAGE  [initandlisten] sxbl.data: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.804+0800 D STORAGE  [initandlisten] sxbl.dbzwh.chunks: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.805+0800 D STORAGE  [initandlisten] sxbl.dbzwh.files: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.805+0800 D STORAGE  [initandlisten] sxbl.dlStVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.806+0800 D STORAGE  [initandlisten] sxbl.dmgySwsxVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.806+0800 D STORAGE  [initandlisten] sxbl.dsrwVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.807+0800 D STORAGE  [initandlisten] sxbl.dyrglVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.808+0800 D STORAGE  [initandlisten] sxbl.dyrywVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.808+0800 D STORAGE  [initandlisten] sxbl.elementVerifyResultVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.809+0800 D STORAGE  [initandlisten] sxbl.fruit: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.809+0800 D STORAGE  [initandlisten] sxbl.fs.chunks: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.810+0800 D STORAGE  [initandlisten] sxbl.fs.files: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.812+0800 D STORAGE  [initandlisten] sxbl.inventory: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.812+0800 D STORAGE  [initandlisten] sxbl.jkcspzVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.813+0800 D STORAGE  [initandlisten] sxbl.jkddRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.814+0800 D STORAGE  [initandlisten] sxbl.jkxxRzKzVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.814+0800 D STORAGE  [initandlisten] sxbl.jkxxRzVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.815+0800 D STORAGE  [initandlisten] sxbl.jmsbTestVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.816+0800 D STORAGE  [initandlisten] sxbl.lhbsSyncDataRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.819+0800 D STORAGE  [initandlisten] sxbl.mLogEnty: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.821+0800 D STORAGE  [initandlisten] sxbl.myColl: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.822+0800 D STORAGE  [initandlisten] sxbl.names: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.823+0800 D STORAGE  [initandlisten] sxbl.nsrXydjVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.824+0800 D STORAGE  [initandlisten] sxbl.nsrzxDjbzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.824+0800 D STORAGE  [initandlisten] sxbl.nsrzxSbqcVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.825+0800 D STORAGE  [initandlisten] sxbl.orders: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.825+0800 D STORAGE  [initandlisten] sxbl.rfclxxdlbVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.826+0800 D STORAGE  [initandlisten] sxbl.rootTcbsYsqRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.827+0800 D STORAGE  [initandlisten] sxbl.rwddRwrqLogVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.827+0800 D STORAGE  [initandlisten] sxbl.sbPdfGdLogVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.828+0800 D STORAGE  [initandlisten] sxbl.sbqcrzbVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.829+0800 D STORAGE  [initandlisten] sxbl.scores: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.830+0800 D STORAGE  [initandlisten] sxbl.sparse_collection: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.830+0800 D STORAGE  [initandlisten] sxbl.sxblTipsVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.831+0800 D STORAGE  [initandlisten] sxbl.sxslShVersion: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.831+0800 D STORAGE  [initandlisten] sxbl.system.profile: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.831+0800 D STORAGE  [initandlisten] sxbl.system_profile: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.833+0800 D STORAGE  [initandlisten] sxbl.tcbsRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.833+0800 D STORAGE  [initandlisten] sxbl.testVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.834+0800 D STORAGE  [initandlisten] sxbl.thirdparty.AccessResource: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.835+0800 D STORAGE  [initandlisten] sxbl.thirdparty.SimplePermission: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.836+0800 D STORAGE  [initandlisten] sxbl.wbbwhcVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.836+0800 D STORAGE  [initandlisten] sxbl.xjgqcmcVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.837+0800 D STORAGE  [initandlisten] sxbl.xxzxHszVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.837+0800 D STORAGE  [initandlisten] sxbl.xxzxMesSendVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.838+0800 D STORAGE  [initandlisten] sxbl.xxzxMesVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.839+0800 D STORAGE  [initandlisten] sxbl.ysqCfybtjRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.840+0800 D STORAGE  [initandlisten] sxbl.ysqCsRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.841+0800 D STORAGE  [initandlisten] sxbl.ysqGyWsWszb: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.842+0800 D STORAGE  [initandlisten] sxbl.ysqGyWsWszbRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.842+0800 D STORAGE  [initandlisten] sxbl.ysqGzRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.843+0800 D STORAGE  [initandlisten] sxbl.ysqJyxxVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.844+0800 D STORAGE  [initandlisten] sxbl.ysqRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.845+0800 D STORAGE  [initandlisten] sxbl.ysqSxblAutoCommitRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.846+0800 D STORAGE  [initandlisten] sxbl.ysqSxblSplhRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.848+0800 D STORAGE  [initandlisten] sxbl.ysqSxblSxjdRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.851+0800 D STORAGE  [initandlisten] sxbl.ysqSxslSxfp: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.851+0800 D STORAGE  [initandlisten] sxbl.ysqSxslSxfp_copy: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.853+0800 D STORAGE  [initandlisten] sxbl.ysqSxsqPzxx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.853+0800 D STORAGE  [initandlisten] sxbl.ysqSxsqPzxx_copy: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.854+0800 D STORAGE  [initandlisten] sxbl.ysqSxsqSfxyxx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.854+0800 D STORAGE  [initandlisten] sxbl.ysqTbsmVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.855+0800 D STORAGE  [initandlisten] sxbl.ysqYgdRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.856+0800 D STORAGE  [initandlisten] sxbl.ysqYsqxxSx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.857+0800 D STORAGE  [initandlisten] sxbl.ysqYsqxxSxRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.857+0800 D STORAGE  [initandlisten] sxbl.ysqYzqJcjcxxVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.858+0800 D STORAGE  [initandlisten] sxbl.ysqxxTjbwVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.863+0800 D STORAGE  [initandlisten] sxbl.ysqxxVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.864+0800 D STORAGE  [initandlisten] sxbl.ysqxxZcbwVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.865+0800 D STORAGE  [initandlisten] sxbl.ywxxVo: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.868+0800 D STORAGE  [initandlisten] sxbl.yzqYzqxx: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.869+0800 D STORAGE  [initandlisten] sxbl.yzqYzqxxNeedCheckRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.870+0800 D STORAGE  [initandlisten] sxbl.yzqYzqxxRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.871+0800 D STORAGE  [initandlisten] sxbl.yzqYzqxxSdhzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.871+0800 D STORAGE  [initandlisten] sxbl.yzqYzqxxZdqfRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.872+0800 D STORAGE  [initandlisten] sxbl.zlpzSxVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.873+0800 D STORAGE  [initandlisten] sxbl.zlpzWddz: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.874+0800 D STORAGE  [initandlisten] sxbl.zlpzWdzlk: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.875+0800 D STORAGE  [initandlisten] sxbl.zlpzWsGdRwVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.875+0800 D STORAGE  [initandlisten] sxbl.zlpzxxRecogVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.876+0800 D STORAGE  [initandlisten] sxbl.zlpzxxVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.877+0800 D STORAGE  [initandlisten] sxbl.znsbSxRzVO: clearing plan cache - collection info cache reset
2019-07-11T11:39:42.877+0800 D -        [initandlisten] reloading view catalog for database sxbl
2019-07-11T11:39:42.877+0800 D STORAGE  [initandlisten] done repairDatabases
2019-07-11T11:39:42.877+0800 D STORAGE  [initandlisten] Slow WT transaction. Lifetime of SnapshotId 3 was 393ms
2019-07-11T11:39:42.878+0800 I COMMAND  [initandlisten] command admin.system.roles command: find { find: "system.roles", $db: "admin" } planSummary: EOF keysExamined:0 docsExamined:0 cursorExhausted:1 numYields:0 nreturned:0 reslen:91 locks:{ Global: { acquireCount: { r: 8, w: 1, W: 3 } }, Database: { acquireCount: { r: 2, W: 1 } }, Collection: { acquireCount: { r: 2 } } } protocol:op_msg 0ms
2019-07-11T11:39:44.386+0800 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory 'D:/app/tools-install/MongoDB/data/db/diagnostic.data'
2019-07-11T11:39:44.391+0800 D INDEX    [initandlisten] checking complete
2019-07-11T11:39:44.392+0800 D COMMAND  [TTLMonitor] BackgroundJob starting: TTLMonitor
2019-07-11T11:39:44.393+0800 D COMMAND  [ClientCursorMonitor] BackgroundJob starting: ClientCursorMonitor
2019-07-11T11:39:44.396+0800 D COMMAND  [PeriodicTaskRunner] BackgroundJob starting: PeriodicTaskRunner
2019-07-11T11:39:44.400+0800 I NETWORK  [initandlisten] waiting for connections on port 27017
2019-07-11T11:39:50.358+0800 I NETWORK  [listener] connection accepted from 127.0.0.1:50678 #1 (1 connection now open)
2019-07-11T11:39:50.360+0800 I NETWORK  [conn1] received client metadata from 127.0.0.1:50678 conn: { driver: { name: "mongo-csharp-driver", version: "0.0.0.0" }, os: { type: "Windows", name: "Microsoft Windows NT 6.1.7601 Service Pack 1", architecture: "x86_64", version: "6.1.7601.65536" }, platform: ".NET Framework 4.5" }
2019-07-11T11:39:50.360+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, client: { driver: { name: "mongo-csharp-driver", version: "0.0.0.0" }, os: { type: "Windows", name: "Microsoft Windows NT 6.1.7601 Service Pack 1", architecture: "x86_64", version: "6.1.7601.65536" }, platform: ".NET Framework 4.5" }, saslSupportedMechs: "sxbl.app", $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:223 locks:{} protocol:op_query 0ms
2019-07-11T11:39:50.362+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:1238 locks:{} protocol:op_query 0ms
2019-07-11T11:39:50.367+0800 I COMMAND  [conn1] command admin.system.users command: saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx", $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:167 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 3ms
2019-07-11T11:39:50.418+0800 I COMMAND  [conn1] command sxbl.$cmd command: saslContinue { saslContinue: 1, conversationId: 1, payload: BinData(0, 633D626977732C723D775931796D3C657A76233775535C212E2160626D534E444B5879643276587235614F7A67595A7035773641774D7971574467346B2C703D7856466E6350...), $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:108 locks:{} protocol:op_query 0ms
2019-07-11T11:39:50.419+0800 I ACCESS   [conn1] Successfully authenticated as principal app on sxbl
2019-07-11T11:39:50.420+0800 I COMMAND  [conn1] command admin.system.users command: saslContinue { saslContinue: 1, conversationId: 1, payload: BinData(0, ), $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:78 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 0ms
2019-07-11T11:39:50.420+0800 I COMMAND  [conn1] command admin.$cmd command: getLastError { getLastError: 1, $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:94 locks:{} protocol:op_query 0ms
2019-07-11T11:39:50.421+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:39:50.421+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:00.354+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:00.355+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:10.355+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:10.357+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:20.353+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:20.355+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:30.353+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:30.354+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:40.353+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:40.354+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:41.051+0800 I NETWORK  [listener] connection accepted from 127.0.0.1:50679 #2 (2 connections now open)
2019-07-11T11:40:41.052+0800 I NETWORK  [conn2] received client metadata from 127.0.0.1:50679 conn: { driver: { name: "mongo-csharp-driver", version: "0.0.0.0" }, os: { type: "Windows", name: "Microsoft Windows NT 6.1.7601 Service Pack 1", architecture: "x86_64", version: "6.1.7601.65536" }, platform: ".NET Framework 4.5" }
2019-07-11T11:40:41.052+0800 I COMMAND  [conn2] command admin.$cmd command: isMaster { isMaster: 1, client: { driver: { name: "mongo-csharp-driver", version: "0.0.0.0" }, os: { type: "Windows", name: "Microsoft Windows NT 6.1.7601 Service Pack 1", architecture: "x86_64", version: "6.1.7601.65536" }, platform: ".NET Framework 4.5" }, saslSupportedMechs: "sxbl.app", $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:223 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.053+0800 I COMMAND  [conn2] command admin.$cmd command: buildInfo { buildInfo: 1, $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:1238 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.059+0800 I COMMAND  [conn2] command sxbl.$cmd command: saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx", $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:167 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.123+0800 I COMMAND  [conn2] command sxbl.$cmd command: saslContinue { saslContinue: 1, conversationId: 1, payload: BinData(0, 633D626977732C723D373771695F42664F5E225B2A546B6E476F7240232F623962387051484E73794B564B3563446E3552523135452B6B6D493550556F2C703D624943453472...), $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:108 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.123+0800 I ACCESS   [conn2] Successfully authenticated as principal app on sxbl
2019-07-11T11:40:41.123+0800 I COMMAND  [conn2] command sxbl.$cmd command: saslContinue { saslContinue: 1, conversationId: 1, payload: BinData(0, ), $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:78 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.123+0800 I COMMAND  [conn2] command admin.$cmd command: getLastError { getLastError: 1, $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:94 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.168+0800 I NETWORK  [listener] connection accepted from 127.0.0.1:50680 #3 (3 connections now open)
2019-07-11T11:40:41.168+0800 I NETWORK  [conn3] received client metadata from 127.0.0.1:50680 conn: { driver: { name: "mongo-csharp-driver", version: "0.0.0.0" }, os: { type: "Windows", name: "Microsoft Windows NT 6.1.7601 Service Pack 1", architecture: "x86_64", version: "6.1.7601.65536" }, platform: ".NET Framework 4.5" }
2019-07-11T11:40:41.168+0800 I COMMAND  [conn3] command admin.$cmd command: isMaster { isMaster: 1, client: { driver: { name: "mongo-csharp-driver", version: "0.0.0.0" }, os: { type: "Windows", name: "Microsoft Windows NT 6.1.7601 Service Pack 1", architecture: "x86_64", version: "6.1.7601.65536" }, platform: ".NET Framework 4.5" }, saslSupportedMechs: "sxbl.app", $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:223 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.169+0800 I COMMAND  [conn3] command admin.$cmd command: buildInfo { buildInfo: 1, $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:1238 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.170+0800 I COMMAND  [conn3] command sxbl.$cmd command: saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx", $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:167 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.171+0800 I COMMAND  [conn2] command sxbl.aBizLogVo command: collStats { collstats: "aBizLogVo", $db: "sxbl" } numYields:0 reslen:20244 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_msg 46ms
2019-07-11T11:40:41.212+0800 I COMMAND  [conn3] command sxbl.$cmd command: saslContinue { saslContinue: 1, conversationId: 1, payload: BinData(0, 633D626977732C723D2530326D677C5F37235A586B60576627617129677273533075327645684A51493336317172325475484D74704E4B4C35366663642C703D54482F6E7076...), $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:108 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.212+0800 I ACCESS   [conn3] Successfully authenticated as principal app on sxbl
2019-07-11T11:40:41.212+0800 I COMMAND  [conn3] command sxbl.$cmd command: saslContinue { saslContinue: 1, conversationId: 1, payload: BinData(0, ), $readPreference: { mode: "secondaryPreferred" }, $db: "sxbl" } numYields:0 reslen:78 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.213+0800 I COMMAND  [conn3] command admin.$cmd command: getLastError { getLastError: 1, $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:94 locks:{} protocol:op_query 0ms
2019-07-11T11:40:41.249+0800 I COMMAND  [conn3] command sxbl command: dbStats { dbStats: 1, $db: "sxbl" } numYields:0 reslen:227 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { R: 1 } } } protocol:op_msg 36ms
2019-07-11T11:40:44.394+0800 D INDEX    [TTLMonitor] ns: config.system.sessions key: { lastUse: 1 } name: lsidTTLIndex
2019-07-11T11:40:44.394+0800 D INDEX    [TTLMonitor] deleted: 0
2019-07-11T11:40:44.453+0800 I NETWORK  [listener] connection accepted from 127.0.0.1:50681 #4 (4 connections now open)
2019-07-11T11:40:44.454+0800 I NETWORK  [conn4] received client metadata from 127.0.0.1:50681 conn: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.2" }, os: { type: "Windows", name: "Microsoft Windows 7", architecture: "x86_64", version: "6.1 SP1 (build 7601)" } }
2019-07-11T11:40:44.454+0800 I COMMAND  [conn4] command admin.$cmd appName: "MongoDB Shell" command: isMaster { isMaster: 1, client: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.2" }, os: { type: "Windows", name: "Microsoft Windows 7", architecture: "x86_64", version: "6.1 SP1 (build 7601)" } }, $db: "admin" } numYields:0 reslen:223 locks:{} protocol:op_query 0ms
2019-07-11T11:40:44.454+0800 I COMMAND  [conn4] command admin.$cmd appName: "MongoDB Shell" command: whatsmyuri { whatsmyuri: 1, $db: "admin" } numYields:0 reslen:47 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.455+0800 I COMMAND  [conn4] command admin.$cmd appName: "MongoDB Shell" command: buildInfo { buildinfo: 1.0, $db: "admin" } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.456+0800 I COMMAND  [conn4] command sxbl.$cmd appName: "MongoDB Shell" command: saslStart { saslStart: 1, mechanism: "SCRAM-SHA-1", payload: "xxx", $db: "sxbl" } numYields:0 reslen:164 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.472+0800 I COMMAND  [conn4] command sxbl.$cmd appName: "MongoDB Shell" command: saslContinue { saslContinue: 1, payload: BinData(0, 633D626977732C723D68524F67636F722F506F506F6A7033396D556B473957585342764450624A7A48796454414A622F444856676F5241557441664551683070376266355A4A...), conversationId: 1, $db: "sxbl" } numYields:0 reslen:93 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.473+0800 I ACCESS   [conn4] Successfully authenticated as principal app on sxbl
2019-07-11T11:40:44.473+0800 I COMMAND  [conn4] command sxbl.$cmd appName: "MongoDB Shell" command: saslContinue { saslContinue: 1, payload: BinData(0, ), conversationId: 1, $db: "sxbl" } numYields:0 reslen:63 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.475+0800 I COMMAND  [conn4] command test.$cmd appName: "MongoDB Shell" command: buildInfo { buildInfo: 1.0, $db: "test" } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.476+0800 I COMMAND  [conn4] command test.$cmd appName: "MongoDB Shell" command: isMaster { isMaster: 1.0, forShell: 1.0, $db: "test" } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:44.476+0800 I COMMAND  [conn4] command admin.$cmd appName: "MongoDB Shell" command: replSetGetStatus { replSetGetStatus: 1.0, forShell: 1.0, $db: "admin" } numYields:0 reslen:106 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:49.060+0800 I COMMAND  [conn4] command sxbl.fruit appName: "MongoDB Shell" command: find { find: "fruit", filter: {}, $db: "sxbl" } planSummary: COLLSCAN keysExamined:0 docsExamined:3 cursorExhausted:1 numYields:0 nreturned:3 reslen:209 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_msg 0ms
2019-07-11T11:40:50.353+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:50.354+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:40:53.406+0800 I COMMAND  [conn4] CMD: drop sxbl.fruit
2019-07-11T11:40:53.406+0800 D STORAGE  [conn4] dropCollection: sxbl.fruit
2019-07-11T11:40:53.406+0800 D STORAGE  [conn4] dropCollection: sxbl.fruit - dropAllIndexes start
2019-07-11T11:40:53.406+0800 D INDEX    [conn4] 	 dropAllIndexes dropping: { v: 2, key: { _id: 1 }, name: "_id_", ns: "sxbl.fruit" }
2019-07-11T11:40:53.406+0800 D STORAGE  [conn4] sxbl.fruit: clearing plan cache - collection info cache reset
2019-07-11T11:40:53.406+0800 D STORAGE  [conn4] dropCollection: sxbl.fruit - dropAllIndexes done
2019-07-11T11:40:53.406+0800 I STORAGE  [conn4] Finishing collection drop for sxbl.fruit (cd513077-dada-4c90-b515-5b63934b4665).
2019-07-11T11:40:53.407+0800 D STORAGE  [conn4] deleting metadata for sxbl.fruit @ RecordId(182)
2019-07-11T11:40:53.445+0800 D STORAGE  [conn4] WT drop of  table:index-1-2938276547367425295 res 0
2019-07-11T11:40:53.445+0800 D STORAGE  [conn4] ~WiredTigerRecordStore for: sxbl.fruit
2019-07-11T11:40:53.486+0800 D STORAGE  [conn4] WT drop of  table:collection-0-2938276547367425295 res 0
2019-07-11T11:40:53.486+0800 I COMMAND  [conn4] command sxbl.fruit appName: "MongoDB Shell" command: drop { drop: "fruit", $db: "sxbl" } numYields:0 reslen:61 locks:{ Global: { acquireCount: { r: 1, w: 1 } }, Database: { acquireCount: { W: 1 } } } protocol:op_msg 80ms
2019-07-11T11:40:55.444+0800 I COMMAND  [conn3] command sxbl.DmGyFlzl command: collStats { collstats: "DmGyFlzl", $db: "sxbl" } numYields:0 reslen:13483 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_msg 5ms
2019-07-11T11:41:00.354+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:00.356+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:10.353+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:10.353+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:20.345+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:20.345+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:20.360+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:20.360+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:30.362+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:30.363+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:40.361+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:40.361+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:44.395+0800 D INDEX    [TTLMonitor] ns: config.system.sessions key: { lastUse: 1 } name: lsidTTLIndex
2019-07-11T11:41:44.395+0800 D INDEX    [TTLMonitor] deleted: 0
2019-07-11T11:41:50.360+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:41:50.361+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms
2019-07-11T11:42:00.360+0800 I COMMAND  [conn1] command admin.$cmd command: isMaster { isMaster: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:208 locks:{} protocol:op_msg 0ms
2019-07-11T11:42:00.360+0800 I COMMAND  [conn1] command admin.$cmd command: buildInfo { buildInfo: 1, $db: "admin", $readPreference: { mode: "primaryPreferred" } } numYields:0 reslen:1223 locks:{} protocol:op_msg 0ms

你可能感兴趣的:(mongo)

MongoDB Oplog 窗口喝醉酒的小白 MongoDB 运维
在MongoDB中，oplog（操作日志）是一个特殊的日志系统，用于记录对数据库的所有写操作。oplog允许副本集成员（通常是从节点）应用主节点上已经执行的操作，从而保持数据的一致性。它是MongoDB副本集实现数据复制的基础。MongoDBOplog窗口oplog窗口是指在MongoDB副本集中，从节点可以用来同步数据的时间范围。这个窗口通常由以下因素决定：Oplog大小：oplog的大小是有限
nosql数据库技术与应用知识点皆过客，揽星河 NoSQL nosql 数据库大数据数据分析数据结构非关系型数据库
Nosql知识回顾大数据处理流程数据采集(flume、爬虫、传感器)数据存储(本门课程NoSQL所处的阶段)Hdfs、MongoDB、HBase等数据清洗(入仓)Hive等数据处理、分析(Spark、Flink等)数据可视化数据挖掘、机器学习应用(Python、SparkMLlib等)大数据时代存储的挑战(三高)高并发(同一时间很多人访问)高扩展(要求随时根据需求扩展存储)高效率(要求读写速度快)
MongoDB知识概括 GeorgeLin98 持久层 mongodb
MongoDB知识概括MongoDB相关概念单机部署基本常用命令索引-IndexSpirngDataMongoDB集成副本集分片集群安全认证MongoDB相关概念业务应用场景：传统的关系型数据库（如MySQL），在数据操作的“三高”需求以及应对Web2.0的网站需求面前，显得力不从心。解释：“三高”需求：①Highperformance-对数据库高并发读写的需求。②HugeStorage-对海量数
Mongodb Error: queryTxt ETIMEOUT xxxx.wwwdz.mongodb.net 佛一脚 error react mongodb 数据库
背景每天都能遇到奇怪的问题，做个记录，以便有缘人能得到帮助！换了一台电脑开发nextjs程序。需要连接mongodb数据，对数据进行增删改查。上一台电脑好好的程序，新电脑死活连不上mongodb数据库。同一套代码，没任何修改，搞得我怀疑人生了，打开浏览器进入mongodb官网毫无问题，也能进入线上系统查看数据，网络应该是没问题。于是我尝试了一下手机热点，这次代码能正常跑起来，连接数据库了！！！是不
springboot整合MongoDB时碰到的问题生产队队长 Database Spring All mongodb spring
1.账号总是不对，导致查不出数据，报错Auth…权鉴错误这次，我也是第一次接触MongoDB，非常的生疏springboot整合MongoDB，要在properties文件中配置账号mongodb基本语法：useDATABASE_NAME;--创建数据库showdbs;--查看我们所有的库，注意，我们刚创建的库，如果没有数据，是不会被显示的showusers;--查看当前库所有拥有的账号db.cr
java mongodb group分组使用 yank1225 mongodb java mongodb group
mongodb的关键字及介绍.mongodb的查询是有一定规则的,刚开始接触老是各种错误,参照以下内容有很多帮助https://docs.mongodb.com/manual/reference/sql-aggregation-comparison/另外出现这种错误时Apipelinestagespecificationobjectmustcontainexactlyonefield是因为条件不对
MongoDB Atlas与LangChain集成指南 afTFODguAKBF mongodb langchain 数据库 python
引言MongoDBAtlas是一款全托管的云数据库解决方案,可在AWS、Azure和GCP上使用。最新版本支持在MongoDB文档数据上进行原生向量搜索。本文将介绍如何使用LangChain将MongoDBAtlas与语言模型集成,以实现高效的向量搜索和语义缓存。安装和设置1.安装langchain-mongodb包pipinstalllangchain-mongodb向量存储LangChain提
数据库管理的利器Navicat —— 全面测评与热门产品推荐界面开发小八哥数据库 Navicat 数据库开发 sql mysql
在数据库管理领域，Navicat无疑是一款深受欢迎的软件。作为一个强大的数据库管理和开发工具，它支持多种数据库类型，包括MySQL、MariaDB、MongoDB、SQLServer、Oracle、PostgreSQL等。本文将全面测评Navicat的核心功能，同时推荐几款热门的Navicat产品。Navicat的主要特点1.跨平台支持：Navicat支持Windows、Mac和Linux平台，可
MongoDB C++库编译，windows平台+VS2015（QT中也可以用） hp_cpp C++
编译准备工作：（1）mongo-c-driver下载地址：https://github.com/mongodb/mongo-c-driver/releases下载最新版：mongo-c-driver1.12.0的Soucecode版（2）mongodb/mongo-cxx-driver下载地址：https://github.com/mongodb/mongo-cxx-driver/releases
使用docker部署MongoDB数据库数据小白的进阶之路数据库 docker mongodb
最近由于工作需要搭建MongoDB数据库：将解析的车端采集的数据写入到数据库，由于MongoDB高可用、海量扩展、灵活数据的模型，因此选用MongoDB数据库；由于现公司只有服务器，因此考虑容器化部署MongoDB数据，特此记录一下~一、镜像拉取使用如下命令拉取最新MongoDB镜像dockerpullmongo二、创建MongoDB容器2.1创建宿主机目录执行如下代码：mkdir-p/home/
MongoDB数据库 weixin_34104341 数据库 json shell
一简介MongoDB是一款强大、灵活、且易于扩展的通用型数据库1.易用性MongoDB是一个面向文档（document-oriented）的数据库，而不是关系型数据库。不采用关系型主要是为了获得更好得扩展性。当然还有一些其他好处，与关系数据库相比，面向文档的数据库不再有“行“（row）的概念取而代之的是更为灵活的“文档”（document）模型。通过在文档中嵌入文档和数组，面向文档的方法能够仅使用
【Docker】MongoDB 容器化部署轻云UC 运维部署 mongodb docker 数据库
MongoDBdocker容器化部署MongoDB标准软件基于BitnamiMongoDB构建。当前版本未7.0.5你可以通过轻云UC部署工具直接安装部署，也可以手动按如下文档操作配置文件地址:https://gitee.com/qingplus/qingcloud-platformQinghubStudio在线体验初始化一个新实例使用Docker容器网络，应用程序容器可以轻松访问容器内运行的Mo
MongoDB ：第五章：MongoDB 插入更新删除查询文档 2401_84558091 作者\/mongodb 数据库
“_id”:ObjectId(“56064f89ade2f21f36b03136”),“title”:“MongoDB”,“description”:“MongoDB是一个Nosql数据库”,“by”:“菜鸟教程”,“url”:“http://www.runoob.com”,“tags”:[“mongodb”,“database”,“NoSQL”],“likes”:100}可以看到标题(title
数据库有关c语言 h海棠溪数据库学习 c语言 linux
数据库的概念SQL（StructuredQueryLanguage）是一种专门用来与数据库进行交互的编程语言，它允许用户查询、更新和管理关系型数据库中的数据。关系型数据库是基于表（Table）的数据库，其中表由行（Row）和列（Column）组成，每一行代表一个记录（Record），每一列代表一个字段（Field）。非关系型数据库MongoDB1、分类：大型中型小型ORACLEMYSQL/MSSQ
使用 MongoDB 构建 AI：Patronus 如何自动进行大语言模型评估来增强对生成式 AI 的信心 MongoDB 数据平台 AI应用客户案例人工智能 mongodb
大语言模型可能不可靠，这几乎算不上头条新闻。对于某些用例，这可能会带来不便。而对于其他行业，尤其是受监管行业，后果则要严重得多。于是，业内首个大语言模型自动评估平台PatronusAI应运而生。PatronusAI由MetaAI和MetaRealityLabs的机器学习专家创立，旨在增强企业对生成式AI应用程序的信心，在塑造值得信赖的AI生态方面处于领先地位。Patronus联合创始人兼首席技术官
MongoDB-副本集PSA架构搭建配置手册玩亚索的小孔 MongoDB MongoDB 副本集 PSA
1安装配置------------------------------------------------------------------------------------机器准备：•系统：RedHatEnterpriseLinuxServerrelease7.3(Maipo)•MongoDB版本：mongodb-linux-x86_64-rhel70-3.4.16•下载地址:http://
解决方案| MongoDB PSA 架构痛点以及如何应对？ MongoDB中文社区 MongoDB mongodb 架构数据库
一.背景最近MongoDB群里面有群友遇到2次重启MongoDB后一直处于实例恢复状态(应用OPLOG)，多达几天甚至更长才完成重启，通常MongoDB副本集三个实例作为标准，重启主库会发生重新选出新主节点(通常在12s内完成)重新对外服务，通常不符合官方标准化或者内部发生异常导致的。经过了解副本集采用PSA架构且存在一个数据从节点不可达的情况(甚至有的从节点宕机几个月没有发现)，来分析这些情况以
MongoDB之写关注及PSA架构相关问题吃饭端住碗 MongoDB mongodb 架构数据库
MongoDB的写关注主要指定了写入操作的确认级别。具体来讲就是客户端在向MongoDB执行比如delete、insert、update等相关写入操作时，MongoDB的写入行为，比如是否立刻刷盘、是否需要等待Secondary节点确认等。写关注说明写关注配置主要包含以下3个字段：{w:,j:,wtimeout:}w选项指定了写入操作需要等待确认的副本集成员个数。取值如下：“majority”：写
mongoDB 对一个做了索引的字段，要不要给默认值？ hongkid mongodb 数据库
引言在设计数据库模式时，如何处理字段的默认值是一个值得深入探讨的话题。对于MongoDB这样的NoSQL数据库来说，灵活性是其一大特点，但这同时也意味着开发者需要更加谨慎地考虑数据的一致性和完整性。本文将探讨在一个已创建索引的字段上，在插入文档时是否应该显式设置默认值的问题，并给出具体的建议。MongoDB中的索引与字段设置在MongoDB中，索引可以帮助提高查询性能，特别是在处理大规模数据集时。
MongoDB-聚合查询操作介绍侯晓阳丶 MongoDB mongodb 数据库 linux dba 经验分享
目录前言db.collection.aggregate()db.collection.aggregate()示例一db.collection.aggregate()示例二复杂的聚合操作通过mongoimport导入测试数据复杂的聚合操作示例聚合操作的偏好设置-project函数聚合操作的偏好设置-unwind函数前言MongoDB聚合操作相当于关系型数据库SQL语句的"groupby"、“orde
Docker搭建MongoDB Replica Set高可用集群+数据丢失&被黑解决+自动备份与恢复脚本+持久化慢查询记录秋风お亦冷运维企业实战笔录运维 docker mongodb 数据库
文章目录引节点规划配置文件创建持久化目录创建并推送证书启动临时容器修改配置文件单节点参考mongod.confdocker-compose.ymlReplicaSet参考mongod.confdocker-compose.yml部署与配置部署集群配置集群验证集群增删节点增加节点删除节点查看节点常用命令重置集群备份数据关闭服务删除持久化数据启动集群配置集群验证集群创建用户验证集群用户管理权限说明创建
vue+jsonrpc+mongoDB文件传输解决方案（任意格式文件） weideng_san 前端 java 文件传输 jsonrpc mongoDB vue
环境及需求：前端采用vue；后端采用spring，但是只用到了spring的对象注入功能，未使用springweb相关功能。前后端通信采用jsonrpc，现需要在前端选中文件（格式未知，上传到后端，后端将其存储在mongoDB中）。背景：springweb可以直接使用controller接受MultipartFile对象；但是jsonrpc不能直接传输文件类型，jsonrpc是轻量级通信框架，擅长
基础爬虫 requests selenium aiohttp BeautifulSoup pyQuery Xpath&CssSelector 肯定是疯了
http://47.101.52.166/blog/back/python/%E7%88%AC%E8%99%AB.html请求requestsseleniumaiohttp*处理BeautifulSouppyQueryXpath&CssSelector*存储pymysqlPyMongoredisaiomysql*Scrapy
python公众号文章_python采集微信公众号文章 Coming May python公众号文章
本文实例为大家分享了python采集微信公众号文章的具体代码，供大家参考，具体内容如下在python一个子目录里存2个文件，分别是：采集公众号文章.py和config.py。代码如下：1.采集公众号文章.pyfromurllib.parseimporturlencodeimportpymongoimportrequestsfromlxml.etreeimportXMLSyntaxErrorfrom
mongodb 在 Windows 环境下迁移数据库的问题 Eagsen CEO 数据库 mongodb
mongodb是一款非常优秀的文档数据库，它的社区版本是免费的。但是mongodb的迁移和其他传统的关系数据库不太一样，通过官方提供的图形化的客户端工具无法备份和迁移，需要下载命令行工具进行。首先下载命令行工具：DownloadMongoDBCommandLineDatabaseTools|MongoDBWindows安装后，使用管理员身份打开cmd命令窗口，导航到安装目录的bin目录下，如果是默
python网络爬虫（五）——爬取天气预报光电的一只菜鸡 python python 爬虫开发语言
1.注册高德天气key 点击高德天气，然后按照开发者文档完成key注册；作为爬虫练习项目之一。从高德地图json数据接口获取天气，可以获取某省的所有城市天气，高德地图的这个接口还能获取县城的天气。其天气查询API服务地址为https://restapi.amap.com/v3/weather/weatherInfo?parameters，若要获取某城市的天气推荐2.安装MongoDB Mong
Spring常用中间件贺仙姑 spring 中间件 java
1.数据库中间件（1）MySQL:常用的关系型数据库，支持JDBC和JPA。（2）PostgreSQL:功能强大的开源关系型数据库，支持复杂查询。（3）MongoDB:NoSQL数据库，适合存储非结构化数据。（4）Redis:内存数据结构存储，常用于缓存和消息队列。2.消息队列（1）RabbitMQ:开源消息代理，支持多种消息协议，适合异步处理。（2）Kafka:分布式流处理平台，适合处理大规模数
Pyhton抓取BOSS直聘职位描述和数据清洗，很简单没有那么难嗨学编程
一、抓取详细的职位描述信息详情页分析Python学习资料或者需要代码、视频加Python学习群：960410445在详情页中，比较重要的就是职位描述和工作地址这两个由于在页面代码中岗位职责和任职要求是在一个div中的，所以在抓的时候就不太好分，后续需要把这个连体婴儿，分开分析。爬虫用到的库使用的库有：requestsBeautifulSoup4pymongoPython代码代码easy，初学者都能
Node.js 数据库操作详解：构建高效的数据持久化层 Switch616 前端 node.js 数据库运维服务器系统架构前端框架前端
Node.js数据库操作详解：构建高效的数据持久化层目录MongoDB使用mongoose连接MongoDB定义模型和数据验证实现CRUD操作️MySQL使用mysql或mysql2模块连接MySQL执行SQL查询处理结果和错误SQLite使用sqlite3模块连接SQLite执行SQL查询处理事务MongoDB使用mongoose连接MongoDBmongoose是一个为MongoDB提供对象数
MongoDB的WiredTiger存储引擎云掣YUNCHE mongodb 数据库
作者：太阳从MongoDB3.2开始，MongoDB实例默认的存储引擎为WiredTiger，WiredTiger存储引擎具体以下几大优点：文档级并发将数据持久化到磁盘快照和checkpoint数据压缩本地数据加密一、文档级别并发1、WiredTiger使用文档级别并发，意味着在同一时间，MongoDB实例允许多个对不同文档间的写操作并发执行（复制应用oplog时同样可以做到文档级并发应用）。2、
ASM系列五利用TreeApi 解析生成Class lijingyao8206 ASM 字节码动态生成 ClassNode TreeAPI
前面CoreApi的介绍部分基本涵盖了ASMCore包下面的主要API及功能，其中还有一部分关于MetaData的解析和生成就不再赘述。这篇开始介绍ASM另一部分主要的Api。TreeApi。这一部分源码是关联的asm-tree-5.0.4的版本。在介绍前，先要知道一点， Tree工程的接口基本可以完
链表树——复合数据结构应用实例 bardo 数据结构树型结构表结构设计链表菜单排序
我们清楚：数据库设计中，表结构设计的好坏，直接影响程序的复杂度。所以，本文就无限级分类（目录）树与链表的复合在表设计中的应用进行探讨。当然，什么是树，什么是链表，这里不作介绍。有兴趣可以去看相关的教材。需求简介：经常遇到这样的需求，我们希望能将保存在数据库中的树结构能够按确定的顺序读出来。比如，多级菜单、组织结构、商品分类。更具体的，我们希望某个二级菜单在这一级别中就是第一个。虽然它是最后
为啥要用位运算代替取模呢 chenchao051 位运算哈希汇编
在hash中查找key的时候，经常会发现用&取代%，先看两段代码吧， JDK6中的HashMap中的indexFor方法： /** * Returns index for hash code h. */ static int indexFor(int h, int length) {
最近的情况麦田的设计者生活感悟计划软考想
今天是2015年4月27号整理一下最近的思绪以及要完成的任务 1、最近在驾校科目二练车，每周四天，练三周。其实做什么都要用心，追求合理的途径解决。为
PHP去掉字符串中最后一个字符的方法 IT独行者 PHP 字符串
今天在PHP项目开发中遇到一个需求，去掉字符串中的最后一个字符原字符串1,2,3,4,5,6, 去掉最后一个字符","，最终结果为1,2,3,4,5,6 代码如下： $str = "1,2,3,4,5,6,"; $newstr = substr($str,0,strlen($str)-1); echo $newstr;
hadoop在linux上单机安装过程 _wy_ linux hadoop
1、安装JDK jdk版本最好是1.6以上，可以使用执行命令java -version查看当前JAVA版本号，如果报命令不存在或版本比较低，则需要安装一个高版本的JDK，并在/etc/profile的文件末尾，根据本机JDK实际的安装位置加上以下几行： export JAVA_HOME=/usr/java/jdk1.7.0_25
JAVA进阶----分布式事务的一种简单处理方法无量多系统交互分布式事务
每个方法都是原子操作：提供第三方服务的系统，要同时提供执行方法和对应的回滚方法 A系统调用B,C,D系统完成分布式事务 =========执行开始======== A.aa(); try { B.bb(); } catch(Exception e) { A.rollbackAa(); } try { C.cc(); } catch(Excep
安墨移动广告：移动DSP厚积薄发引领未来广告业发展命脉矮蛋蛋 hadoop 互联网
　　“谁掌握了强大的DSP技术，谁将引领未来的广告行业发展命脉。”2014年，移动广告行业的热点非移动DSP莫属。各个圈子都在纷纷谈论，认为移动DSP是行业突破点，一时间许多移动广告联盟风起云涌，竞相推出专属移动DSP产品。　　到底什么是移动DSP呢? 　　DSP(Demand-SidePlatform)，就是需求方平台，为解决广告主投放的各种需求，真正实现人群定位的精准广
myelipse设置 alafqq IP
在一个项目的完整的生命周期中，其维护费用，往往是其开发费用的数倍。因此项目的可维护性、可复用性是衡量一个项目好坏的关键。而注释则是可维护性中必不可少的一环。注释模板导入步骤安装方法：打开eclipse/myeclipse 选择 window-->Preferences-->JAVA-->Code-->Code
java数组百合不是茶 java数组
java数组的声明创建初始化； java支持C语言数组中的每个数都有唯一的一个下标一维数组的定义声明： int[] a = new int[3];声明数组中有三个数int[3] int[] a 中有三个数，下标从0开始，可以同过for来遍历数组中的数
javascript读取表单数据 bijian1013 JavaScript
利用javascript读取表单数据，可以利用以下三种方法获取： 1、通过表单ID属性：var a = document.getElementByIdx_x_x("id"); 2、通过表单名称属性：var b = document.getElementsByName("name"); 3、直接通过表单名字获取：var c = form.content.
探索JUnit4扩展：使用Theory bijian1013 java JUnit Theory
理论机制（Theory）一.为什么要引用理论机制（Theory）当今软件开发中，测试驱动开发（TDD — Test-driven development）越发流行。为什么 TDD 会如此流行呢？因为它确实拥有很多优点，它允许开发人员通过简单的例子来指定和表明他们代码的行为意图。 TDD 的优点： &nb
[Spring Data Mongo一]Spring Mongo Template操作MongoDB bit1129 template
什么是Spring Data Mongo Spring Data MongoDB项目对访问MongoDB的Java客户端API进行了封装，这种封装类似于Spring封装Hibernate和JDBC而提供的HibernateTemplate和JDBCTemplate，主要能力包括 1. 封装客户端跟MongoDB的链接管理 2. 文档-对象映射，通过注解:@Document(collectio
【Kafka八】Zookeeper上关于Kafka的配置信息 bit1129 zookeeper
问题： 1. Kafka的哪些信息记录在Zookeeper中 2. Consumer Group消费的每个Partition的Offset信息存放在什么位置 3. Topic的每个Partition存放在哪个Broker上的信息存放在哪里 4. Producer跟Zookeeper究竟有没有关系？没有关系！！！ //consumers、config、brokers、cont
java OOM内存异常的四种类型及异常与解决方案 ronin47 java OOM 内存异常
　OOM异常的四种类型：　　　　　一：　StackOverflowError ：通常因为递归函数引起（死递归，递归太深）。-Xss 128k 一般够用。　二：　out Of memory: PermGen Space：通常是动态类大多，比如web 服务器自动更新部署时引起。-Xmx
java-实现链表反转-递归和非递归实现 bylijinnan java
20120422更新：对链表中部分节点进行反转操作，这些节点相隔k个： 0->1->2->3->4->5->6->7->8->9 k=2 8->1->6->3->4->5->2->7->0->9 注意1 3 5 7 9 位置是不变的。解法：将链表拆成两部分： a.0-&
Netty源码学习-DelimiterBasedFrameDecoder bylijinnan java netty
看DelimiterBasedFrameDecoder的API，有举例：接收到的ChannelBuffer如下： +--------------+ | ABC\nDEF\r\n | +--------------+ 经过DelimiterBasedFrameDecoder(Delimiters.lineDelimiter())之后，得到： +-----+----
linux的一些命令 -查看cc攻击-网口ip统计等 hotsunshine linux
Linux判断CC攻击命令详解 2011年12月23日 ⁄ 安全 ⁄ 暂无评论查看所有80端口的连接数 netstat -nat|grep -i '80'|wc -l 对连接的IP按连接数量进行排序 netstat -ntu | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -n 查看TCP连接状态 n
Spring获取SessionFactory ctrain sessionFactory
String sql = "select sysdate from dual"; WebApplicationContext wac = ContextLoader.getCurrentWebApplicationContext(); String[] names = wac.getBeanDefinitionNames(); for(int i=0; i&
Hive几种导出数据方式 daizj hive 数据导出
Hive几种导出数据方式 1.拷贝文件如果数据文件恰好是用户需要的格式，那么只需要拷贝文件或文件夹就可以。 hadoop fs –cp source_path target_path 2.导出到本地文件系统 --不能使用insert into local directory来导出数据，会报错 --只能使用
编程之美 dcj3sjt126com 编程 PHP 重构
我个人的 PHP 编程经验中，递归调用常常与静态变量使用。静态变量的含义可以参考 PHP 手册。希望下面的代码，会更有利于对递归以及静态变量的理解 header("Content-type: text/plain"); function static_function () { static $i = 0; if ($i++ < 1
Android保存用户名和密码 dcj3sjt126com android
转自：http://www.2cto.com/kf/201401/272336.html 我们不管在开发一个项目或者使用别人的项目，都有用户登录功能，为了让用户的体验效果更好，我们通常会做一个功能，叫做保存用户，这样做的目地就是为了让用户下一次再使用该程序不会重新输入用户名和密码，这里我使用3种方式来存储用户名和密码 1、通过普通的txt文本存储 2、通过properties属性文件进行存
Oracle 复习笔记之同义词 eksliang Oracle 同义词 Oracle synonym
转载请出自出处：http://eksliang.iteye.com/blog/2098861 1.什么是同义词同义词是现有模式对象的一个别名。概念性的东西，什么是模式呢？创建一个用户，就相应的创建了一个模式。模式是指数据库对象，是对用户所创建的数据对象的总称。模式对象包括表、视图、索引、同义词、序列、过
Ajax案例 gongmeitao Ajax jsp
数据库采用Sql Server2005 项目名称为:Ajax_Demo 1.com.demo.conn包 package com.demo.conn; import java.sql.Connection;import java.sql.DriverManager;import java.sql.SQLException; //获取数据库连接的类public class DBConnec
ASP.NET中Request.RawUrl、Request.Url的区别 hvt .net Web C#asp.net hovertree
如果访问的地址是：http://h.keleyi.com/guestbook/addmessage.aspx?key=hovertree%3C&n=myslider#zonemenu那么Request.Url.ToString() 的值是：http://h.keleyi.com/guestbook/addmessage.aspx?key=hovertree<&
SVG 教程（七）SVG 实例，SVG 参考手册天梯梦 svg
SVG 实例在线实例下面的例子是把SVG代码直接嵌入到HTML代码中。谷歌Chrome，火狐，Internet Explorer9，和Safari都支持。注意：下面的例子将不会在Opera运行，即使Opera支持SVG - 它也不支持SVG在HTML代码中直接使用。 SVG 实例 SVG基本形状一个圆矩形不透明矩形一个矩形不透明2 一个带圆角矩
事务管理 luyulong java spring 编程事务
事物管理 spring事物的好处为不同的事物API提供了一致的编程模型支持声明式事务管理提供比大多数事务API更简单更易于使用的编程式事务管理API 整合spring的各种数据访问抽象 TransactionDefinition 定义了事务策略 int getIsolationLevel()得到当前事务的隔离级别 READ_COMMITTED
基础数据结构和算法十一：Red-black binary search tree sunwinner Algorithm Red-black
The insertion algorithm for 2-3 trees just described is not difficult to understand; now, we will see that it is also not difficult to implement. We will consider a simple representation known
centos同步时间 stunizhengjia linux 集群同步时间
做了集群，时间的同步就显得非常必要了。以下是查到的如何做时间同步。在CentOS 5不再区分客户端和服务器，只要配置了NTP，它就会提供NTP服务。 1)确认已经ntp程序包： # yum install ntp 2)配置时间源（默认就行，不需要修改） # vi /etc/ntp.conf server pool.ntp.o
ITeye 9月技术图书有奖试读获奖名单公布 ITeye管理员 ITeye
ITeye携手博文视点举办的9月技术图书有奖试读活动已圆满结束，非常感谢广大用户对本次活动的关注与参与。 9月试读活动回顾：http://webmaster.iteye.com/blog/2118112本次技术图书试读活动的优秀奖获奖名单及相应作品如下（优秀文章有很多，但名额有限，没获奖并不代表不优秀）：《NFC：Arduino、Andro