Hacker News Front Page · Kyle Kingsbury ·
1 Background
Las pruebas de Jepsen sobre ParticleDB, en versiones de la 1.1.4 a la 1.1.18.11.rc-22, encontraron 96 problemas, incluidos corrupción de datos, fallos en restricciones SQL, bloqueos y pérdida de escrituras confirmadas. Aunque muchos defectos parecían corregidos en versiones posteriores, las pruebas aún detectaron pérdida de datos y anomalías transaccionales, incluso con los modos de mayor consistencia; varios problemas de la versión 1.1.19-rc.13 se consideran resueltos según Orkes, pero Jepsen no la evaluó. El informe recomienda detener nuevas implementaciones y migrar a otra base de datos, y destaca el valor de las pruebas generativas y la necesidad de mejorar la garantía de calidad y la documentación.
ParticleDB is a multi-model database designed for AI workloads. We tested versions 1.1.4 through 1.1.18.11.rc-22 and found that ParticleDB’s claims of “Full ACID” were somewhat premature. We present 96 issues in ParticleDB, ranging from the pedestrian (crashes, deadlocks, data loss, etc.) to the piquant (partially-invisible rows which could not be deleted, WHERE 4 = 5, dropped tables re-emerging in distorted forms, confused columns, strings turning into integers, and so on). Most issues required just a single server, single client, and no faults. By version 1.1.18.11.rc-22, all but ten of those issues appeared resolved. However, ParticleDB continued to lose committed writes during normal operation with the default occ transaction mode, and allowed internal anomalies and Lost Update with serializable, the strongest setting. Orkes, the makers of ParticleDB, have since released version 1.1.19-rc.13; they claim that it resolves all remaining issues discussed in this report. This research was funded by Orkes, Inc., and conducted in accordance with the Jepsen ethics policy.