/
What can cause a 412- Precondition Failed message?

What can cause a 412- Precondition Failed message?

By Aaron Enfield
Jun 30, 2017
  1. Enforce tenancy = true and the domain is unknown
  2. Replicate on Write (ROW) cannot find a replication partner
  3. Erasure Coding (EC) "checkIntegrity" fails -- missing segments
  4. Named object write attempted to non-found domain/bucket
  5. Caching If-* conditions can't be satisfied

Related content

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.