Azure app service help

[Mr Mirchi]

Azure app service lo .net app running 3 instances tho

e roju autoscaling enable chesthe automatic select chesi…. Immediate ga 2 instaces add ayinavi .. and then 500 error random ga throwing users ki…..

auto-scaling thisesthe work avuthundhi antha normal ga

[BulletBaskar]

Possible Causes

• New Instance Readiness: When autoscaling kicks in (especially the "Automatic" mode), Azure adds instances rapidly. If your .NET app has a slow startup (e.g., due to database connections, caching, or compilation), requests might hit these "cold" instances before they're initialized, causing 500 errors. The load balancer routes traffic to them too soon.
• State Management: If your app relies on in-memory session state, local files, or non-distributed caches, scaling out can lead to inconsistencies or failures across instances.
• Resource Dependencies: Issues like maxed-out database connections, API rate limits, or external service timeouts can surface more prominently with more instances.
• Configuration Mismatch: Autoscaling rules might be too aggressive, or features like health checks aren't enabled to validate instance health.
• App-Specific Errors: Bugs in startup code or unhandled exceptions that only appear under load or on new instances.

Random 500s suggest it's not a total failure but intermittent, likely affecting only some requests routed to unprepared instances.

[Mr Mirchi]

7 minutes ago, BulletBaskar said:

Possible Causes

• New Instance Readiness: When autoscaling kicks in (especially the "Automatic" mode), Azure adds instances rapidly. If your .NET app has a slow startup (e.g., due to database connections, caching, or compilation), requests might hit these "cold" instances before they're initialized, causing 500 errors. The load balancer routes traffic to them too soon.
• State Management: If your app relies on in-memory session state, local files, or non-distributed caches, scaling out can lead to inconsistencies or failures across instances.
• Resource Dependencies: Issues like maxed-out database connections, API rate limits, or external service timeouts can surface more prominently with more instances.
• Configuration Mismatch: Autoscaling rules might be too aggressive, or features like health checks aren't enabled to validate instance health.
• App-Specific Errors: Bugs in startup code or unhandled exceptions that only appear under load or on new instances.

Random 500s suggest it's not a total failure but intermittent, likely affecting only some requests routed to unprepared instances

[Mr Mirchi]

11 minutes ago, BulletBaskar said:

Possible Causes

• New Instance Readiness: When autoscaling kicks in (especially the "Automatic" mode), Azure adds instances rapidly. If your .NET app has a slow startup (e.g., due to database connections, caching, or compilation), requests might hit these "cold" instances before they're initialized, causing 500 errors. The load balancer routes traffic to them too soon.
• State Management: If your app relies on in-memory session state, local files, or non-distributed caches, scaling out can lead to inconsistencies or failures across instances.
• Resource Dependencies: Issues like maxed-out database connections, API rate limits, or external service timeouts can surface more prominently with more instances.
• Configuration Mismatch: Autoscaling rules might be too aggressive, or features like health checks aren't enabled to validate instance health.
• App-Specific Errors: Bugs in startup code or unhandled exceptions that only appear under load or on new instances.

Random 500s suggest it's not a total failure but intermittent, likely affecting only some requests routed to unprepared instances.

In memory session, andhuke session affinity enable chesaam.

so, 3 instances tho manual sclanout tho no issues rojuuu… but auto scale cheyagaane fasak mani random 500s, session affinity enable chesinaa

 

[futureofandhra]

57 minutes ago, Mr Mirchi said:

Azure app service lo .net app running 3 instances tho

e roju autoscaling enable chesthe automatic select chesi…. Immediate ga 2 instaces add ayinavi .. and then 500 error random ga throwing users ki…..

auto-scaling thisesthe work avuthundhi antha normal ga

Which plan are you using 

[Mr Mirchi]

30 minutes ago, futureofandhra said:

Which plan are you using 

General purpose

[futureofandhra]

51 minutes ago, Mr Mirchi said:

General purpose

why not premiuum?