Starwind iSCSI service slow to start

[gymmbo]

I am in the process of an emergency reboot of my SAN. The SAN is up but the Starwind iSCSI service is very slow to start. It is almost like it is hung on "starting". I am talking in the 15 - 20 minute range and I have production machines that need to get back up ASAP. I have just upgraded to 5.7 so I am waiting for the setup to complete.

[gymmbo]

I upgraded to the latest version (.1733) and the service restart is killing me. Over 30 minutes now and I know my synchs are going to be several hours for all to be completed. I am not sure what is going on in the background but something should be looked at. Maybe the service is trying to reconnect the targets or connect w/ the other HA device. Either way, this should be addressed.

[anton (staff)]

Is there anything reported inside StarWind log? Do you happen to know how many targets and of what size are you synchronizing between each other?

[gymmbo]

I am looking at about 30 targets. I didn't find anything in the logs but again, I am not sure what I am looking for. Synch size varies from 1024 MB Quorum files to a large 1.8TB data file. Most are in the 30GB - 60GB range

[Anatoly (staff)]

This is caused by the time that is needed to MS iSCSI initiator to establish all the sessions. So you have at least 60 sessions, but since you are using 5.7 I think the nember is 150 (4 sync session and one Heartbeat).

In future releases we will change this (we`ll use our own initiator) and starwind service will stop/start quicker.