Support Center

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Index Lock Timeout

Garry Bargsley Sep 24, 2015 09:44AM CDT

In our current routine for index maintenance we have the ability to put a timeout on an index rebuild. So if the lock is set to X amount of time and the index rebuild is locked for X amount of time it will bypass that index and move to the next. Does minion index have the ability to gracefully keep working if it hits an index that it gets a lock on. Our hope is to not fail all rebuild/reindex processes over one index that cannot be processed.

Up 0 rated Down
Sean McCown Sep 24, 2015 09:54AM CDT MinionWare Agent

Hey Garry, it’s been a while. Yeah we’ve got 2 mechanisms for that. 1st, you can take advantage of the SQL 2014 features. Our Settings tables allow you to configure this at the DB or at the table level. 2nd, in 1.2 (which will release very soon) you can take advantage of the new StmtPrefix. This allows you to setup a statement prefix that runs in the same context as the reindex stmt. So you can do things like set deadlock priority and lockTimeout. When the stmt returns the routine should pick up the error msg and put it in the log table… NOT a txt file.
1.2 is in its final stages now and if you need the Prefix feature right away just let me know and i’ll be happy to shoot you the code early.

Up 0 rated Down
Sean McCown Sep 24, 2015 09:56AM CDT MinionWare Agent

I’m going to close this, but feel free to re-open if you need.

Up 0 rated Down
Garry Bargsley Sep 24, 2015 10:03AM CDT
Thanks for your quick response. I will continue with my testing on 1.1 with the knowledge that we will have this in the next released version.
Up 0 rated Down
Sean McCown Nov 06, 2015 11:35AM CST MinionWare Agent

Hey Garry, just wanted to let you know we released v.1.2 a couple wks ago.

Post Your Public Answer

Your name (required)
Your email address (required)
Answer (required)
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found