MarkMappingOffline hangs until timeout
See original GitHub issueIn version 1.3.3 MarkMappingOffline just hangs until timeout exception occurs. When downgrading to 1.3.2 it works as expected.
Here is a stacktrace dump:
at Microsoft.Azure.SqlDatabase.ElasticScale.ShardManagement.StoreOperation.Do()
at Microsoft.Azure.SqlDatabase.ElasticScale.ShardManagement.BaseShardMapper.Update[TMapping,TUpdate,TStatus](TMapping currentMapping, TUpdate update, Func4 constructMapping, Func
2 statusAsInt, Func2 intAsStatus, Guid lockOwnerId) at Microsoft.Azure.SqlDatabase.ElasticScale.ShardManagement.ListShardMapper
1.Update(PointMapping1 currentMapping, PointMappingUpdate update, Guid lockOwnerId) at Microsoft.Azure.SqlDatabase.ElasticScale.ShardManagement.BaseShardMapper.SetStatus[TMapping,TUpdate,TStatus](TMapping mapping, TStatus status, Func
2 getStatus, Func2 createUpdate, Func
4 runUpdate, Guid lockOwnerId)
at Microsoft.Azure.SqlDatabase.ElasticScale.ShardManagement.ListShardMapper1.MarkMappingOffline(PointMapping
1 mapping, Guid lockOwnerId)
at Microsoft.Azure.SqlDatabase.ElasticScale.ShardManagement.ListShardMap1.MarkMappingOffline(PointMapping
1 mapping)
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (3 by maintainers)
Top GitHub Comments
I came across this issue using v2.3.0. I was able to use this method by including the
MappingOptions
parameter.mapping = ShardMap.MarkMappingOffline(mapping, MappingOptions.None);
.Is there any update/advice for this issue? It tried to upgrade/downgrade client version. I have almost full elastic pool right now (97 dbs) and it would be nice to remove not needed ones since some tenants are no longer using the app. I’m getting timeouts every time i try to set mapping to offline