Slashdot Mirror
Linux Clustering
Bookman emphasizes a central piece of wisdom that no system administrator should ignore: redundancy. In the case of high availability clusters, parts redundancy is the name of the game, but one should not forget the human component; no administrator should be caught with only a cell phone -- keep a pager just in case. However, in a post-modern turn that might seem brilliant if it were applied in a work of fiction rather than a technical book, the author seems to apply the concept of redundancy to the text itself.
That the book began not as a book but rather as a collection of talks or presentations, or some other smaller format, is evidenced by the repetition of information between chapters and sections. Such nearly poetic repetitions also occurs within sentences and paragraphs (e.g. "nightly backups each night" on page 25).
An editor never looked at Linux Clustering; the book had two "technical reviewers" but their contributions seemingly didn't include fixing mangled syntax and strained style. On page 14 in the second paragraph a large segment of a sentence from the previous page is pasted into another sentence, resulting in a nonsensical block of text. The number of hyphenation, syntax, word choice, and subject-verb agreement errors is atrocious and makes the book difficult to read.
Some of the misinformation in the text appears to be unintentional (but ignorance is no excuse for a UNIX systems administrator); some is due to the fact that the author deals only with old (2.2) kernels (though the book came out 18 months after the 2.4 kernel release), old versions of journaling filesystems, and old distributions; and yet other misinformation is the result of misplaced attempts at humor (such as stating that GNU stands for the Gateway Naming Utility; one can only hope that this was intended to be funny). Other jokes often misfire, but do point to the intended audience (consider, for example, the section heading "Space: The Final Frontier").
In the Introduction, the author indicates that the book should be read by "Linux enthusiasts and users who want to get a Linux cluster up and running with the least amount of fuss." The organization of the book will not, however, aid this enterprise, for there is little "how to" information provided, but rather a great deal of background information on compiling kernels, various types of journaling file systems, and RedHat's Kickstart (perhaps inappropriate considering that the book specifically states that basic information will not be covered). Another section or two deal with basic networking and security. Various types of clusters are discussed, as are a few of the types of clustering software (e.g. Condor and Mosix) available.
The book, however, is clearly intended for administrators of clustering systems; a special emphasis is high-availability and load-balancing clusters. Parallel computing and the types of applications end users would wish to run receive far too little discussion.
Almost all technical books regurgitate the contents of freely available FAQs and HOWTOs to some degree, yet the good ones summarize the relevant points, make dry documentation more accessible, and give the reader some new insights. Because Bookman's Linux Clustering suffers from heinous spelling, grammar, and style errors; deals primarily with outdated software; contributes little new to the discussion; and doesn't speak to non-admins, I can only recommend that those interested in Linux clustering stick to online FAQs and HOWTOs.
You can purchase the Linux Clustering: Building and Maintaining Linux Clusters from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
I hate to turn this into an Ask Slashdot, but truth is I could really use a good book on Linux clustering, especially if it covers:
1. Clustering (not just replicating) MySQL databases.
2. Network attached storage.
3. Load balancing and failover.
4. Probably six other things I'm not thinking of right now.
Anyone got any suggestions?
However, there are good uses for modification of vehicles, like say air bags. I don't call air bags, gimmicks, just because I think that guys who put dual exhaust systems on a 20 year old car seem like they are wasting money to me.
However, in terms of redundancy, your far, far better off with 10 P3 500's, then with one P4 5Ghz machine. One of the PIII's is having problems, shut if off, run the diagnostics. The P4 has problems, you shut if off, you are in deep shit.
If I had my choice, I'd rather have a cluster of 5-10 well built, redundant machines then one machine 10 times as fast for any problem that can easily be distributed (think websites, DNS, mail servers). No, I don't want to use 10, 3 year old Dell workstations to serve up my enterprise website, but I wouldn't have any objections to 10 Dell Servers that were bleeding edge 3 years ago assuming it uses parts that are still commonly available.
Kirby
Actually, it would be nice to slow down the pounceposters who stab us with one-liners as soon as an article hits the front page in order to grab that funny karma goodness...
So long, michael. Don't let the door hit you...
That's why I don't buy many books anymore. I can get most of the relevant information for any current topic/projects from the internet. I think the most innovative thing created in the last few years was tabbed browsing, I love Galeon.