[tickets] [opensaf:tickets] #3011 amf: comp stuck in RESTARTING presence state
- **status**: review --> fixed
- **Comment**:
commit bac9c3f53f32e12dce0bfc1aa792a844fa8b4f19
Author: thuan.tran
Date: Wed Mar 6 14:59:56 2019 +1100
amf: fix Comp stuck in RESTARTING presence state [#3011]
During SU (many COMPs) restart recovery, if any COMP finish instantiated
then crash while other COMPs are still instantiating, AMF recovery it by
restarting but AMF only cleanup without re-instantiation because AMF see
the COMP is not eligible for instantiation. The error COMP is stuck in
RESTARTING without further action from AMF.
AMF should allow COMP re-instantiation if SU state is INSTANTIATING and
error COMP state is RESTARTING.
---
** [tickets:#3011] amf: comp stuck in RESTARTING presence state**
**Status:** fixed
**Milestone:** 5.19.03
**Created:** Mon Feb 25, 2019 02:41 AM UTC by Thuan
**Last Updated:** Mon Feb 25, 2019 03:13 AM UTC
**Owner:** Thuan
When a SU (has many comp) is instantatiating for SU restart recovery, some comp
are instantiated then crash, AMF recovery them by restarting but AMF only
cleanup without re-instantiation them because AMF see them are not eligible for
instantiation.
~~~
if (isRestartSet(comp->su)) { // SU is restarting (RESTART admin op or
// recovery policy).
if (isFailed(comp->su)) { // SU is failed (case surestart recovery).
/*During surestart recovery, after cleanup of all components, amfnd
starts
instantiation of components. A component may fault at this stage. Such
a
component is eligible for instantiation.*/
if ((comp->pres == SA_AMF_PRESENCE_INSTANTIATING) &&
(comp->su->pres ==
SA_AMF_PRESENCE_INSTANTIATING))
return true;
~~~
These comp are stuck in RESTATING presence state without further action from
AMF.
---
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.___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3014 log: The value of logRecordDestinationConfiguration is not deleted in lgd
- **status**: review --> fixed - **assigned_to**: Canh Truong --> nobody - **Comment**: commit 89c579247b5b43122301b248433b319054178b58 (HEAD -> develop, origin/develop) Author: Canh Van Truong Date: Thu Feb 28 10:50:42 2019 +0700 log: fix last value of logRecordDestinationConfiguration is not deleted [#3014] When using the command "immcfg logConfig=1,safApp=safLogService -a logRecordDestinationConfiguration-=" If there is just one value in the multi attribute and we delete last one, the value will be deleted in imm database but it is not deleted in LGD. The patch update the attribute "logRecordDestinationConfiguration" = empty in lgd after the last value is deleted. --- ** [tickets:#3014] log: The value of logRecordDestinationConfiguration is not deleted in lgd** **Status:** fixed **Milestone:** 5.19.03 **Created:** Thu Feb 28, 2019 03:33 AM UTC by Canh Truong **Last Updated:** Fri Mar 01, 2019 10:36 AM UTC **Owner:** nobody After removing value "saLogSystem_dest;UNIX_SOCKET;/var/run/stream/CMW_saLogSystem.sock" from logRecordDestinationConfiguration of logConfig=1 successfully SC-2-1:~ # immlist logConfig=1,safApp=safLogService Name Type Value(s) logStreamSystemLowLimitSA_UINT32_T 100 (0x64) logStreamSystemHighLimit SA_UINT32_T 10500 (0x2904) logStreamFileFormatSA_STRING_T @Cr @CY-@Cm-@CdT@Ch:@Cn:@Cs.@Ck@Cz @Cp @Cq @Sl @Sv: "@Cb" logStreamAppLowLimit SA_UINT32_T 1000 (0x3e8) logStreamAppHighLimit SA_UINT32_T 52500 (0xcd14) logRootDirectory SA_STRING_T /storage/no-backup/coremw/var/log/saflog **logRecordDestinationConfiguration SA_STRING_T ** logMaxLogrecsize SA_UINT32_T 32767 (0x7fff) logMaxApplicationStreams SA_UINT32_T 64 (0x40) logFileSysConfig SA_UINT32_T 1 (0x1) logFileIoTimeout SA_UINT32_T 500 (0x1f4) logDataGroupname SA_STRING_T cmw-log-data logConfig SA_STRING_T logConfig=1 SaImmAttrImplementerName SA_STRING_T safLogService SaImmAttrClassName SA_STRING_T OpenSafLogConfig SaImmAttrAdminOwnerNameSA_STRING_T The runtime object logConfig=current was not updated accordingly SC-2-1:~ # immlist logConfig=currentConfig,safApp=safLogService Name Type Value(s) logStreamSystemLowLimitSA_UINT32_T 100 (0x64) logStreamSystemHighLimit SA_UINT32_T 10500 (0x2904) logStreamFileFormatSA_STRING_T @Cr @CY-@Cm-@CdT@Ch:@Cn:@Cs.@Ck@Cz @Cp @Cq @Sl @Sv: "@Cb" logStreamAppLowLimit SA_UINT32_T 1000 (0x3e8) logStreamAppHighLimit SA_UINT32_T 52500 (0xcd14) logRootDirectory SA_STRING_T /storage/no-backup/coremw/var/log/saflog logRecordDestinationStatus SA_STRING_T **logRecordDestinationConfiguration SA_STRING_T saLogSystem_dest;UNIX_SOCKET;/var/run/stream/CMW_saLogSystem.sock** logMaxLogrecsize SA_UINT32_T 32767 (0x7fff) logMaxApplicationStreams SA_UINT32_T 64 (0x40) logFileSysConfig SA_UINT32_T 1 (0x1) logFileIoTimeout SA_UINT32_T 500 (0x1f4) logDataGroupname SA_STRING_T cmw-log-data logConfig SA_STRING_T logConfig=currentConfig SaImmAttrImplementerName SA_STRING_T safLogService SaImmAttrClassName SA_STRING_T OpenSafLogCurrentConfig SaImmAttrAdminOwnerNameSA_STRING_T --- 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3016 osaf: etcd3.plugin slows down cluster shutdown
--- ** [tickets:#3016] osaf: etcd3.plugin slows down cluster shutdown** **Status:** accepted **Milestone:** 5.19.03 **Created:** Thu Mar 07, 2019 06:29 AM UTC by Gary Lee **Last Updated:** Thu Mar 07, 2019 06:29 AM UTC **Owner:** Gary Lee During a cluster shutdown, if the active SC is shutdown first, then the standby SC becomes active if etcd is still up. If etcd is then shutdown, the newly active SC may take a long time to shutdown when it's executing 'watch takeover_request' while etcd is down. 2019-02-27 13:23:55.395 SC-2 osafrded[175]: NO Peer down on node 0x2010f 2019-02-27 13:24:19.824 SC-2 osafrded[175]: NO RDE role set to ACTIVE 2019-02-27 13:24:19.824 SC-2 osafrded[175]: NO Running '/usr/local/lib/opensaf/opensaf_sc_active' with 0 argument(s) <143>1 2019-02-27T13:24:25.296088+01:00 SC-2 osafrded 175 osafrded [meta sequenceId="628"] 821:osaf/consensus/key_value.cc:0 << Execute <143>1 2019-02-27T13:24:25.308915+01:00 SC-2 osafrded 175 osafrded [meta sequenceId="629"] 822:osaf/consensus/key_value.cc:42 TR Executed '/usr/local/lib/opensaf/etcd.plugin watch "takeover_request"', returning 1 <143>1 2019-02-27T13:24:28.430054+01:00 SC-2 osafrded 175 osafrded [meta sequenceId="634"] 821:osaf/consensus/key_value.cc:0 << Execute <143>1 2019-02-27T13:24:28.445755+01:00 SC-2 osafrded 175 osafrded [meta sequenceId="635"] 822:osaf/consensus/key_value.cc:42 TR Executed '/usr/local/lib/opensaf/etcd.plugin watch "takeover_request"', returning 1 <143>1 2019-02-27T13:26:36.97202+01:00 SC-2 osafrded 175 osafrded [meta sequenceId="937"] 821:osaf/consensus/key_value.cc:0 << Execute <143>1 2019-02-27T13:26:36.996691+01:00 SC-2 osafrded 175 osafrded [meta sequenceId="938"] 822:osaf/consensus/key_value.cc:42 TR Executed '/usr/local/lib/opensaf/etcd.plugin watch "takeover_request"', returning 1 --- 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
