- General information
- Data readiness
- Calibration
- Databases
- Frequently Asked Questions
- How-To: user section
- How-To: admin section
- How-To: subsystem coordinator
- Online Databases
- Offline Databases
- FileCatalog Databases
- Software Infrastructure Databases
- Maintenance
- DB & Docker
- Development
- Advanced DB Infrastructure : Hecate project
- Archive: unsorted documents
- Bridging EPICS and High-Level Services at STAR
- C++ DB-API
- Database types
- Distributed Control System - Conditions
- Enhanced Logger Infrastructure
- IRMIS
- Load Balancer
- MIRA: Fake IOC Development
- Online API
- PXL database design
- STAR DB API v2
- STAR Online Services Aggregator
- STAR Online Status Viewer
- STAR database inrastructure improvements proposal
- Solid State Drives (SSD) vs. Serial Attached SCSI (SAS) vs. Dynamic Random Access Memory (DRAM)
- Test
- Quality Assurance
- Grid and Cloud
- Infrastructure
- Machine Learning
- Offline Software
- Production
- S&C internal group meetings
- Test tree
Load Balancer Connection
Updated on Tue, 2009-05-05 13:25 by testadmin. Originally created by deph on 2007-09-28 10:52.
Under:
The load balancer makes its decision as to which node to connect to, based on the number of active connections on each node.
It will choose the node with the least number of connections.
In order to do this it must make a connection to each node in a group.
The load balancer will need an account on the database server with a password associated with it.
The account is:
user = loadbalancer
please contact an administrator for the password associated with the account.
631-344-2499
The load this operation creates is minimal.
so
something like
grant process on *.* to 'loadbalancer'@'%.bnl.gov' identified by 'CALL 631-344-2499';
of coarse the location should be local.
»
- Printer-friendly version
- Login or register to post comments