Log file Viewer

[00:45:04] <jamespharvey20> If journaling is enabled, must mongodb always be shutdown cleanly? I ask because github::rpm/mongod.service allows systemd to kill mongod after waiting only 90 seconds for it to stop running. I'm wondering if with journaling, if this is OK, or if it should be modified to disable any timeout. On my 450G MongoDB database with 64G RAM and 16G swap, a clean "db.shutdownServer()" can taken an hour. Is there

[00:45:06] <jamespharvey20> reason to delay a reboot to wait for this?

[03:59:53] <sameert> I recently came across intresting issue. I have a sharded cluster which has two replication sets with 2 secondaries. On my primaries, there were 300-400 connections at a point in time, shortly after sometime around a minutes spane, there were almost read and write connections in total 1200 spiked over primaries. Read and write ticket availability went down to 0 for few seconds. Cluster was non responsive during that time. We

[03:59:53] <sameert> have nginx at web level and node js for application layer. What might have caused this? During month end cluster manages more then this load.

[09:49:13] <troop> hello, full text search doesn't work with 3 characters string but works with 4 characters string. how can I set it up?