Ticket 1980 - slurmdbd configuration -- DbdBackupAddr field missing?
Summary: slurmdbd configuration -- DbdBackupAddr field missing?
Status: RESOLVED INVALID
Alias: None
Product: Slurm
Classification: Unclassified
Component: slurmdbd (show other tickets)
Version: 15.08.0
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Brian Christiansen
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2015-09-27 18:39 MDT by Doug Jacobsen
Modified: 2015-09-28 06:51 MDT (History)
2 users (show)

See Also:
Site: NERSC
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Doug Jacobsen 2015-09-27 18:39:53 MDT 
Hello,

I'm continuing to setup the cori slurm instances.  Normal NERSC hostname/networking protocol is to have a hostname, e.g., cori06, accessible via gethostname(), and then separate DNS entries/hostnames for each network interface, e.g., cori06-ib and cori06-244 identifying particular network interfaces.

Anyway, this means to get routes between the various slurm daemons correct, I am making heavy use of the Addr configuration options (ControlAddr, HostAddr, etc)

In this context, I noticed that DbdBackupHost exists, but not DbdBackupAddr?  For the case of routing traffic from the inside of cori to the outside (where slurmdbd runs), it will be necessary to have DbdBackupAddr unless I do something ugly to the configuration files.  However, for other instances not specifying this will cause slurm traffic to cross over interfaces I'd prefer it not to.

Thus, my question: it seems that DbdBackupAddr is missing, or am I missing something?

Thanks,
Doug
Comment 1 Brian Christiansen 2015-09-28 04:07:38 MDT 
You'll want to take a look at Bug 1921. From Comment 6:

"A DbdBackupHostAddr is not needed. DbdBackupHost is only used to verify the host that the backup is running on. The backup uses DbdAddr to communicate with the primary dbd. The controller, sacct and sacctmgr use AccountingStorageHost and AccountingStorageBackupHost in the slurm.conf to know where the dbds are running."

You may want the the DbdAddr fix in (Comment 3):
https://github.com/SchedMD/slurm/commit/5beb84db5af9ac73657d555ca672d711dc4eda60

Does this help?

Thanks,
Brian
Comment 2 Doug Jacobsen 2015-09-28 06:51:21 MDT 
Yes, this does help.  I guess I misunderstood what the DbdBackupHost was for. Thank you.