Fix bad cluster.database in documentation
Summary: This is mistaken.
Test Plan: Careful inspection, grep for other mistakes.
Reviewers: chad, eadler
Reviewed By: eadler
Differential Revision: https://secure.phabricator.com/D15717
Description
Description
Details
Details
- Provenance
epriestley Authored on Apr 14 2016, 9:58 PM epriestley Pushed on Apr 14 2016, 10:00 PM - Reviewer
- eadler
- Differential Revision
- D15717: Fix bad `cluster.database` in documentation
- Parents
- rP7852ec16190f: Use --master-data, not --dump-slave, in bin/storage dump
- Branches
- Unknown
- Tags
- Build Status
Buildable 11739 Build 14707: Run Core Tests
Event Timeline
Comment Actions
I noticed an issue with mail that I received regarding this commit.
This may have already been fixed, but just-in-case.
Comment Actions
I think this was because I was briefly running daemons against a replica database with a bad dataset. Let me know if it happens again, but I know a handful of duplicate / screwed up mail messages went out.
Possibly we should also make that message not echo the whole token. It's not really dangerous in any way that I can come up with, but it would be just as useful to print the first, say, "clr-ukkw...".