?

Log in

No account? Create an account
inveigh, inveigle, invective. - The year was 2081 [entries|archive|friends|userinfo]
matt

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

inveigh, inveigle, invective. [Feb. 22nd, 2005|12:01 am]
matt
[Current Mood |contemplativecontemplative]

inveigh: To give vent to angry disapproval; protest vehemently.
inveigle: To lure by false representations or other deceit; to obtain by cajolery
invective: Denunciatory or abusive expression or discourse.

1. how is it that wikipedia can be down?
2. how do I develop a business model to take on the paradigm of search?
3. invective against those who would inveigle deleted.
4. without "facts" or "statistics", weapons whose truth is forever obscure, can you inveigh against liars?
5. can a suicide critique a coward justly?
LinkReply

Comments:
[User Picture]From: reddragdiva
2005-02-22 02:38 pm (UTC)
1. Disks with writeback cache that LIE about it being disabled. You tell them "don't damn well do this" and they do it anyway. The same thing that meant LJ took ages to come back up after a disk failure.
(Reply) (Thread)
[User Picture]From: hbergeronx
2005-02-22 07:58 pm (UTC)
That may tell me why this happened, but not how.

How is it that the OSS community can stand to see this happen, especially since the issue is a known issue? I have *zero* faith that OSS will ever be worthwhile enterprise/production quality.

How can anyone ever offer service levels that are not total hail marys?
(Reply) (Parent) (Thread)
[User Picture]From: reddragdiva
2005-02-22 08:03 pm (UTC)
This was a hardware vendor lie, not the software (the disk firmware is thoroughly closed).
(Reply) (Parent) (Thread)
[User Picture]From: hbergeronx
2005-02-23 12:25 am (UTC)
This was a hardware vendor lie which was at least known to those who should know, and has a strange tendency to inflict itself on MySQL servers?
(Reply) (Parent) (Thread)
[User Picture]From: reddragdiva
2005-02-23 12:38 am (UTC)
So far it was known from the LJ case; now that it's known from the Wikimedia case, I expect some rather close questioning of the hardware vendor.

The admins swear this wasn't actually a MySQL problem, despite many claiming it must have been. I assume they know their system better than I do.

(Wikimedia currently gets a fair bit of free consulting assistance from MySQL AB, as MySQL AB are keenly aware of the work to get MediaWiki fully functional on PostGreSQL.)

One of the problems is that Wikimedia is barely above hobby status as an operation, never mind its top 200 status. It was started by a dotcom winner and currently has half an employee (all the devs and almost all the sysadmins are volunteers; the funding drives go almost entirely on server hardware). It's a victim of its own success and life is a perpetual "WTF?!" moment.
(Reply) (Parent) (Thread)
[User Picture]From: hbergeronx
2005-02-23 04:29 am (UTC)
The library at alexandria comes to mind.
(Reply) (Parent) (Thread)
[User Picture]From: reddragdiva
2005-02-23 11:11 am (UTC)
At least there are copies of this one around.
(Reply) (Parent) (Thread)
[User Picture]From: reddragdiva
2005-02-23 06:39 pm (UTC)
Here's the postmortem. They are not certain it's the hardware, and they're not so pleased with MySQL. Note the clearly hobby-level running of the site ... life really is a continuous "WTF?!" moment there.

(Compare the LJ crash postmortem.)

My current hobbyhorse is the quest for paper. But some of the stuff I want for that (the reviewing feature, so that reviewing will actually scale), I'll need to write myself for it to happen; so I've been working through this as well. Just installed the prerequisites, now to pull in MediaWiki from CVS ...
(Reply) (Parent) (Thread)