Index fragmentation for SQL Server implementations

Not sure if this is a bug or a configuration issue, but we’re getting quite a few Hangfire.Storage.DistributedLockTimeoutException errors. I am in the process of working on some different configurations to see if it will resolve the issue.

One thing I am noticing, is the Hangfire table indexes fragment fast. I will rebuild the indexes and within a few hours they are back up to 99%. Specifically the following indexes:

  • PK_Hangfire_Hash (on Hash table)
  • PK_Hangfire_Set (on Set table)
  • IX_HangFire_Set_Score (on Set table)
  • CX_HangFire_Counter (on Counter table)

Is this normal with most implementations?

I’d like to rule it out in my troubleshooting before I get too deep into changing configuration options or the code written that’s interfacing with HangFire.

Thanks!