It is safe to remove all data that the shard coordinator stored when you restart the cluster. Stop all nodes, remove the data and then start them again.
You should probably investigate why your data got corrupt. The usual suspect is that you got multiple writers to the same persistenceId, i.e. you have split the cluster into two separate clusters. That can happen if you use auto-down. Cheers, Patrik On Mon, Jun 22, 2015 at 2:09 PM, Diego Martinoia <[email protected]> wrote: > Hi All, > > While using the cluster sharding extension, you have to provide some sort > of persistence journal so that the plugin can store its metadata > (ShardRegionAllocated, etc...). > > These metadata are used when new actors are instantiated / moved across > nodes to recover from their frozen state. > > Suppose that for any reason your journal becomes corrupted (loses one > entry, duplicates an entry, whatever). This leads to pretty bad exceptions > at the actor's startup (Persistence recovery failure), possibly terminating > the whole region if not correctly handled. > > What is the best way to manage this scenario? (I'm asking for ideas at any > level of the stack, from the supervisor's policy to some sort of > intervention directly on the journal) > > Any ideas welcome! > > Thanks, > > D. > > Notice: This email is confidential and may contain copyright material of > members of the Ocado Group. Opinions and views expressed in this message > may not necessarily reflect the opinions and views of the members of the > Ocado Group. > > > > If you are not the intended recipient, please notify us immediately and > delete all copies of this message. Please note that it is your > responsibility to scan this message for viruses. > > > > Fetch and Sizzle are trading names of Speciality Stores Limited, a member > of the Ocado Group. > > > > References to the “Ocado Group” are to Ocado Group plc (registered in > England and Wales with number 7098618) and its subsidiary undertakings (as > that expression is defined in the Companies Act 2006) from time to time. > The registered office of Ocado Group plc is Titan Court, 3 Bishops Square, > Hatfield Business Park, Hatfield, Herts. AL10 9NE. > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: > http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
