Hi Ildar, I remember there was a compact dataset command that forces the flush, but I have never used it. Alternatively, you can simply add an HTTP cluster API to be used during development and send a message to all NCs to flush all datasets upon receiving the request.
As for the message ACK during instance shutdown, it is not there by default but you can implement it yourself. For example, you can force an NC to wait - as part of stopping a life cycle component (e.g. StatisticsManager) - until it receives some kind of a message, which indicates that all messages have been processed, from other NCs or the CC. Cheers, Murtadha > On Jan 19, 2017, at 6:02 AM, Ildar Absalyamov <[email protected]> > wrote: > > Hi devs, > > Since I was out for quite a while and a lot of things happened in a meantime > in a codebase I wanted to clarify couple of things. > > I was wondering if there is any legitimate way to force the data of in-memory > components to be flushed, other then stop the whole instance? > It used to be that choosing a different default dataverse with “use” > statement did that trick, but that is not the case anymore. > > Another question is regarding CC<->NC & NC<->NC messaging. Does the sender > get some kind of ACK that the message was received by the addressee? Say if I > send a message just before the instance shutdown will the shutdown hook wait > until the message is delivered and processed? > > Best regards, > Ildar >
