tsai
/
abp
mirror of https://github.com/abpframework/abp.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Improve same-storage section in background jobs&workers docs

pull/22314/head
Engincan VESKE 2 years ago
committed by GitHub
parent
b490e202fa
commit
dd8cb9a053
No known key found for this signature in database GPG Key ID: B5690EEEBB952194
2 changed files with 12 additions and 12 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 12
      docs/en/framework/infrastructure/background-jobs/index.md
  2. 12
      docs/en/framework/infrastructure/background-workers/index.md

12
docs/en/framework/infrastructure/background-jobs/index.md
View File

@ -236,13 +236,13 @@ Background Jobs module implements `IBackgroundJobStore` using various data acces
> Background Jobs module is already installed to the startup templates by default and it works based on your ORM/data access choice.
### Multiple Applications Use Same Storage
### Using the Same Storage for Background Jobs & Workers
If you have multiple applications using one storage as background jobs and workers(`Default, Hangfire, RabbitMQ, and Quartz`), You should set the provider options to use the application name to isolate.
If multiple applications share the same storage for background jobs and workers (`Default, Hangfire, RabbitMQ, and Quartz`), you should configure the provider options to use the application name for isolation.
#### Default Background Job/Workers
Set `ApplicationName` of `AbpBackgroundJobWorkerOptions` to your application name.
Set `ApplicationName` property in `AbpBackgroundJobWorkerOptions` to your application's name:
````csharp
public override void PreConfigureServices(ServiceConfigurationContext context)
@ -256,7 +256,7 @@ public override void PreConfigureServices(ServiceConfigurationContext context)
#### Hangfire Background Job/Workers
Set `DefaultQueuePrefix` of `AbpHangfireOptions` to your application name.
Set `DefaultQueuePrefix` property in `AbpHangfireOptions` to your application's name:
````csharp
public override void ConfigureServices(ServiceConfigurationContext context)
@ -270,7 +270,7 @@ public override void ConfigureServices(ServiceConfigurationContext context)
#### Quartz Background Job/Workers
Set `quartz.scheduler.instanceName` to your application name.
Set the `quartz.scheduler.instanceName` property to your application's name:
````csharp
public override void PreConfigureServices(ServiceConfigurationContext context)
@ -296,7 +296,7 @@ public override void PreConfigureServices(ServiceConfigurationContext context)
#### RabbitMQ Background Job
Set `DefaultQueueNamePrefix` and `DefaultDelayedQueueNamePrefix` of `AbpRabbitMqBackgroundJobOptions` to your application name.
Set `DefaultQueueNamePrefix` and `DefaultDelayedQueueNamePrefix` properties in `AbpRabbitMqBackgroundJobOptions` to your application's name:
````csharp
public override void PreConfigureServices(ServiceConfigurationContext context)

12
docs/en/framework/infrastructure/background-workers/index.md
View File

@ -133,13 +133,13 @@ If that's a problem for your workers, you have the following options:
* Stop the background workers (set `AbpBackgroundWorkerOptions.IsEnabled` to `false`) in all application instances and create a dedicated application (maybe a console application running in its own container or a Windows Service running in the background) to execute all the background tasks. This can be a good option if your background workers consume high system resources (CPU, RAM or Disk), so you can deploy that background application to a dedicated server and your background tasks don't affect your application's performance.
### Multiple Applications Use Same Storage
### Using the Same Storage for Background Jobs & Workers
If you have multiple applications using one storage as background jobs and workers(`Default, Hangfire, RabbitMQ, and Quartz`), You should set the provider options to use the application name to isolate.
If multiple applications share the same storage for background jobs and workers (`Default, Hangfire, RabbitMQ, and Quartz`), you should configure the provider options to use the application name for isolation.
#### Default Background Job/Workers
Set `ApplicationName` of `AbpBackgroundJobWorkerOptions` to your application name.
Set `ApplicationName` property in `AbpBackgroundJobWorkerOptions` to your application's name:
````csharp
public override void PreConfigureServices(ServiceConfigurationContext context)
@ -153,7 +153,7 @@ public override void PreConfigureServices(ServiceConfigurationContext context)
#### Hangfire Background Job/Workers
Set `DefaultQueuePrefix` of `AbpHangfireOptions` to your application name.
Set `DefaultQueuePrefix` property in `AbpHangfireOptions` to your application's name:
````csharp
public override void ConfigureServices(ServiceConfigurationContext context)
@ -167,7 +167,7 @@ public override void ConfigureServices(ServiceConfigurationContext context)
#### Quartz Background Job/Workers
Set `quartz.scheduler.instanceName` to your application name.
Set `quartz.scheduler.instanceName` property to your application's name:
````csharp
public override void PreConfigureServices(ServiceConfigurationContext context)
@ -193,7 +193,7 @@ public override void PreConfigureServices(ServiceConfigurationContext context)
#### RabbitMQ Background Job
Set `DefaultQueueNamePrefix` and `DefaultDelayedQueueNamePrefix` of `AbpRabbitMqBackgroundJobOptions` to your application name.
Set `DefaultQueueNamePrefix` and `DefaultDelayedQueueNamePrefix` properties in `AbpRabbitMqBackgroundJobOptions` to your application's name:
````csharp
public override void PreConfigureServices(ServiceConfigurationContext context)

Write Preview
Loading…
Cancel
Save