Comments on: Don’t Use MongoDB Profiling Level 1 https://www.percona.com/blog/dont-use-mongodb-profiling-level-1/ Tue, 23 Jun 2020 12:38:04 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Akira Kurogane https://www.percona.com/blog/dont-use-mongodb-profiling-level-1/#comment-10972389 Tue, 23 Jun 2020 12:38:04 +0000 https://www.percona.com/blog/?p=63376#comment-10972389 v4.4 update: I thought I saw https://jira.mongodb.org/browse/SERVER-4785 and/or https://jira.mongodb.org/browse/SERVER-5266 as one of the “4.3 Desired” or “4.3 Required” items several months ago, but maybe that was just a daydream. It’s in Backlog now and won’t be 4.4.

]]> By: asaSAS https://www.percona.com/blog/dont-use-mongodb-profiling-level-1/#comment-10971525 Mon, 09 Dec 2019 07:30:49 +0000 https://www.percona.com/blog/?p=63376#comment-10971525 Wait a minute. System.profile can be set as a capped collection, did you try it?

]]> By: Mark Callaghan https://www.percona.com/blog/dont-use-mongodb-profiling-level-1/#comment-10971445 Sat, 16 Nov 2019 20:16:06 +0000 https://www.percona.com/blog/?p=63376#comment-10971445 Thank you. Now I can file the issue on jira

]]> By: Akira Kurogane https://www.percona.com/blog/dont-use-mongodb-profiling-level-1/#comment-10971443 Sat, 16 Nov 2019 04:57:57 +0000 https://www.percona.com/blog/?p=63376#comment-10971443 https://jira.mongodb.org/browse/SERVER-18946 (from 2015), with related SERVER-4785 (2012).

We can hope that it might be fixed in v4.4 I guess. (I can’t see any patch as being backward compatible due to it probably having small user interface changes).

]]> By: Mark Callaghan https://www.percona.com/blog/dont-use-mongodb-profiling-level-1/#comment-10971442 Fri, 15 Nov 2019 17:40:57 +0000 https://www.percona.com/blog/?p=63376#comment-10971442 Please file a feature request and list the URL in this post

]]>