On 03/08/2016 12:57 PM, Benjamin ESTRABAUD wrote: > Hi, > > I've been facing with a small issue lately when working with 128 iSCSI > targets on a single system with multiple iscsi initiators connecting to > it (3, 4 inits). If I remove the iSCSI targets or even just the ACLs > from the system even temporarily I get flooded by thousands upon > thousands of connection failures from the hosts trying to login to the > system with messages like: > > [ 923.560908] iSCSI Initiator Node: iqn.1994-05.com.redhat:c87d91366225 > is not authorized to access iSCSI target portal group: 1. > [ 923.561124] iSCSI Login negotiation failed. > > These are fine in small number but when all of the hosts are combined to > so many targets the system gets overwhelmed, the kernel logger gets > flooded and the network portal thread's CPU usage ramps up to close to > 100%. > > Is there a way to limit those, say for instance add a timer between the > login attempt processing that gradually increases with each login failure? > > I can control the hosts but it's not always evident as a solution > (sometimes the initiators have been improperly configured and I get back > in the same situation). > Is this with Linux hosts only? We can implement something on the initiator side like other OSes have where for these types of errors it will stop retrying the relogin then the user has to relogin manually later. We used to do that by default, but hit issues. We can just make the behavior a config option. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
