LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 06-13-2018, 09:36 PM   #1
dcapone2004
LQ Newbie
 
Registered: Jun 2018
Posts: 1

Rep: Reputation: Disabled
Pacemaker Cluster iSCSI Target does not gracefully Stop


I have configured an iSCSI HA cluster using DRBD, Pacemaker, and Corosync. I am using the tgt implementation and am using CentOS 7. I attempted to use the LIO-T implementation, however, the write performance using LIO was 3 times lower than TGT for some reason. After some googling on that issue, I learned that LIO has apparently not yet been fully performance tuned and there are some issues if certain settings do not match perfectly between initiator and target.

Anyway, onto my issue...

If I attempt to "gracefully" move the iSCSI resources and/or put one of the nodes into Standby mode to gracefully move the nodes that way, it ends up being a nightmare with a lot of pcs resource cleanups needing to be issues to eventually get the Iscsitarget resources to stop.

After running pcs resource debug-stop (and also combing the corosync log file), the issue appears that tgtadm which I understand pcs calls on the backend to shutdown the target, does not release the target because of existing iSCSI initiator connections that are established to the target. Exact output is:

> stderr: tgtadm: this target is still active
> stderr: WARNING: Failed to remove target <target iqn>, retrying.
> stderr: tgtadm: this target is still active
> stderr: WARNING: Failed to remove target <target iqn>, retrying.
> stderr: tgtadm: this target is still active
> stderr: WARNING: Failed to remove target <target iqn>, retrying.
> stderr: tgtadm: this target is still active
> stderr: WARNING: Failed to remove target <target iqn>, retrying.
> stderr: tgtadm: this target is still active

The stop fails, the resource goes into a failed state and then I am forced to run cleanup to eventually force the resource to stop to move over. This obviously is far from ideal and takes away significantly the HA of the solution as the process takes long enough to cause my initiator connections to drop and need to be manually reconnected.

Is there something in my configuration that I am missing to force tgtadm to immediately close any connections? How should this situation be handled?

If it matters, the initiators connecting are all Microsoft Windows Server 2016 iSCSI initiators.

Any assistance in resolving this would be greatly appreciated.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] pacemaker - iscsi: problems with a multihomed target eantoranz Linux - Server 4 01-04-2013 09:14 AM
[SOLVED] pacemaker - iscsi: how to set up iscsi targets/logical units? eantoranz Linux - Server 9 01-02-2013 08:38 AM
Building some sort of cluster: slurm, pacemaker, cluster-glue or .... kaz2100 Linux - Software 2 07-21-2011 12:04 AM
changes on other iscsi nodes attached to an ext3 iscsi target not being seen sldahlin Linux - Server 1 06-07-2008 02:02 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 09:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration