During primary space restart when direct persistence is used, records updated in DB might not be replicated and will be missing in the new primary

Description

Customer use direct persistence together with deterministic deployment after failover primary is restarted by deterministic deployment, the shutdown of instance takes a bit long, during that time client keep loading the space, and the customer saw that objects that were inserted to DB (central) were not available on the new primary.

Issue was discussed wit Yechiel that said this is the expected behavior and it will be improved (not 100% fixed) using demote in deterministic deployment
see jira :

Workaround

None

Acceptance Test

None

Assignee

Unassigned

Reporter

Ester Atzmon

Labels

None

Priority

Medium

SalesForce Case ID

None

Fix versions

None

Commitment Version/s

None

Due date

None

Product

XAP

Edition

Premium

Platform

All
Configure