Is it possible to identify the work left for the current pass of write daemon?

Question

Question

Mack Altman · May 2, 2018

Currently, we are receiving an alert that states, "Write Daemon still on pass 31". It's been that way for a few hours.

I was wondering if it is possible to identify what the WD has left to work on so that we can see how we can reduce this and possibly identify if there are issues with the way something is written.

Thanks in advance for any insight.

Discussion (4)0

Log in or sign up to continue

Andrew Krammen · May 2, 2018

Mack, there are multiple possibilities for why the write daemon is still on pass 31. I recommend contacting InterSystems Support at 617-621-0700 or Support@InterSystems.com for assistance resolving this, especially if it is impacting users in any way.

2 0

score 1 · Answer 1 · 2018-05-02T14:14:12-04:00

Dmitry Maslennikov · May 2, 2018

You can run mgstat, for some time, and look what happens. It has a lot of metrics, some about WD state

1 0

score 0 · Answer 2 · 2018-05-02T15:09:55-04:00

I know that mgstat has the queue size, blocks updated, and phase. What I'm looking for is more what is left in the queue. As of now, the WD is still on the same phase (1h and 6m later).

score 0 · Answer 3 · 2018-05-03T10:07:04-04:00

I agree with Andrew that this is complex enough that you'll get better answers by talking to the WRC. In addition, I'd also recommend taking a Buttons or CacheHung report quickly, so that you have the cstat data to look at later if the problem clears up. If it clears up before you collect any data, there likely won't be much anyone can say.