diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/sgml/administration.sgml | 31 | ||||
| -rw-r--r-- | docs/sgml/database.sgml | 5 | ||||
| -rw-r--r-- | docs/sgml/installation.sgml | 4 | ||||
| -rw-r--r-- | docs/xml/administration.xml | 31 | ||||
| -rw-r--r-- | docs/xml/database.xml | 5 | ||||
| -rw-r--r-- | docs/xml/installation.xml | 4 |
6 files changed, 26 insertions, 54 deletions
diff --git a/docs/sgml/administration.sgml b/docs/sgml/administration.sgml index 1873ee025..847527203 100644 --- a/docs/sgml/administration.sgml +++ b/docs/sgml/administration.sgml @@ -69,8 +69,14 @@ write locking. What this means is that if someone needs to make a change to a bug, they will lock the entire table until the operation is complete. Locking for write also blocks reads until the write is - complete. The - <quote>shadowdb</quote> + complete. Note that more recent versions of mysql support row level + locking using different table types. These types are slower than the + standard type, and Bugzilla does not yet take advantage of features + such as transactions which would justify this speed decrease. The + Bugzilla team are, however, happy to hear about any experiences with + row level locking and Bugzilla</para> + + <para>The <quote>shadowdb</quote> parameter was designed to get around this limitation. While only a single user is allowed to write to a table at a time, reads can continue unimpeded on a read-only shadow copy of the database. @@ -85,23 +91,10 @@ Bugzilla bug changes and comments per day.</para> <para>The value of the parameter defines the name of the - shadow bug database. - Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a - *very* large installation of Bugzilla. - <note> - <para>Enabling "shadowdb" can adversely affect the stability of - your installation of Bugzilla. You should regularly check that your - database is in sync. It is often advisable to force a shadow - database sync nightly via - <quote>cron</quote>. - </para> - </note> - </para> - - <para>If you use the "shadowdb" option, it is only natural that you - should turn the "queryagainstshadowdb" option on as well. Otherwise - you are replicating data into a shadow database for no reason!</para> - + shadow bug database. You will need to set the host and port settings + from the params page, and set up replication in your database server + so that updates reach this readonly mirror. Consult your database + documentation for more detail.</para> </step> <step> diff --git a/docs/sgml/database.sgml b/docs/sgml/database.sgml index ae1918207..d32bb57cc 100644 --- a/docs/sgml/database.sgml +++ b/docs/sgml/database.sgml @@ -198,7 +198,6 @@ | products | | profiles | | profiles_activity | -| shadowlog | | tokens | | versions | | votes | @@ -290,10 +289,6 @@ sshh... don't tell your users!) profiles_activity: Need to know who did what when to who's profile? This'll tell you, it's a pretty complete history. -shadowlog: I could be mistaken here, but I believe this table tells you when -your shadow database is updated and what commands were used to update it. We -don't use a shadow database at our site yet, so it's pretty empty for us. - versions: Version information for every product votes: Who voted for what when diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml index 8d1a94ec7..7aec021ce 100644 --- a/docs/sgml/installation.sgml +++ b/docs/sgml/installation.sgml @@ -559,9 +559,7 @@ AllowOverride Limit <para>There are important files and directories that should not be a served by the HTTP server - most files in the <quote>data</quote> - and - <quote>shadow</quote> - directories and the + directory and the <quote>localconfig</quote> file. You should configure your HTTP server to not serve these files. Failure to do so will expose critical passwords and diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml index 1873ee025..847527203 100644 --- a/docs/xml/administration.xml +++ b/docs/xml/administration.xml @@ -69,8 +69,14 @@ write locking. What this means is that if someone needs to make a change to a bug, they will lock the entire table until the operation is complete. Locking for write also blocks reads until the write is - complete. The - <quote>shadowdb</quote> + complete. Note that more recent versions of mysql support row level + locking using different table types. These types are slower than the + standard type, and Bugzilla does not yet take advantage of features + such as transactions which would justify this speed decrease. The + Bugzilla team are, however, happy to hear about any experiences with + row level locking and Bugzilla</para> + + <para>The <quote>shadowdb</quote> parameter was designed to get around this limitation. While only a single user is allowed to write to a table at a time, reads can continue unimpeded on a read-only shadow copy of the database. @@ -85,23 +91,10 @@ Bugzilla bug changes and comments per day.</para> <para>The value of the parameter defines the name of the - shadow bug database. - Set "shadowdb" to e.g. "bug_shadowdb" if you will be running a - *very* large installation of Bugzilla. - <note> - <para>Enabling "shadowdb" can adversely affect the stability of - your installation of Bugzilla. You should regularly check that your - database is in sync. It is often advisable to force a shadow - database sync nightly via - <quote>cron</quote>. - </para> - </note> - </para> - - <para>If you use the "shadowdb" option, it is only natural that you - should turn the "queryagainstshadowdb" option on as well. Otherwise - you are replicating data into a shadow database for no reason!</para> - + shadow bug database. You will need to set the host and port settings + from the params page, and set up replication in your database server + so that updates reach this readonly mirror. Consult your database + documentation for more detail.</para> </step> <step> diff --git a/docs/xml/database.xml b/docs/xml/database.xml index ae1918207..d32bb57cc 100644 --- a/docs/xml/database.xml +++ b/docs/xml/database.xml @@ -198,7 +198,6 @@ | products | | profiles | | profiles_activity | -| shadowlog | | tokens | | versions | | votes | @@ -290,10 +289,6 @@ sshh... don't tell your users!) profiles_activity: Need to know who did what when to who's profile? This'll tell you, it's a pretty complete history. -shadowlog: I could be mistaken here, but I believe this table tells you when -your shadow database is updated and what commands were used to update it. We -don't use a shadow database at our site yet, so it's pretty empty for us. - versions: Version information for every product votes: Who voted for what when diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml index 8d1a94ec7..7aec021ce 100644 --- a/docs/xml/installation.xml +++ b/docs/xml/installation.xml @@ -559,9 +559,7 @@ AllowOverride Limit <para>There are important files and directories that should not be a served by the HTTP server - most files in the <quote>data</quote> - and - <quote>shadow</quote> - directories and the + directory and the <quote>localconfig</quote> file. You should configure your HTTP server to not serve these files. Failure to do so will expose critical passwords and |