Update and standardize unordered lists to be - (#37854)
This commit is contained in:
@@ -20,8 +20,8 @@ shortTitle: HA for GitHub Actions
|
||||
|
||||
We strongly recommend that you configure your {% data variables.product.prodname_actions %} external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation:
|
||||
|
||||
* [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy)
|
||||
* [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html)
|
||||
- [Azure Storage redundancy documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy)
|
||||
- [Amazon S3 replication documentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html)
|
||||
|
||||
## High availability replicas
|
||||
|
||||
|
||||
@@ -60,8 +60,8 @@ If you deploy {% data variables.product.prodname_ghe_server %} in your environme
|
||||
|
||||
You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.location.product_location %}. Each self-hosted runner will require one of the following procedures:
|
||||
|
||||
* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application.
|
||||
* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/removing-self-hosted-runners)" and "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)."
|
||||
- In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application.
|
||||
- Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/removing-self-hosted-runners)" and "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners)."
|
||||
|
||||
## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits
|
||||
|
||||
@@ -81,12 +81,12 @@ If the overall "System Health" CPU and memory usage is OK, scroll down the monit
|
||||
|
||||
Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for:
|
||||
|
||||
* `mps_frontend`
|
||||
* `mps_backend`
|
||||
* `token_frontend`
|
||||
* `token_backend`
|
||||
* `actions_frontend`
|
||||
* `actions_backend`
|
||||
- `mps_frontend`
|
||||
- `mps_backend`
|
||||
- `token_frontend`
|
||||
- `token_backend`
|
||||
- `actions_frontend`
|
||||
- `actions_backend`
|
||||
|
||||
If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit.
|
||||
|
||||
@@ -122,9 +122,9 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
|
||||
|
||||
In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above:
|
||||
|
||||
* `mps.hcl.ctmpl`
|
||||
* `token.hcl.ctmpl`
|
||||
* `actions.hcl.ctmpl`
|
||||
- `mps.hcl.ctmpl`
|
||||
- `token.hcl.ctmpl`
|
||||
- `actions.hcl.ctmpl`
|
||||
1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following:
|
||||
|
||||
```
|
||||
|
||||
@@ -40,12 +40,12 @@ For more information about storage configuration for {% data variables.product.p
|
||||
|
||||
To more accurately mirror your production environment, you can optionally copy files from your production storage location for {% data variables.product.prodname_actions %} to the staging storage location.
|
||||
|
||||
* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). For example:
|
||||
- For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). For example:
|
||||
|
||||
```shell
|
||||
azcopy copy 'https://<em>SOURCE-STORAGE-ACCOUNT-NAME</em>.blob.core.windows.net/<em>SAS-TOKEN</em>' 'https://<em>DESTINATION-STORAGE-ACCOUNT-NAME</em>.blob.core.windows.net/' --recursive
|
||||
```
|
||||
* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). For example:
|
||||
- For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). For example:
|
||||
|
||||
```shell
|
||||
aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET
|
||||
|
||||
Reference in New Issue
Block a user