Is there any news about this issue ?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 10 2016
I'm probably done for the night, here's a quick update:
Apr 9 2016
Can this be closed now? I don't think there's enough in here to reproduce.
We need this for T4571 for the cluster status console so it doesn't take 10000 years if replicas are down.
Yeah, that should work fine. To promote, you'd update the VIP stuff and Phabricator could remain in the dark.
Ah, I see. In my world master promotion independently of the web tier. The web hosts connect over a VIP which always reaches the current master. We can also connect over a VIP to reach the slaves but don't currently use this.
I think the answer is yes:
I think this is fine to close for now -- the discussion probably remains relevant going forward, but I can point back here the next time a driving use case arises. I think we're unlikely to pursue any of this "suggest a patch" vein of changes on our natural roadmap for a long time.
(I got an error when I created this bug report, which is why I went and added another one. Then, I discover they're BOTH in existence. Meh. Merged duplicate into T10766: Calendar - Unhandled Exception, since I referenced that task elsewhere.)
will this task support setting a separate read-only username and password for database connections? This is useful in our environment to access the slaves.
This is resolved to my satisfaction by {D15468}. @epriestley: should this remain open to pursue something more elaborate in the future?
This is now deployed and appears to be working.
✂✂✂✂✂
✄✄✄✄✄
needs a haircut
yea i noticed that.
Apr 8 2016
Sounds good -- yell at us (or maybe CircleCI?) if you change your mind.
This "shouldn't" be possible: the overseer should restart them if they fail. And if the overseer dies, all the other daemons should die.
Yeah, my bad. Sorry about this. Back to my cave.
See also earlier on the page:
Ugh, my apologies. I stand corrected. It's not, a bit later on the same page
Why do you believe the documentation is inaccurate?
You can now start daemons at a low level by piping JSON into scripts/daemon/phd-daemon:
This is almost a year old and we have no idea how to reproduce it. If anyone hits this, feel free to file a new issue with reproduction steps (see Providing Reproduction Steps).
I fixed the totally unrelated half of this (bad default verbosity of phd debug) at some point in the recent-ish few months.
We got rid of this warning in favor of automatically reloading after config changes, which should survive HA setups without additional work.