Saving every so many, and synced with, insertions might be an
alternative, perhaps with an upper limit on the frequency. This limits
recovery time as well as time spent on creating the snapshots.
-W
On 12/08/2013, Mauricio Salatino <salaboy(a)gmail.com> wrote:
IMO that's a very difficult problem to solve.. because if you
want to do it
every X seconds you can be caught in the middle of an execution. If you
delay the snapshot creation for when the execution ends, you will probably
caught in the next snapshot creation.
Depending on what are you doing within your rules, you can always recreate
the session from the scratch. You can also use rules to summarize state and
persist that summaries in your external database, that can save you some
time.
HTH
On Mon, Aug 12, 2013 at 8:52 AM, IK81 <ml(a)kofler.me> wrote:
> Hi,
>
> I am looking for a solution to make the engine's state persistent in
> regular
> intervals. I do not want to persist the engine's state at every event
> insertion for performance reasons. Instead I am thinking of making a
> snapshot of the engine's state let's say every X seconds. The events I
> have
> are always stored to a database. In case of a crash or reboot I'd like to
> recover the engine's state from the snapshot + reinserting the events
> that
> happened after the timestamp of my snapshot.
>
> Are there any hints or caveats regarding this approach?
>
> Best regards,
> Ingo
>
>
>
>
> --
> View this message in context:
>
http://drools.46999.n3.nabble.com/Snapshot-of-drools-engine-s-state-tp402...
> Sent from the Drools: User forum mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
--
- MyJourney @
http://salaboy.com <
http://salaboy.wordpress.com>
- Co-Founder @
http://www.jugargentina.org
- Co-Founder @
http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -