Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

I/o fencing & number of instances per node

5 posts in Cluster Last posting was on 2009-06-01 17:00:45.0Z
Jose-Miguel Torres Posted on 2009-05-29 19:55:19.0Z
Sender: 5b89.4a203bd9.1804289383@sybase.com
From: Jose-Miguel Torres
Newsgroups: sybase.public.ase.cluster
Subject: I/o fencing & number of instances per node
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4a203da7.5bdf.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 29 May 2009 12:55:19 -0700
X-Trace: forums-1-dub 1243626919 10.22.241.41 (29 May 2009 12:55:19 -0700)
X-Original-Trace: 29 May 2009 12:55:19 -0700, 10.22.241.41
Lines: 18
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.cluster:144
Article PK: 48426

Hi,
Regarding to this note in the Installation Guide:

Chapter 3: Creating and Starting the Cluster
----------------------------------------------
Adding an instance to a cluster

"Do not add another instance to a node that already has one,
as the IO fencing feature requires that each instance be on
a separate node."

As I/O fencing is a requierement , does this effectively
limit to "1" the number of ASE instances that can be
configured by machine ..?
(One would expect to have 2+ ASE instances per node)

Thank you
JMT


J Posted on 2009-05-29 22:49:24.0Z
From: jtotally_bogus@sbcglobal.net (J)
Newsgroups: sybase.public.ase.cluster
Subject: Re: I/o fencing & number of instances per node
Reply-To: J@bogusemailAddress.com
Message-ID: <4a206455.27855524@forums.sybase.com>
References: <4a203da7.5bdf.1681692777@sybase.com>
X-Newsreader: Forte Free Agent 1.21/32.243
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 29 May 2009 15:49:24 -0700
X-Trace: forums-1-dub 1243637364 10.22.241.152 (29 May 2009 15:49:24 -0700)
X-Original-Trace: 29 May 2009 15:49:24 -0700, vip152.sybase.com
Lines: 39
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.cluster:145
Article PK: 48425

On 29 May 2009 12:55:19 -0700, Jose-Miguel Torres wrote:

Jose-Miguel,

A node refers to the hardware host. An instance refers to a running
ASE image on that node.

What the document is saying that if you were run multiple instances on
the same node then they are both fenced when one of them fails.

I/O Fencing is not a strict requirement for test configurations but
without it in test or production one could get data corruption.

I don't know why you would expect to have 2+ ASE instances per node??

Note: each of the ASE instances could be running on many engines just
like SMP ASE.

Jay

>Hi,
> Regarding to this note in the Installation Guide:
>
>Chapter 3: Creating and Starting the Cluster
>----------------------------------------------
>Adding an instance to a cluster
>
>"Do not add another instance to a node that already has one,
>as the IO fencing feature requires that each instance be on
>a separate node."
>
>As I/O fencing is a requierement , does this effectively
>limit to "1" the number of ASE instances that can be
>configured by machine ..?
>(One would expect to have 2+ ASE instances per node)
>
>Thank you
>JMT


Jose-Miguel Torres Posted on 2009-06-01 14:28:34.0Z
Sender: 658b.4a23e341.1804289383@sybase.com
From: Jose-Miguel Torres
Newsgroups: sybase.public.ase.cluster
Subject: Re: I/o fencing & number of instances per node
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4a23e592.65d6.1681692777@sybase.com>
References: <4a206455.27855524@forums.sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 1 Jun 2009 07:28:34 -0700
X-Trace: forums-1-dub 1243866514 10.22.241.41 (1 Jun 2009 07:28:34 -0700)
X-Original-Trace: 1 Jun 2009 07:28:34 -0700, 10.22.241.41
Lines: 54
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.cluster:146
Article PK: 48432

Jay ,Thank you very much.
I was kind of lost with that manual explanation , and most
of the presentations that I've seen showed at least 2 ASE
instances/per node running .
So our recommendation for a production environment would be
to have one (or 2 maximum) ase instance(s) per node/host
running on multiple engines..?

Thank you
Regards
Jose-Miguel

> On 29 May 2009 12:55:19 -0700, Jose-Miguel Torres wrote:
>
> Jose-Miguel,
>
> A node refers to the hardware host. An instance refers to
> a running ASE image on that node.
>
> What the document is saying that if you were run multiple
> instances on the same node then they are both fenced when
> one of them fails.
>
> I/O Fencing is not a strict requirement for test
> configurations but without it in test or production one
> could get data corruption.
>
> I don't know why you would expect to have 2+ ASE instances
> per node??
>
> Note: each of the ASE instances could be running on many
> engines just like SMP ASE.
>
> Jay
>
> >Hi,
> > Regarding to this note in the Installation Guide:
> >
> >Chapter 3: Creating and Starting the Cluster
> >----------------------------------------------
> >Adding an instance to a cluster
> >
> >"Do not add another instance to a node that already has
> one, >as the IO fencing feature requires that each
> instance be on >a separate node."
> >
> >As I/O fencing is a requierement , does this effectively
> >limit to "1" the number of ASE instances that can be
> >configured by machine ..?
> >(One would expect to have 2+ ASE instances per node)
> >
> >Thank you
> >JMT
>


Jeff Tallman [Sybase] Posted on 2009-06-01 15:27:14.0Z
From: "Jeff Tallman [Sybase]" <jeff.tallman@sybase.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.cluster
Subject: Re: I/o fencing & number of instances per node
References: <4a206455.27855524@forums.sybase.com> <4a23e592.65d6.1681692777@sybase.com>
In-Reply-To: <4a23e592.65d6.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a23f352$1@forums-1-dub>
Date: 1 Jun 2009 08:27:14 -0700
X-Trace: forums-1-dub 1243870034 10.22.241.152 (1 Jun 2009 08:27:14 -0700)
X-Original-Trace: 1 Jun 2009 08:27:14 -0700, vip152.sybase.com
Lines: 71
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.cluster:147
Article PK: 48427

Presentations were most likely showing the 'possibilities' and not what
would be done necessarily. I would only see advantages in multiple
instances per node if the node is domained - at which point it becomes a
separate node (am referring to hard domain vs. soft domain - not sure
why you would want multiple instances in a single soft domain).

Keep in mind that what Jay said is correct, if you have multiple
instances on same node, they both would get iofenced if one does - and
arguably that would be correct as it means ASE cluster lost contact with
one of them - likely due to a network glitch - which would likely affect
both anyhow due to both probably using the same private IP/NIC.

Jeff Tallman
Enterprise Data Management Products Technical Evangelism
jeff.tallman@sybase.com
http://blogs.sybase.com/database

Jose-Miguel Torres wrote:
> Jay ,Thank you very much.
> I was kind of lost with that manual explanation , and most
> of the presentations that I've seen showed at least 2 ASE
> instances/per node running .
> So our recommendation for a production environment would be
> to have one (or 2 maximum) ase instance(s) per node/host
> running on multiple engines..?
>
> Thank you
> Regards
> Jose-Miguel
>
>> On 29 May 2009 12:55:19 -0700, Jose-Miguel Torres wrote:
>>
>> Jose-Miguel,
>>
>> A node refers to the hardware host. An instance refers to
>> a running ASE image on that node.
>>
>> What the document is saying that if you were run multiple
>> instances on the same node then they are both fenced when
>> one of them fails.
>>
>> I/O Fencing is not a strict requirement for test
>> configurations but without it in test or production one
>> could get data corruption.
>>
>> I don't know why you would expect to have 2+ ASE instances
>> per node??
>>
>> Note: each of the ASE instances could be running on many
>> engines just like SMP ASE.
>>
>> Jay
>>
>>> Hi,
>>> Regarding to this note in the Installation Guide:
>>>
>>> Chapter 3: Creating and Starting the Cluster
>>> ----------------------------------------------
>>> Adding an instance to a cluster
>>>
>>> "Do not add another instance to a node that already has
>> one, >as the IO fencing feature requires that each
>> instance be on >a separate node."
>>> As I/O fencing is a requierement , does this effectively
>>> limit to "1" the number of ASE instances that can be
>>> configured by machine ..?
>>> (One would expect to have 2+ ASE instances per node)
>>>
>>> Thank you
>>> JMT


Jose-Miguel Torres Posted on 2009-06-01 17:00:45.0Z
Sender: 658b.4a23e341.1804289383@sybase.com
From: Jose-Miguel Torres
Newsgroups: sybase.public.ase.cluster
Subject: Re: I/o fencing & number of instances per node
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4a24093d.6bc7.1681692777@sybase.com>
References: <4a23f352$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 1 Jun 2009 10:00:45 -0700
X-Trace: forums-1-dub 1243875645 10.22.241.41 (1 Jun 2009 10:00:45 -0700)
X-Original-Trace: 1 Jun 2009 10:00:45 -0700, 10.22.241.41
Lines: 82
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.cluster:148
Article PK: 48431

Jeff/Jay
Thank you vey much for your help. Now I'm very clear about
this
topic

Regards
Jose-Miguel

> Presentations were most likely showing the 'possibilities'
> and not what would be done necessarily. I would only
> see advantages in multiple instances per node if the node
> is domained - at which point it becomes a separate node
> (am referring to hard domain vs. soft domain - not sure
> why you would want multiple instances in a single soft
> domain).
>
> Keep in mind that what Jay said is correct, if you have
> multiple instances on same node, they both would get
> iofenced if one does - and arguably that would be correct
> as it means ASE cluster lost contact with one of them -
> likely due to a network glitch - which would likely affect
> both anyhow due to both probably using the same private
> IP/NIC.
>
> Jeff Tallman
> Enterprise Data Management Products Technical Evangelism
> jeff.tallman@sybase.com
> http://blogs.sybase.com/database
>
> Jose-Miguel Torres wrote:
> > Jay ,Thank you very much.
> > I was kind of lost with that manual explanation , and
> > most of the presentations that I've seen showed at
> > least 2 ASE instances/per node running .
> > So our recommendation for a production environment
> > would be to have one (or 2 maximum) ase instance(s) per
> > node/host running on multiple engines..?
> >
> > Thank you
> > Regards
> > Jose-Miguel
> >
> >> On 29 May 2009 12:55:19 -0700, Jose-Miguel Torres
> wrote: >>
> >> Jose-Miguel,
> >>
> >> A node refers to the hardware host. An instance refers
> to >> a running ASE image on that node.
> >>
> >> What the document is saying that if you were run
> multiple >> instances on the same node then they are both
> fenced when >> one of them fails.
> >>
> >> I/O Fencing is not a strict requirement for test
> >> configurations but without it in test or production one
> >> could get data corruption.
> >>
> >> I don't know why you would expect to have 2+ ASE
> instances >> per node??
> >>
> >> Note: each of the ASE instances could be running on
> many >> engines just like SMP ASE.
> >>
> >> Jay
> >>
> >>> Hi,
> >>> Regarding to this note in the Installation Guide:
> >>>
> >>> Chapter 3: Creating and Starting the Cluster
> >>> ----------------------------------------------
> >>> Adding an instance to a cluster
> >>>
> >>> "Do not add another instance to a node that already
> has >> one, >as the IO fencing feature requires that each
> >> instance be on >a separate node."
> >>> As I/O fencing is a requierement , does this
> effectively >>> limit to "1" the number of ASE instances
> that can be >>> configured by machine ..?
> >>> (One would expect to have 2+ ASE instances per node)
> >>>
> >>> Thank you
> >>> JMT