[SERVER-3748] Add init scripts for mongos and configsvr to packages Created: 01/Sep/11  Updated: 09/Aug/23  Resolved: 09/Aug/23

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

Type: Improvement Priority: Major - P3
Reporter: Richard Kreuter (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 17
Labels: build-later, move, packaging
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-31733 Explicit mongos default value for --t... Closed
Duplicate
is duplicated by SERVER-18750 Supply a mongoS startup script Closed
is duplicated by SERVER-43250 Include systemd mongos.service in pac... Closed
is duplicated by SERVER-3079 Init script for mongos Closed
Related
is related to SERVER-963 Separate os packages into multiple pa... Closed
is related to SERVER-31733 Explicit mongos default value for --t... Closed
is related to SERVER-20897 improved sysv init script Closed
Assigned Teams:
Server Development Platform
Participants:
Case:
Story Points: 13

 Description   

Although it's not possible to automatigically bring up mongos or configsvr processes without some manual configuration, we could provide init scripts and skeleton conf files for these in the packages.



 Comments   
Comment by Alex Neben [ 09/Aug/23 ]

Closing this issues as part of some SDP backlog cleanup. Please reopen if you feel this should be prioitized.

Comment by Ernie Hershey [ 08/Mar/17 ]

daniel.morrison - I'm not sure I understand your question. The best approach to do this currently is probably to copy the mongod init script (or your init system's equivalent) and modify it. I recommend posting to the mongodb-user google group to get additional details or ideas.

Comment by daniel.morrison#1 [ 08/Mar/17 ]

Hi @Ernie Hershey
what is the status of this... do you have any suggestions on what to do instead of an init script?

Comment by Ernestas Lukoševi?ius [ 11/Feb/15 ]

Uhhh, I hope this won't break existing functionality when upgrading?

Comment by Ernie Hershey [ 11/Feb/15 ]

It's still open because we'd like to make it even easier than that - with the approach of installing separate init scripts and config files that can be separately enabled without modifying /etc/default/mongod.

Comment by Ernestas Lukoševi?ius [ 26/Jan/15 ]

Why is this still open? For the OP - init script in 2.6 sources /etc/default/mongod, which allows setting DAEMON to /usr/bin/mongos in that file and thus /etc/init/mongod.conf is now for mongos, not mongod.

Comment by Ernie Hershey [ 27/Jun/14 ]

Here's our plan for how this will work:

  1. Single init script in the mongod repo that will work in three cases:
    1. mongod as normal node
    2. mongod as config server
    3. mongos
  2. Package installs symlinks or copies of single init script in three places
  3. Package installs config files for all three
  4. Package only enables mongod init script, leaves others off and they can be enabled with chkconfig
Comment by David Mytton [ 02/Sep/11 ]

This is a duplicate of SERVER-3079 (for Mongos).

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