[SERVER-11039] During Upgrade of Mongos from 2.2 to 2.4, process does not come out. Created: 04/Oct/13  Updated: 10/Dec/14  Resolved: 24/Mar/14

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Rajat Bhasin Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Devlopement server


Attachments: Text File MONGOS_UPGRADE_LOG.txt    
Issue Links:
Duplicate
duplicates SERVER-13294 mongos --upgrade should exit after up... Closed
Participants:

 Description   

Hi Team,
When we upgrade mongos from 2.2 to 2.4. The process running with --upgrade does not completes, it keep runnign for ever and we have kill or teminate it and then start it again without --upgrade option.

While in case of upgrade of mongod instance --upgrade process comes out of its own and once it comes out we start it again.

Want to check if this is normal behaviour of Mongos or our mongos process is getting hanged. I have attached the mongos upgrade logs file.



 Comments   
Comment by Rajat Bhasin [ 10/Oct/13 ]

Thanks Randolph,
You can close the case now. Thanks for all your help and explanation.

Regards
Rajat Bhasin
UDB Database Engineer
Office: 732 652 7252 | Cell: 732 322 5763 | Email: rbhasin@metlife.com

Comment by Randolph Tan [ 10/Oct/13 ]

Yes. The log entry "upgrade of config server to v4 successful" means that the upgrade has completed.

Comment by Rajat Bhasin [ 08/Oct/13 ]

Hi Randolph,
If mongos process keep running with --upgrade option, it will always be a confusion and does not seems to be good option to keep it running for always(months or year till new upgrade not done).

Can your team confirm us some checks in mongos upgrade log file which shows mongos upgrade is completed and now we can kill that mongos process and start its normal process (i.e. without --upgrade) ?
And will this alternative approach be safe approach(considering we have a big production Mongo Env)?

Regards
Rajat Bhasin
UDB Database Engineer
Office: 732 652 7252 | Cell: 732 322 5763 | Email: rbhasin@metlife.com

Comment by Randolph Tan [ 08/Oct/13 ]

Hi,

The mongos process does not terminate after it finishes the upgrade. So that means you can start using it right away without having to start the mongos again. On the other hand, I know that the inconsistency in the behavior is confusing.

Thanks!

Comment by Rajat Bhasin [ 08/Oct/13 ]

yes I have read the document provided. I did following:
1. I have first stoped the only mongos instance running on standalone box.
2. uninstall and installed the new binaries
3. Started the mongos process again with --upgrade option:
mongos --port 27017 --logpath /udb/udbll002/data/m_data/mongos/mongos.log --logappend --configdb lxrsvnsqlt01:27018 --keyFile /udb/udbll002/data/m_data/key_file/keyfile.conf --upgrade

4. Above command keep running for indefinate time and does not comes out.

Comment by Rajat Bhasin [ 08/Oct/13 ]

I have uploaded my MONGOS LOG fiel generated during upgrade.

Comment by Daniel Pasette (Inactive) [ 07/Oct/13 ]

Can you post the log files for your mongos when you attempted the upgrade? Have you read the upgrade instructions for a sharded cluster in the documentation before attempting the upgrade?
http://docs.mongodb.org/manual/release-notes/2.4-upgrade/#upgrade-a-sharded-cluster-from-mongodb-2-2-to-mongodb-2-4

Generated at Thu Feb 08 03:24:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.