Hi Praveen,
I understand how the AMF callback code works, in this case it does not timeout,
the call the Ckpt open and the read both return success, this occurs before the
configured timeout. I will post the logs in a following email.
On Jan 11, 2016, at 1:50 AM, praveen malviya
On 08-Jan-16 5:09 PM, Tony Hart wrote:
>
> There are no errors returned from the osaf calls, there are no error logs
> generated.
>
> What problems would writing to the checkpoint in an AMF callback cause?
Is any fault reported on the component which received the active
callback? And what is
The problem happens even with 20MB, which is less than the system limit.
> On Jan 7, 2016, at 10:19 PM, A V Mahesh wrote:
>
> Hi,
>
>>> (so the standby code does not run until the active code is done).
>
> If above the sequence of checkpoint writing , you should be
There are no errors returned from the osaf calls, there are no error logs
generated.
What problems would writing to the checkpoint in an AMF callback cause?
—
tony
> On Jan 7, 2016, at 10:23 PM, A V Mahesh wrote:
>
>
> One more thing ideally writing checkpoint kind
One more thing ideally writing checkpoint kind of operation are NOT
suggested in CALLBACKs
what exactly is your requirement ?
Did error handling is done properly ?
-AVM
On 1/8/2016 8:49 AM, A V Mahesh wrote:
> Hi,
>
>>> (so the standby code does not run until the active code is done).
>
>
Should also mention that this is using the synchronous API calls.
> On Jan 7, 2016, at 10:55 AM, Tony Hart wrote:
>
> OpenSAF 4.5.1
>
> We’re seeing an issue where checkpoints are not syncing between two nodes
> (the data in one is different from the other). There are