4 ms·
Same happened to me many years ago. QA dropped the prod db. It's been many years but if I recall, I believe in the dropdown menu of the MongoDB browser, exit &
by fma 6y ago
Same happened to me many years ago. QA dropped the prod db. It's been many years but if I recall, I believe in the dropdown menu of the MongoDB browser, exit & drop database were next to each other...Spent a whole night replaying the oplog.
No one owned up to it, but had a pretty good idea who it was.
- vanviegen 6y ago> No one owned up to it, but had a pretty good idea who it was. That sounds like you're putting (some of) the blame on whoever misclicked. As opposed to everyone who has allowed this insanely dangerous situation to exist.
- rocqua 6y agoMisclicking is a tiny forgivable mistake. Not immediately calling up your boss to say "I fucked up big" is not a mistake, it is a conscious bad action.
- ojnabieoot 6y agoIt sounds like whoever did it might not even be aware they were responsible: > in the dropdown menu of the MongoDB browser, exit & drop database were next to each other So maybe they signed off for the night without realizing anything was wrong.
- cutemonster 6y agoMongoDB can sell an enterprise version with the buttons further apart
- xtracto 6y agoThis. The person that erased the database in my case came forward to me as soon as we realized what had happened. At that moment I was very happy it was an "inside job", it meant I could discard hacking. As its said before: he made a mistake. The error was allowing the prod database to to be port forwarded from a non prod environment. As head of eng that was MY error. So I owned to it and we changed policies.
- cutemonster 6y agoHow do you prevent forwarding ports? Then one needs to disable ssh access? Nice that you were a person he felt ok with sharing the mistake with, I suppose that's an important part of being head of eng.
- fogihujy 6y ago`AllowTcpForwarding No` There are ways around it, of course, but it prevents the scenario described above.
- cutemonster 6y agoThanks
- xtracto 6y agoNope . The solution is to password protect and not give the pass to developers. Or only give read only access.
- cutemonster 6y agoAnother thought: the company culture and approach to hiring and firing, can cause people to try to hide mistakes, although they don't really want to?
- stennie 6y agoWhich MongoDB browser or admin tool are you referring to? I haven't seen this design in practice using MongoDB Atlas or Compass, but would hope for an "Are you really sure?" confirmation in an admin UI.