[tickets] [opensaf:tickets] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".
- **status**: unassigned --> assigned - **Blocker**: --> False --- ** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()". ** **Status:** assigned **Milestone:** 5.2.FC **Created:** Thu May 16, 2013 06:41 AM UTC by Praveen **Last Updated:** Wed Apr 12, 2017 06:50 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2817. Changeset:3728 When saAmfComponentErrorReport_4() and saAmfComponentErrorReport_4() are called after finalizing the amfHandle(calling saAmfFinalize()), both of them returns SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #243 amf:Response_4 fails with ERR_VERSION even when invoked with correct versioned handle
- **status**: assigned --> invalid
- **Milestone**: future --> never
- **Comment**:
So, marking as invalid
---
** [tickets:#243] amf:Response_4 fails with ERR_VERSION even when invoked with
correct versioned handle**
**Status:** invalid
**Milestone:** never
**Created:** Thu May 16, 2013 06:32 AM UTC by Praveen
**Last Updated:** Wed Jul 19, 2017 05:47 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**
-
[amf_demo_243.c](https://sourceforge.net/p/opensaf/tickets/243/attachment/amf_demo_243.c)
(15.4 kB; application/octet-stream)
Migrated from http://devel.opensaf.org/ticket/2877.
The issue is seen on SLES 64bit VMs.
Migrated from http://devel.opensaf.org/ticket/2877.
The component initially initializes with B.4.1. Another initialize is invoked
with B.1.1 version. When callbacks arrived at the component, Response_4 is
invoked with the handle obtained from B.4.1 initialization. Response_4 returned
SA_AIS_ERR_VERSION.
Output from the component log:
Invoking the function with the arguments
(4289724417, 4271898630L, None, 1)
('Return Value of the function : <—', 1) ==> Response_4 invoked before doing
Initialize with B.1.1 version
Invoking the function
('Return Value of the function : <—', [1, 4290772994])
Invoking the function with the arguments
(4289724417, 4287627277L, None, 1)
('Return Value of the function : <—', 3) ===> same handle as used before but
got ERR_VERSION now.
Traces can be shared if required.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #243 amf:Response_4 fails with ERR_VERSION even when invoked with correct versioned handle
Jul 19 11:11:24 PM_SC-1 osafamfnd[30940]: NO
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING =>
INSTANTIATED
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: HC started with AMF 4
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: 1. saAmfComponentRegister FAILED, But
Continueing 14
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: HC started with AMF for 1
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: Registered with AMF
Jul 19 11:11:24 PM_SC-1 amf_demo[31113]: Health check 1
Jul 19 11:11:34 PM_SC-1 amf_demo[31113]: Health check 2
Jul 19 11:11:44 PM_SC-1 amf_demo[31113]: Health check 3
Jul 19 11:11:54 PM_SC-1 amf_demo[31113]: Health check 4
The response was given to Amf 4.1 callback.
---
** [tickets:#243] amf:Response_4 fails with ERR_VERSION even when invoked with
correct versioned handle**
**Status:** assigned
**Milestone:** future
**Created:** Thu May 16, 2013 06:32 AM UTC by Praveen
**Last Updated:** Wed Jul 19, 2017 05:45 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**
-
[amf_demo_243.c](https://sourceforge.net/p/opensaf/tickets/243/attachment/amf_demo_243.c)
(15.4 kB; application/octet-stream)
Migrated from http://devel.opensaf.org/ticket/2877.
The issue is seen on SLES 64bit VMs.
Migrated from http://devel.opensaf.org/ticket/2877.
The component initially initializes with B.4.1. Another initialize is invoked
with B.1.1 version. When callbacks arrived at the component, Response_4 is
invoked with the handle obtained from B.4.1 initialization. Response_4 returned
SA_AIS_ERR_VERSION.
Output from the component log:
Invoking the function with the arguments
(4289724417, 4271898630L, None, 1)
('Return Value of the function : <—', 1) ==> Response_4 invoked before doing
Initialize with B.1.1 version
Invoking the function
('Return Value of the function : <—', [1, 4290772994])
Invoking the function with the arguments
(4289724417, 4287627277L, None, 1)
('Return Value of the function : <—', 3) ===> same handle as used before but
got ERR_VERSION now.
Traces can be shared if required.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #243 amf:Response_4 fails with ERR_VERSION even when invoked with correct versioned handle
Please find attached sample file, used in testing.
I tested on CS #8791. I didn't get any issue. Health check continued.
---
** [tickets:#243] amf:Response_4 fails with ERR_VERSION even when invoked with
correct versioned handle**
**Status:** assigned
**Milestone:** future
**Created:** Thu May 16, 2013 06:32 AM UTC by Praveen
**Last Updated:** Wed Jul 19, 2017 05:43 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**
-
[amf_demo_243.c](https://sourceforge.net/p/opensaf/tickets/243/attachment/amf_demo_243.c)
(15.4 kB; application/octet-stream)
Migrated from http://devel.opensaf.org/ticket/2877.
The issue is seen on SLES 64bit VMs.
Migrated from http://devel.opensaf.org/ticket/2877.
The component initially initializes with B.4.1. Another initialize is invoked
with B.1.1 version. When callbacks arrived at the component, Response_4 is
invoked with the handle obtained from B.4.1 initialization. Response_4 returned
SA_AIS_ERR_VERSION.
Output from the component log:
Invoking the function with the arguments
(4289724417, 4271898630L, None, 1)
('Return Value of the function : <—', 1) ==> Response_4 invoked before doing
Initialize with B.1.1 version
Invoking the function
('Return Value of the function : <—', [1, 4290772994])
Invoking the function with the arguments
(4289724417, 4287627277L, None, 1)
('Return Value of the function : <—', 3) ===> same handle as used before but
got ERR_VERSION now.
Traces can be shared if required.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #243 amf:Response_4 fails with ERR_VERSION even when invoked with correct versioned handle
- Attachments has changed:
Diff:
--- old
+++ new
@@ -0,0 +1 @@
+amf_demo_243.c (15.4 kB; application/octet-stream)
---
** [tickets:#243] amf:Response_4 fails with ERR_VERSION even when invoked with
correct versioned handle**
**Status:** assigned
**Milestone:** future
**Created:** Thu May 16, 2013 06:32 AM UTC by Praveen
**Last Updated:** Tue Jul 18, 2017 10:34 AM UTC
**Owner:** Nagendra Kumar
**Attachments:**
-
[amf_demo_243.c](https://sourceforge.net/p/opensaf/tickets/243/attachment/amf_demo_243.c)
(15.4 kB; application/octet-stream)
Migrated from http://devel.opensaf.org/ticket/2877.
The issue is seen on SLES 64bit VMs.
Migrated from http://devel.opensaf.org/ticket/2877.
The component initially initializes with B.4.1. Another initialize is invoked
with B.1.1 version. When callbacks arrived at the component, Response_4 is
invoked with the handle obtained from B.4.1 initialization. Response_4 returned
SA_AIS_ERR_VERSION.
Output from the component log:
Invoking the function with the arguments
(4289724417, 4271898630L, None, 1)
('Return Value of the function : <—', 1) ==> Response_4 invoked before doing
Initialize with B.1.1 version
Invoking the function
('Return Value of the function : <—', [1, 4290772994])
Invoking the function with the arguments
(4289724417, 4287627277L, None, 1)
('Return Value of the function : <—', 3) ===> same handle as used before but
got ERR_VERSION now.
Traces can be shared if required.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2530 amfd: amfd coredump after SC absence
- **status**: unassigned --> accepted
- **assigned_to**: Minh Hon Chau
---
** [tickets:#2530] amfd: amfd coredump after SC absence**
**Status:** accepted
**Milestone:** 5.17.08
**Labels:** assignment failover during stop of both SC
**Created:** Wed Jul 19, 2017 03:00 AM UTC by Minh Hon Chau
**Last Updated:** Wed Jul 19, 2017 03:00 AM UTC
**Owner:** Minh Hon Chau
amfd coredump happens in the same sceario of ticket #2477
In #2477, amfd prevents to create 2 active assignments for same 2N SI, but amfd
has missed a case of 2 standby assignments, which leads to the coredump in this
ticket
backtrace:
~~~
#0 0x7f4092cdb0c7 in raise () from /lib64/libc.so.6
#1 0x7f4092cdc478 in abort () from /lib64/libc.so.6
#2 0x7f4093b3be2e in __osafassert_fail (__file=,
__line=, __func=,
__assertion=) at ../../opensaf/src/base/sysf_def.c:286
#3 0x7f4094aa1058 in avd_sg_2n_act_susi (sg=sg@entry=0x7f4096ba41f0,
stby_susi=stby_susi@entry=0x7ffe4e89ae80,
cb=0x7f4094d2ce80 <_control_block>) at
../../opensaf/src/amf/amfd/sg_2n_fsm.cc:596
#4 0x7f4094aa1b8f in avd_sg_2n_su_chose_asgn (cb=cb@entry=0x7f4094d2ce80
<_control_block>, sg=0x7f4096ba41f0)
at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:649
#5 0x7f4094aa70de in SG_2N::node_fail (this=0x7f4096ba41f0,
cb=0x7f4094d2ce80 <_control_block>, su=0x7f4096bb6dd0)
at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:3583
#6 0x7f4094a97c8a in AVD_SG::failover_absent_assignment
(this=0x7f4096ba41f0)
at ../../opensaf/src/amf/amfd/sg.cc:2310
#7 0x7f4094a4e155 in avd_cluster_tmr_init_evh (cb=0x7f4094d2ce80
<_control_block>, evt=)
at ../../opensaf/src/amf/amfd/cluster.cc:103
#8 0x7f4094a7689c in process_event (cb_now=0x7f4094d2ce80
<_control_block>, evt=0x7f4084000c20)
at ../../opensaf/src/amf/amfd/main.cc:775
#9 0x7f4094a3082e in main_loop () at ../../opensaf/src/amf/amfd/main.cc:691
#10 main (argc=, argv=) at
../../opensaf/src/amf/amfd/main.cc:848
(gdb) f 3
#3 0x7f4094aa1058 in avd_sg_2n_act_susi (sg=sg@entry=0x7f4096ba41f0,
stby_susi=stby_susi@entry=0x7ffe4e89ae80,
cb=0x7f4094d2ce80 <_control_block>) at
../../opensaf/src/amf/amfd/sg_2n_fsm.cc:596
596 ../../opensaf/src/amf/amfd/sg_2n_fsm.cc: No such file or directory.
(gdb) p a_susi_1->si->list_of_sisu->su->name
$1 = {static npos = ,
_M_dataplus = { = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x7f4096bb84d8 "safSu=SC-2,safSg=2N,safApp=ABC"}}
(gdb) p a_susi_1->si->list_of_sisu->state
$2 = SA_AMF_HA_STANDBY
(gdb) p a_susi_1->si->list_of_sisu->fsm
$3 = AVD_SU_SI_STATE_ABSENT
(gdb) p a_susi_1->si->list_of_sisu->si_next->su->name
$4 = {static npos = ,
_M_dataplus = { = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x7f4096bb39d8 "safSu=db68a05892,safSg=2N,safApp=ABC"}}
(gdb) p a_susi_1->si->list_of_sisu->si_next->fsm
$5 = AVD_SU_SI_STATE_ASGND
(gdb) p a_susi_1->si->list_of_sisu->si_next->state
$6 = SA_AMF_HA_STANDBY
(gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->su->name
$7 = {static npos = ,
_M_dataplus = { = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x7f4096bbb6e8 "safSu=PL-4,safSg=2N,safApp=ABC"}}
(gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->fsm
$8 = AVD_SU_SI_STATE_ASGND
(gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->state
$9 = SA_AMF_HA_ACTIVE
(gdb)
~~~
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2530 amfd: amfd coredump after SC absence
---
** [tickets:#2530] amfd: amfd coredump after SC absence**
**Status:** unassigned
**Milestone:** 5.17.08
**Labels:** assignment failover during stop of both SC
**Created:** Wed Jul 19, 2017 03:00 AM UTC by Minh Hon Chau
**Last Updated:** Wed Jul 19, 2017 03:00 AM UTC
**Owner:** nobody
amfd coredump happens in the same sceario of ticket #2477
In #2477, amfd prevents to create 2 active assignments for same 2N SI, but amfd
has missed a case of 2 standby assignments, which leads to the coredump in this
ticket
backtrace:
~~~
#0 0x7f4092cdb0c7 in raise () from /lib64/libc.so.6
#1 0x7f4092cdc478 in abort () from /lib64/libc.so.6
#2 0x7f4093b3be2e in __osafassert_fail (__file=,
__line=, __func=,
__assertion=) at ../../opensaf/src/base/sysf_def.c:286
#3 0x7f4094aa1058 in avd_sg_2n_act_susi (sg=sg@entry=0x7f4096ba41f0,
stby_susi=stby_susi@entry=0x7ffe4e89ae80,
cb=0x7f4094d2ce80 <_control_block>) at
../../opensaf/src/amf/amfd/sg_2n_fsm.cc:596
#4 0x7f4094aa1b8f in avd_sg_2n_su_chose_asgn (cb=cb@entry=0x7f4094d2ce80
<_control_block>, sg=0x7f4096ba41f0)
at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:649
#5 0x7f4094aa70de in SG_2N::node_fail (this=0x7f4096ba41f0,
cb=0x7f4094d2ce80 <_control_block>, su=0x7f4096bb6dd0)
at ../../opensaf/src/amf/amfd/sg_2n_fsm.cc:3583
#6 0x7f4094a97c8a in AVD_SG::failover_absent_assignment
(this=0x7f4096ba41f0)
at ../../opensaf/src/amf/amfd/sg.cc:2310
#7 0x7f4094a4e155 in avd_cluster_tmr_init_evh (cb=0x7f4094d2ce80
<_control_block>, evt=)
at ../../opensaf/src/amf/amfd/cluster.cc:103
#8 0x7f4094a7689c in process_event (cb_now=0x7f4094d2ce80
<_control_block>, evt=0x7f4084000c20)
at ../../opensaf/src/amf/amfd/main.cc:775
#9 0x7f4094a3082e in main_loop () at ../../opensaf/src/amf/amfd/main.cc:691
#10 main (argc=, argv=) at
../../opensaf/src/amf/amfd/main.cc:848
(gdb) f 3
#3 0x7f4094aa1058 in avd_sg_2n_act_susi (sg=sg@entry=0x7f4096ba41f0,
stby_susi=stby_susi@entry=0x7ffe4e89ae80,
cb=0x7f4094d2ce80 <_control_block>) at
../../opensaf/src/amf/amfd/sg_2n_fsm.cc:596
596 ../../opensaf/src/amf/amfd/sg_2n_fsm.cc: No such file or directory.
(gdb) p a_susi_1->si->list_of_sisu->su->name
$1 = {static npos = ,
_M_dataplus = { = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x7f4096bb84d8 "safSu=SC-2,safSg=2N,safApp=ABC"}}
(gdb) p a_susi_1->si->list_of_sisu->state
$2 = SA_AMF_HA_STANDBY
(gdb) p a_susi_1->si->list_of_sisu->fsm
$3 = AVD_SU_SI_STATE_ABSENT
(gdb) p a_susi_1->si->list_of_sisu->si_next->su->name
$4 = {static npos = ,
_M_dataplus = { = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x7f4096bb39d8 "safSu=db68a05892,safSg=2N,safApp=ABC"}}
(gdb) p a_susi_1->si->list_of_sisu->si_next->fsm
$5 = AVD_SU_SI_STATE_ASGND
(gdb) p a_susi_1->si->list_of_sisu->si_next->state
$6 = SA_AMF_HA_STANDBY
(gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->su->name
$7 = {static npos = ,
_M_dataplus = { = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x7f4096bbb6e8 "safSu=PL-4,safSg=2N,safApp=ABC"}}
(gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->fsm
$8 = AVD_SU_SI_STATE_ASGND
(gdb) p a_susi_1->si->list_of_sisu->si_next->si_next->state
$9 = SA_AMF_HA_ACTIVE
(gdb)
~~~
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #243 amf:Response_4 fails with ERR_VERSION even when invoked with correct versioned handle
- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar
- **Part**: - --> lib
- **Blocker**: --> False
---
** [tickets:#243] amf:Response_4 fails with ERR_VERSION even when invoked with
correct versioned handle**
**Status:** assigned
**Milestone:** future
**Created:** Thu May 16, 2013 06:32 AM UTC by Praveen
**Last Updated:** Mon Apr 03, 2017 06:47 PM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2877.
The issue is seen on SLES 64bit VMs.
Migrated from http://devel.opensaf.org/ticket/2877.
The component initially initializes with B.4.1. Another initialize is invoked
with B.1.1 version. When callbacks arrived at the component, Response_4 is
invoked with the handle obtained from B.4.1 initialization. Response_4 returned
SA_AIS_ERR_VERSION.
Output from the component log:
Invoking the function with the arguments
(4289724417, 4271898630L, None, 1)
('Return Value of the function : <—', 1) ==> Response_4 invoked before doing
Initialize with B.1.1 version
Invoking the function
('Return Value of the function : <—', [1, 4290772994])
Invoking the function with the arguments
(4289724417, 4287627277L, None, 1)
('Return Value of the function : <—', 3) ===> same handle as used before but
got ERR_VERSION now.
Traces can be shared if required.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2509 osaf: Support self scale-out
- **status**: assigned --> accepted --- ** [tickets:#2509] osaf: Support self scale-out** **Status:** accepted **Milestone:** 5.17.10 **Created:** Wed Jun 21, 2017 09:23 AM UTC by Anders Widell **Last Updated:** Sat Jul 01, 2017 04:15 PM UTC **Owner:** Anders Widell Ticket [#1453] added support for scale-out, which allows scale-out from an initial cluster containing at least one node. This ticket add support for scaling out from a cluster containing zero nodes, or alternatively, a cluster where the active node is not a configured node. The use cases are as follows: * Support loading a backup that was created on a different cluster where none of the new nodes have the same name as any of the nodes in the old cluster. * Support cluster restart on a system where nodes don't have persistent local storage (or persistent host names / node names) - i.e. a system where a node reboot will always cause a scale-in followed by a scale-out * Make scaling more robust, e.g. imagine a case when a one-node cluster is scaled out by adding a second node, but then the original node is removed before scale-out of the new node has completed. One possible solution is that when a node boots up and becomes the newly elected active system controller (i.e. the first active system controller after a cluster restart), it will check if the node itself exists as a configured node in the IMM database. If it does not, then at first only IMM will be started and the scale-out script (added in ticket [#1453]) will be called to scale out the current node. When the current node has added to IMM, the rest of the OpenSAF services are started. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
