NotifyBC
Home
Docs
Help
GitHub
Home
Docs
Help
GitHub
  • Getting Started

    • Welcome
    • Overview
    • Quick Start
    • Installation
    • Web Console
    • What's New
  • Configuration

    • Configuration Overview
    • Database
    • Admin IP List
    • Reverse Proxy IP Lists
    • HTTP Host
    • Internal HTTP Host
    • Email
    • SMS
    • Subscription
    • Notification
    • Node Roles
    • Cron Jobs
    • RSA Keys
    • Worker Process Count
    • Middleware
    • OIDC
    • TLS Certificates
    • Queue
    • Logging
  • API

    • API Overview
    • Subscription
    • Notification
    • Configuration
    • Administrator
    • Bounce
  • Miscellaneous

    • Health Check
    • Disaster Recovery
    • Memory Dump
    • Benchmarks
    • Bulk Import
    • Developer Notes
    • Upgrade Guide
  • Meta

    • Code of Conduct
    • Security Reporting
    • Acknowledgments

Node Roles

In a multi-node deployment, tasks that don't support concurrency have to be run by one node. That node is designated as primary. To alleviate primary node's burden, tasks that support concurrency are not assigned to the primary node.

The distinction is made using environment variable NOTIFYBC_NODE_ROLE. For primary node, don't set this environment variable. For secondary nodes, set it to secondary.

multi-CPU node

If the primary node has multiple CPUs, then only one worker has primary role. The rest have secondary role. If a secondary node has multiple CPUs, all workers have secondary role. See Worker Process Count for multi-CPU nodes.

Prev
Notification
Next
Cron Jobs