Announcement

Collapse
No announcement yet.

Have I reached the limit for searchindex?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • bira
    replied
    Dunno, Apache works well for us. Never had a problem with it. My moto is, don't fix it if it's not broken. And from Apache's standpoint, upgrading doesn't give me any added value beyond what I already have. I upgrade PHP & MySQL either because it has new functions/features or because of bug and security fixes. Since version 1.3.9 of Apache is extremely stable and secure, I don't see a need to go the extra mile and upgrade it

    Leave a comment:


  • George L
    replied
    Originally posted by bira
    no eva. It's 1.3.9 -- I'm too lazy to upgrade it. Too many changes needed


    maybe need something like www.apachetoolbox.com

    Leave a comment:


  • bira
    replied
    no eva. It's 1.3.9 -- I'm too lazy to upgrade it. Too many changes needed

    Leave a comment:


  • George L
    replied
    Originally posted by DVD Plaza
    That's quite an old version of Apache you've got there?
    probably meant 1.3.19 ?

    Leave a comment:


  • DVD Plaza
    replied
    That's quite an old version of Apache you've got there?

    Leave a comment:


  • bira
    replied
    just an update:

    reindexing took me a total of 4 hours and 20 minutes.

    The searchindex table now contains 14,499,799 entries.

    I really hope I won't have to do it again

    Leave a comment:


  • bira
    replied
    Code:
    Filesystem           1k-blocks      Used Available Use% Mounted on
    /dev/ida/c0d0p6         300273       480    284290   0% /tmp
    That's the state now.

    So freddie, after I finish reindexing, I won't have problems again - provided I don't run myisamchk on that table?

    Leave a comment:


  • bira
    replied
    some information on my server, I guess:

    dual pIII 800
    1gb sdram

    RedHat 6.1 (or 6.2?)
    Apache 1.3.9
    MySQL 3.23.44
    PHP 4.0.6

    Allowed search word lengh in vB: 3-15

    (3 is a prerequisite, since my BB is about Formula One, where BMW and BAR, for example, would be among the most commonly used words in search)

    Leave a comment:


  • Freddie Bingham
    replied
    Error 28 - you have ran out of space on the device that is holding the /tmp partition.

    Leave a comment:


  • bira
    started a topic Have I reached the limit for searchindex?

    Have I reached the limit for searchindex?

    Hi,

    My bb's database has 630,000 posts. The searchindex table has over 15 million rows.

    Today, I began getting mysql error e-mails suggesting the searchindex table is corrupt.

    I shut down mysql and ran myisamchk -r and got the following:

    - recovering (with sort) MyISAM-table '../var/bbdb/searchindex.MYI'
    Data records: 15499872
    - Fixing index 1
    myisamchk: Error writing file '/tmp/STky5jnY' (Errcode: 28)
    myisamchk: Error writing file '/tmp/STky5jnY' (Errcode: 28)
    myisamchk: error: 28 when fixing table
    MyISAM-table '../var/bbdb/searchindex.MYI' is not fixed because of errors
    Try fixing it by using the --safe-recover (-o) or the --force (-f) option
    So I am now reindexing search (after emptying). It is still running, and so far 30 minutes gone by. At the rate it's going, the full reindexing will take 2 hours.

    My question is: have I reached the limit?

    What should I do?

    Thanks,

    Bira
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X