Skip to content

Commit a6bcb14

Browse files
committed
Tweak
1 parent 8fff522 commit a6bcb14

File tree

1 file changed

+4
-2
lines changed
  • articles/azure-functions/errors-diagnostics/diagnostic-events

1 file changed

+4
-2
lines changed

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0004.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 01/28/2023
1010

1111
# AZFD0004: Host ID collision
1212

13-
This event occurs when you have multiple function apps or slots with the same generated host ID sharing the same storage account.
13+
This event occurs when you have multiple function apps or slots assigned the same host ID sharing the same storage account.
1414

1515
| | Value |
1616
|-|-|
@@ -22,14 +22,16 @@ This event occurs when you have multiple function apps or slots with the same ge
2222

2323
A host ID collision can occur when you've more than one function app or slot using the same host ID while sharing a storage account. This condition usually occurs due to truncation of similar function app names when the host ID value is generated. For example, if you have multiple apps or slots with names longer than 32 characters and the first 32 characters are shared, both generated host ID values may be the same due to truncation.
2424

25+
You can also have the same collision when you explicitly set the same host ID value on multiple function apps using the same storage account.
26+
2527
When multiple apps have the same host ID, the resulting collision can result incorrect behaviors. For example, some triggers, like timer and Blob Storage, store tracking info by host ID. This collision can result in incorrect behavior when the host can't differentiate between apps by host ID. When such a collision is detected, an error (hard failure) is logged and the host is shut down.
2628

2729
For more information, see [host ID considerations](../../storage-considerations.md#host-id-considerations).
2830

2931
## Options for addressing collisions:
3032

3133
- Connect each function app or slot in the collision to a different storage account by changing the [AzureWebJobsStorage](../../functions-app-settings.md#azurewebjobsstorage) application setting or slot setting.
32-
- Rename your function apps to a name that is fewer than 32 characters in length. When names have fewer than 32 characters, unique host IDs can be generated for each app, which removes the collision.
34+
- Rename your function apps to a name that has fewer than 32 characters. When names have fewer than 32 characters, unique host IDs can be generated for each app, which removes the collision.
3335
- Set explicit host ID values for your function apps or slots so they no longer conflict. For more information, see [host ID considerations](../../storage-considerations.md#host-id-considerations).
3436

3537
## When to suppress the event

0 commit comments

Comments
 (0)