Hi
Thanks for the response. the above mentioned text is a part of the
description given by RFC. Please find below the other part.
So the RFC states the below mentioned text for fail over. And apart from
the method of listening to the heart beat messages it also mentions that
fail over mechanism is possible but not explained fully in this document.
The RFC says:
Server failover and recovery are topics of continuing research, and
adequate resolution of issues such
as split brain and primary server selection is dependent on the
specific implementation requirements and deployment needs. The
failover mechanisms discussed in this document focus on the
interaction between iSNS clients and iSNS servers. Specifically,
what is covered in this document includes the following:
- iSNS client behavior and the iSNS protocol interaction between the
client and multiple iSNS servers, some of which are backup
servers.
- Required failover behaviors of the collection of iSNS servers that
includes active and backup servers.
*However*, note that this document does not specify the complete
functional failover requirements of each iSNS server. In particular,
it does not specify the complete set of protocol interactions among
the iSNS servers that are required to achieve stable failover
operation in an interoperable manner.
I know it says that the above mentioned details are implementation
specific but I would like to know these implementations as I myself
have some ideas regarding the same and need to know the current
implementation methods.
Thanks
Lokesh
On Sat, Jul 4, 2015 at 4:00 AM, The Lee-Man <[email protected]> wrote:
> On Thursday, July 2, 2015 at 2:17:12 AM UTC-7, [email protected] wrote:
>>
>> I would like to know about the fail over mechanisms used by iSNS for
>> ISCSI implementation. The RFC states that "Note that it is possible to
>> create multiple physical iSNS servers to form a single logical iSNS server
>> cluster, and thus to distribute iSNS transaction processing among multiple
>> physical servers. However, a more detailed discussion of the interactions
>> between physical servers within a logical iSNS server cluster is beyond the
>> scope of this document."
>>
>> I tried searching but most of the findings are related to Windows and
>> that too does not explain what are the fail over techniques used or the
>> implementation details.
>>
>> Any links or documents about the same would be very useful. Thanks
>>
>
> It does not sound like the method mentioned by the RFC was meant for
> fail-over, but instead was meant to distribute the work.
>
> And I can't imagine an iSNS workload so large a single system could not
> handle it. But perhaps I think too small.
>
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
