Sfrgttk

How to get the first element while continue streaming?

Can a Trickery Domain cleric cast a spell through the Invoke Duplicity clone while inside a Forcecage?

What is better: yes / no radio, or simple checkbox?

PTIJ: Mordechai mourning

Where is the fallacy here?

How do you say “my friend is throwing a party, do you wanna come?” in german

I can't die. Who am I?

What is the meaning of "notice to quit at once" and "Lotty points”

Can we carry rice to Japan?

Is divide-by-zero a security vulnerability?

Why doesn't "adolescent" take any articles in "listen to adolescent agonising"?

Where is this quote about overcoming the impossible said in "Interstellar"?

Wardrobe above a wall with fuse boxes

How to fix my table, centering of columns

An Undercover Army

How to kill a localhost:8080

A bug in Excel? Conditional formatting for marking duplicates also highlights unique value

Was it really inappropriate to write a pull request for the company I interviewed with?

How does insurance birth control work?

Draw bounding region by list of points

Caulking a corner instead of taping with joint compound?

Lock enemy's y-axis when using Vector3.MoveTowards to follow the player

Specific Chinese carabiner QA?

Formatting a table to look nice

Mongostat display size / res

MongoDB working set size on capped collection larger than capped collection size?MongoDB Document size too largehigh background flush avg mongodbUnderstanding document size in MongoDBMongodb background indexing - no progressMongodb Huge Number of Open Connections and Write LocksMongoDB Storage size scalingSudden Mongodb high connections/queues, db stops respondingMongoDB replication throttled due to Mongo using all system memorybigchaindb set up and run cluster node error

0

I would like to have your opinion and of course an explanation on the following.

My configuration :

• mongodb version 3.4.4




• 1 replicaset with three identical servers( 4 cpu / 32 Go RAM under linux ubuntu v16)




• 1 primary and two secondaries.



• No delay in replication every thing is up ta date.


• The engine is WiredTigger.

During insertion or update time I have the following:

• Primary : vsize : 3.73 G/ res : 3.02 G


• 1st secondary : vsize : 3.28 G / res : 2.63 G


• 2nd secondary : vsize : 5.66 G / res : 5.02G

I am wondering why is there this difference between the vsize/res of the 2nd secondary and the 1st one?

I was guessing that I should see some kind of equality between them because they both support the same informations from the primary.

Any help or information will bee appreciated.

mongodb

share|improve this question

edited Jul 17 '17 at 8:47

McNets

16.1k42161

asked Jul 17 '17 at 8:31

YrkYrk

13

bumped to the homepage by Community♦ 4 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  There are several possible reasons for secondaries in the same replica set to have different memory usage. Are all three servers in the same data centre? Are you running any queries with secondary read preferences? Do all mongod processes have similar uptime? Have there been any elections? Can you include the full output of rs.status() (anonymize the host names but keep the other details)?
  
  – Stennie
  Jul 17 '17 at 11:18
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi Stennie and JJussi , first of all thanks for your answers, and my apologies for being long to answer. In your answers you point something very interesting for me, and I did not think about it. Yes I have read preference set on the secondary, and that may explain my question, I will do some tests regarding that. Thanks a lot for your help. Best regards
  
  – Yrk
  Oct 16 '17 at 15:58
  

  
  
  
  

add a comment | 

0

I would like to have your opinion and of course an explanation on the following.

My configuration :

• mongodb version 3.4.4




• 1 replicaset with three identical servers( 4 cpu / 32 Go RAM under linux ubuntu v16)




• 1 primary and two secondaries.



• No delay in replication every thing is up ta date.


• The engine is WiredTigger.

During insertion or update time I have the following:

• Primary : vsize : 3.73 G/ res : 3.02 G


• 1st secondary : vsize : 3.28 G / res : 2.63 G


• 2nd secondary : vsize : 5.66 G / res : 5.02G

I am wondering why is there this difference between the vsize/res of the 2nd secondary and the 1st one?

I was guessing that I should see some kind of equality between them because they both support the same informations from the primary.

Any help or information will bee appreciated.

mongodb

share|improve this question

edited Jul 17 '17 at 8:47

McNets

16.1k42161

asked Jul 17 '17 at 8:31

YrkYrk

13

bumped to the homepage by Community♦ 4 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  There are several possible reasons for secondaries in the same replica set to have different memory usage. Are all three servers in the same data centre? Are you running any queries with secondary read preferences? Do all mongod processes have similar uptime? Have there been any elections? Can you include the full output of rs.status() (anonymize the host names but keep the other details)?
  
  – Stennie
  Jul 17 '17 at 11:18
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi Stennie and JJussi , first of all thanks for your answers, and my apologies for being long to answer. In your answers you point something very interesting for me, and I did not think about it. Yes I have read preference set on the secondary, and that may explain my question, I will do some tests regarding that. Thanks a lot for your help. Best regards
  
  – Yrk
  Oct 16 '17 at 15:58
  

  
  
  
  

add a comment | 

I would like to have your opinion and of course an explanation on the following.

My configuration :

• mongodb version 3.4.4




• 1 replicaset with three identical servers( 4 cpu / 32 Go RAM under linux ubuntu v16)




• 1 primary and two secondaries.



• No delay in replication every thing is up ta date.


• The engine is WiredTigger.

During insertion or update time I have the following:

• Primary : vsize : 3.73 G/ res : 3.02 G


• 1st secondary : vsize : 3.28 G / res : 2.63 G


• 2nd secondary : vsize : 5.66 G / res : 5.02G

I am wondering why is there this difference between the vsize/res of the 2nd secondary and the 1st one?

I was guessing that I should see some kind of equality between them because they both support the same informations from the primary.

Any help or information will bee appreciated.

mongodb

share|improve this question

edited Jul 17 '17 at 8:47

McNets

16.1k42161

asked Jul 17 '17 at 8:31

YrkYrk

13

share|improve this question

edited Jul 17 '17 at 8:47

McNets

16.1k42161

asked Jul 17 '17 at 8:31

YrkYrk

13

share|improve this question

edited Jul 17 '17 at 8:47

McNets

16.1k42161

asked Jul 17 '17 at 8:31

YrkYrk

13

edited Jul 17 '17 at 8:47

McNets

16.1k42161

edited Jul 17 '17 at 8:47

McNets

16.1k42161

asked Jul 17 '17 at 8:31

YrkYrk

13

asked Jul 17 '17 at 8:31

YrkYrk

13

1 Answer
1

active

oldest

votes

0

Has those servers been on that order during their uptime? It looks like that current 2nd secondary has been primary earlier during time what this replica set has been up. Because mongod memory consumption grow (until it reach it's maximum) when it reads data/indexes from disk. (and of course when you insert documents)

At start, mongod process eats only little memory, but during time when it serve clients, it will consume all available free memory, eventually! Because secodary nodes don't (normally) server/receive queries, their memory consumption grows much slower than primary.

share|improve this answer

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f179984%2fmongostat-display-size-res%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Has those servers been on that order during their uptime? It looks like that current 2nd secondary has been primary earlier during time what this replica set has been up. Because mongod memory consumption grow (until it reach it's maximum) when it reads data/indexes from disk. (and of course when you insert documents)

At start, mongod process eats only little memory, but during time when it serve clients, it will consume all available free memory, eventually! Because secodary nodes don't (normally) server/receive queries, their memory consumption grows much slower than primary.

share|improve this answer

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314

add a comment | 

0

Has those servers been on that order during their uptime? It looks like that current 2nd secondary has been primary earlier during time what this replica set has been up. Because mongod memory consumption grow (until it reach it's maximum) when it reads data/indexes from disk. (and of course when you insert documents)

At start, mongod process eats only little memory, but during time when it serve clients, it will consume all available free memory, eventually! Because secodary nodes don't (normally) server/receive queries, their memory consumption grows much slower than primary.

share|improve this answer

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314

add a comment | 

Has those servers been on that order during their uptime? It looks like that current 2nd secondary has been primary earlier during time what this replica set has been up. Because mongod memory consumption grow (until it reach it's maximum) when it reads data/indexes from disk. (and of course when you insert documents)

At start, mongod process eats only little memory, but during time when it serve clients, it will consume all available free memory, eventually! Because secodary nodes don't (normally) server/receive queries, their memory consumption grows much slower than primary.

share|improve this answer

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314

share|improve this answer

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314

answered Jul 20 '17 at 12:54

JJussiJJussi

3,1391314