I installed Solr on a separate server.
Solr stores something in a /data directory

root@ks201220:/home/solr# du -h data
884K    data/spellchecker1
12K     data/spellchecker
884K    data/spellchecker2
2.3M    data/index
4.1M    data

but the Mysql search* tables of the drupal site are also populated.

search_dataset     668      MyISAM   utf8_general_ci   1.2 MiB
search_index       76,038   MyISAM   utf8_general_ci   3.7 MiB
search_node_links  27       MyISAM   utf8_general_ci   4.2 KiB
search_total       11,666   MyISAM   utf8_general_ci   513.5 KiB

Thanks for helping me understand...

Comments

jpmckinney’s picture

jpmckinney commented
Status: Active » Fixed

Unless you disable core search, cron will populate the MySQL tables: http://www.drupalcoder.com/story/742-performance-tip-disable-drupals-cor...

jvieille’s picture

jvieille commented

Thanks for the directions ... should be in the module documentation!
I had to flush the tables manually though

For those looking for this information
- Drupal search indexing is no longer necessary with Solr
- but Drupal Search needs to be enabled for a smooth transition
- goto admin/settings/search
- INDEXING THROTTLE Number of items to index per cron run: 0
- Flush manually the search_* tables (PHPMyadmin for example)
TRUNCATE `search_dataset` ;
TRUNCATE `search_index` ;
TRUNCATE `search_node_links` ;
TRUNCATE `search_total` ;

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.