Cron Jobs (edit)
- Load Balancing
- Docker container
- Prevent duplicate cron jobs running
Fully-featured .NET library for working with Cron expressions. Built with time zones in mind and intuitively handles daylight saving time transitions
Cronos is a .NET library for parsing Cron expressions and calculating next occurrences. It was designed with time zones in mind, and intuitively handles Daylight saving time (also known as Summer time) transitions as in *nix Cron.
Please note this library doesn't include any task/job scheduler, it only works with Cron expressions.
- Supports standard Cron format with optional seconds.
- Supports non-standard characters like L, W, # and their combinations.
- Supports reversed ranges, like 23-01 (equivalent to 23,00,01) or DEC-FEB (equivalent to DEC,JAN,FEB).
- Supports time zones, and performs all the date/time conversions for you.
- Does not skip occurrences, when the clock jumps forward to Daylight saving time (known as Summer time).
- Does not skip interval-based occurrences, when the clock jumps backward from Summer time.
- Does not retry non-interval based occurrences, when the clock jumps backward from Summer time.
- Contains 1000+ unit tests to ensure everything is working correctly.
Common Load Balancer Issues
This topic discusses several issues and how to resolve them.
- Load balancing on TCP port (for example, port 443) does not work.
- A member of the load balancing pool is not utilized.
- Verify the server is in the pool, enabled, and monitor health status.
- Edge traffic is not load balanced.
- Verify the pool and persistence configuration. If you have persistence configured and you are using a small number of clients, you may not see even distribution of connections to backend pool members.
- Layer 7 load balancing engine is stopped.
- Health monitor engine is stopped.
- Enable load balancer service. Refer to the NSX Administration Guide.
- Pool member monitor status is WARNING/CRITICAL.
- Verify the application server is reachable from the load balancer.
- Verify the application server firewall or DFW is allowing traffic.
- Ensure the application server is able to respond to the specified health probe.
- Pool member has the INACTIVE status.
- Verify the pool member is enabled in the pool configuration.
- Layer 7 sticky table is not synchronized with the standby Edge.
- Ensure that HA is configured.
- Client connections, but cannot complete an application transaction.
- Verify that the proper persistence is configured in the application profile.
- If the application works with only one server in the pool (and not two), it is most likely a persistence problem.