DB
Я недавно узнал что у редиса в коде есть проверка, что когда он видит http хедеры типа Host: он обрубает подключение
Size: a a a
2020 May 19
DB
потому что огромное кол-во людей делает ssrf на редис с рутом
A
А есть тлдр?
MongoDB is a distributed document database which claims to offer “among the strongest data consistency, correctness, and safety guarantees of any database available today”, with “full ACID transactions”. Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and allow dirty reads, even downgrading requested safety levels at the database and collection level. Moreover, the snapshot read concern did not guarantee snapshot unless paired with write concern majority—even for read-only transactions. These design choices complicate the safe use of MongoDB transactions. This work was performed independently, without compensation, and conducted in accordance with the Jepsen ethics policy. MongoDB, Fauna, and YugaByte, all mentioned in this report, have previously engaged Jepsen for paid analyses.
DB
Я недавно узнал что у редиса в коде есть проверка, что когда он видит http хедеры типа Host: он обрубает подключение
вот с этого я орал 5 минут
VK
MongoDB is a distributed document database which claims to offer “among the strongest data consistency, correctness, and safety guarantees of any database available today”, with “full ACID transactions”. Jepsen evaluated MongoDB version 4.2.6, and found that even at the strongest levels of read and write concern, it failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and allow dirty reads, even downgrading requested safety levels at the database and collection level. Moreover, the snapshot read concern did not guarantee snapshot unless paired with write concern majority—even for read-only transactions. These design choices complicate the safe use of MongoDB transactions. This work was performed independently, without compensation, and conducted in accordance with the Jepsen ethics policy. MongoDB, Fauna, and YugaByte, all mentioned in this report, have previously engaged Jepsen for paid analyses.
Хех
SN
Смелые парни, ничего не могу сказать.
A
… users would prefer, of course, to use readConcern level “majority” and writeConcern w:“majority”, since everyone wants safety. However, when users find stronger consistency levels to be too slow, they will switch to using weaker consistency levels. These decisions are often based on business requirements and SLAs rather than granular developer needs.
VP
это плохой код?
SN
Шо, скалисты таки кокнули последнюю крупную компанию с f# 🤔 (е_аный рыночек)
это обычная desinformation campaign. проще говоря fake news
SN
это плохой код?
скорее странный
КП
Весь современный мир это сплошная инфовойна всех против всех.
VK
… users would prefer, of course, to use readConcern level “majority” and writeConcern w:“majority”, since everyone wants safety. However, when users find stronger consistency levels to be too slow, they will switch to using weaker consistency levels. These decisions are often based on business requirements and SLAs rather than granular developer needs.
Звучит конечно страшновато
A
я там ещё ору с того, что "Read concern ‘snapshot’ returns data from a snapshot of majority committed data if the transaction commits with write concern ‘majority’"
A
т.е. если ты закоммитал с другим консёрном, то это undefined behaviour
AH
Я вот знал что монга говно, но не настолько же
AH
Я думал она хотя бы БД
A
Я вот знал что монга говно, но не настолько же
ну это про распределённые транзакции в том числе и между шардами
A
в рамках одной ноды там всё норм