I replied to this list. I figured it out. It was my stupid mistake. I use Docker and I automated restoring data from a json file the last time I upgraded keycloak. I never took that line out; it had been a long time since I restarted and when I finally did, that line was still in the Dockerfile. I restored back to the old user data by accident.

On Mon, Sep 7, 2015 at 9:55 AM, Marko Strukelj <mstrukel@redhat.com> wrote:

Sounds like we might not be using WriteConcern.ACKNOWLEDGED.

I think there should be

this.db.setWriteConcern(WriteConcern.ACKNOWLEDGED);

in this line: https://github.com/keycloak/keycloak/blob/master/connections/mongo/src/main/java/org/keycloak/connections/mongo/DefaultMongoConnectionFactoryProvider.java#L92

On Mon, Sep 7, 2015 at 2:47 AM, Dean Peterson <peterson.dean@gmail.com> wrote:
There may be a serious bug in Keycloak. I have a number of users that have been completely wiped from the Keycloak mongodb database after a power outage. Luckily I retain their information in a separate mongodb database with other information or they would be gone forever. When does Keycloak commit user data? The users that are missing are users that registered after the last system restart but before the system went down after a power outage.

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user