Hi Canh,
You are right about that configuration streams except the "well known" ones can
be deleted but if the stream configuration object exist and numOpeners = 0
there is an inconsistency that must be considered as "out of synch" that
requires a restart.
Regards
Lennart
From: Canh Van
Thanks Lennart,
Please my comments.
Regards
Canh
From: Lennart Lund
Sent: Tuesday, March 26, 2019 3:41 PM
To: Canh Van Truong ; Vu Minh Nguyen
Cc: opensaf-devel@lists.sourceforge.net; Lennart Lund
Subject: RE: [PATCH 1/1] log: logd crash due to well known stream has
numOpeners = 0
ack, review only/Thanks HansN
-Original Message-
From: Gary Lee
Sent: den 26 mars 2019 02:05
To: Minh Hon Chau ; Hans Nordebäck
Cc: opensaf-devel@lists.sourceforge.net; Gary Lee
Subject: [PATCH 1/1] osaf: ensure an error is returned if takeover_request
fails [#3023]
if we cannot
Hi Canh,
I don't really understand what you suggest and how this will keep standby and
active in sync. However, there are two things I would like to mention:
1. It is not only the "well known streams" if you by this means the alarm,
notification and system streams that must never have 0
When underlying file system is unresponsive to pbe write request, all IMM
requests that required to be persistent such as creating an IMM object or
creating an IMM class likely gets SA_AIS_ERR_TIMEOUT.
This changeset introduces two administrative operations which are provided to
let user inform
Summary: imm: return try-again on write requests while fs is unavailable [#3019]
Review request for Ticket(s): 3019
Peer Reviewer(s): Hans, Lennart, Gary
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-3019
Base revision:
