Mongo warning: log line attempted (36kB) over max size (10kB)
up vote
0
down vote
favorite
I have used mongodb running with codeigiter.
However, when I checked the log, I discovered the error content.
I COMMAND [conn80191] warning: log line attempted (36kB) over max
size (10kB), printing beginning and end ... command news.post command:
count { count: "post", query: { active: 1, id: { $in: [ 0, 258195,
258201] } }, $db: "news" } planSummary: IXSCAN { id: 1 }
keysExamined:8361 docsExamined:4329 numYields:84 reslen:44 locks:{
Global: { acquireCount: { r: 170 } }, Database: { acquireCount: { r:
85 } }, Collection: { acquireCount: { r: 85 } } } protocol:op_query
1447ms
Lots of requests,
We wish everyone help.
Thanks!
mongodb
edited Nov 17 at 10:49
Sagar Zala
2,30741235
asked Nov 17 at 10:42
Phan Hồng Văn
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I have used mongodb running with codeigiter.
However, when I checked the log, I discovered the error content.
I COMMAND [conn80191] warning: log line attempted (36kB) over max
size (10kB), printing beginning and end ... command news.post command:
count { count: "post", query: { active: 1, id: { $in: [ 0, 258195,
258201] } }, $db: "news" } planSummary: IXSCAN { id: 1 }
keysExamined:8361 docsExamined:4329 numYields:84 reslen:44 locks:{
Global: { acquireCount: { r: 170 } }, Database: { acquireCount: { r:
85 } }, Collection: { acquireCount: { r: 85 } } } protocol:op_query
1447ms
Lots of requests,
We wish everyone help.
Thanks!
mongodb
edited Nov 17 at 10:49
Sagar Zala
2,30741235
asked Nov 17 at 10:42
Phan Hồng Văn
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Server log messages are not really a topic for Stack Overflow. You can ask about configuring those on dba.stackexchange.com instead. From a "coding" perspective the message is essentially triggered by excessively long query statements. A likely cause of which is commonly putting 1000's of arguments within$in, which you really should not do
– Neil Lunn
Nov 18 at 22:08
Further to the error message, the max line size MongoDB will log is 10kB. You have a slow query (>100ms) which is by default logged by MongoDB. However the whole log line which includes your query is 36kB, which is more than 3x the maximum log line. Note that a ~10kB query is already big, so a ~36kB query is excessively big and will not be performant (hence the query being slow). You might want to revisit your queries to make sure you don't have such a big query.
– Kevin Adistambha
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have used mongodb running with codeigiter.
However, when I checked the log, I discovered the error content.
I COMMAND [conn80191] warning: log line attempted (36kB) over max
size (10kB), printing beginning and end ... command news.post command:
count { count: "post", query: { active: 1, id: { $in: [ 0, 258195,
258201] } }, $db: "news" } planSummary: IXSCAN { id: 1 }
keysExamined:8361 docsExamined:4329 numYields:84 reslen:44 locks:{
Global: { acquireCount: { r: 170 } }, Database: { acquireCount: { r:
85 } }, Collection: { acquireCount: { r: 85 } } } protocol:op_query
1447ms
Lots of requests,
We wish everyone help.
Thanks!
mongodb
edited Nov 17 at 10:49
Sagar Zala
2,30741235
asked Nov 17 at 10:42
Phan Hồng Văn
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have used mongodb running with codeigiter.
However, when I checked the log, I discovered the error content.
I COMMAND [conn80191] warning: log line attempted (36kB) over max
size (10kB), printing beginning and end ... command news.post command:
count { count: "post", query: { active: 1, id: { $in: [ 0, 258195,
258201] } }, $db: "news" } planSummary: IXSCAN { id: 1 }
keysExamined:8361 docsExamined:4329 numYields:84 reslen:44 locks:{
Global: { acquireCount: { r: 170 } }, Database: { acquireCount: { r:
85 } }, Collection: { acquireCount: { r: 85 } } } protocol:op_query
1447ms
Lots of requests,
We wish everyone help.
Thanks!
mongodb
mongodb
edited Nov 17 at 10:49
Sagar Zala
2,30741235
asked Nov 17 at 10:42
Phan Hồng Văn
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 17 at 10:49
Sagar Zala
2,30741235
asked Nov 17 at 10:42
Phan Hồng Văn
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 17 at 10:49
Sagar Zala
2,30741235
edited Nov 17 at 10:49
Sagar Zala
2,30741235
edited Nov 17 at 10:49
Sagar Zala
2,30741235
2,30741235
asked Nov 17 at 10:42
Phan Hồng Văn
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 17 at 10:42
Phan Hồng Văn
1
asked Nov 17 at 10:42
Phan Hồng Văn
1
1
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Phan Hồng Văn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Server log messages are not really a topic for Stack Overflow. You can ask about configuring those on dba.stackexchange.com instead. From a "coding" perspective the message is essentially triggered by excessively long query statements. A likely cause of which is commonly putting 1000's of arguments within$in, which you really should not do
– Neil Lunn
Nov 18 at 22:08
Further to the error message, the max line size MongoDB will log is 10kB. You have a slow query (>100ms) which is by default logged by MongoDB. However the whole log line which includes your query is 36kB, which is more than 3x the maximum log line. Note that a ~10kB query is already big, so a ~36kB query is excessively big and will not be performant (hence the query being slow). You might want to revisit your queries to make sure you don't have such a big query.
– Kevin Adistambha
yesterday
add a comment |
Server log messages are not really a topic for Stack Overflow. You can ask about configuring those on dba.stackexchange.com instead. From a "coding" perspective the message is essentially triggered by excessively long query statements. A likely cause of which is commonly putting 1000's of arguments within$in, which you really should not do
– Neil Lunn
Nov 18 at 22:08
Further to the error message, the max line size MongoDB will log is 10kB. You have a slow query (>100ms) which is by default logged by MongoDB. However the whole log line which includes your query is 36kB, which is more than 3x the maximum log line. Note that a ~10kB query is already big, so a ~36kB query is excessively big and will not be performant (hence the query being slow). You might want to revisit your queries to make sure you don't have such a big query.
– Kevin Adistambha
yesterday
Server log messages are not really a topic for Stack Overflow. You can ask about configuring those on dba.stackexchange.com instead. From a "coding" perspective the message is essentially triggered by excessively long query statements. A likely cause of which is commonly putting 1000's of arguments within
$in, which you really should not do– Neil Lunn
Nov 18 at 22:08
Server log messages are not really a topic for Stack Overflow. You can ask about configuring those on dba.stackexchange.com instead. From a "coding" perspective the message is essentially triggered by excessively long query statements. A likely cause of which is commonly putting 1000's of arguments within
$in, which you really should not do– Neil Lunn
Nov 18 at 22:08
Further to the error message, the max line size MongoDB will log is 10kB. You have a slow query (>100ms) which is by default logged by MongoDB. However the whole log line which includes your query is 36kB, which is more than 3x the maximum log line. Note that a ~10kB query is already big, so a ~36kB query is excessively big and will not be performant (hence the query being slow). You might want to revisit your queries to make sure you don't have such a big query.
– Kevin Adistambha
yesterday
Further to the error message, the max line size MongoDB will log is 10kB. You have a slow query (>100ms) which is by default logged by MongoDB. However the whole log line which includes your query is 36kB, which is more than 3x the maximum log line. Note that a ~10kB query is already big, so a ~36kB query is excessively big and will not be performant (hence the query being slow). You might want to revisit your queries to make sure you don't have such a big query.
– Kevin Adistambha
yesterday
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Phan Hồng Văn is a new contributor. Be nice, and check out our Code of Conduct.
Phan Hồng Văn is a new contributor. Be nice, and check out our Code of Conduct.
Phan Hồng Văn is a new contributor. Be nice, and check out our Code of Conduct.
Phan Hồng Văn is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53350436%2fmongo-warning-log-line-attempted-36kb-over-max-size-10kb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Server log messages are not really a topic for Stack Overflow. You can ask about configuring those on dba.stackexchange.com instead. From a "coding" perspective the message is essentially triggered by excessively long query statements. A likely cause of which is commonly putting 1000's of arguments within
$in, which you really should not do– Neil Lunn
Nov 18 at 22:08
Further to the error message, the max line size MongoDB will log is 10kB. You have a slow query (>100ms) which is by default logged by MongoDB. However the whole log line which includes your query is 36kB, which is more than 3x the maximum log line. Note that a ~10kB query is already big, so a ~36kB query is excessively big and will not be performant (hence the query being slow). You might want to revisit your queries to make sure you don't have such a big query.
– Kevin Adistambha
yesterday