[chef] Re: Re: Re: chef-server-ctl reindex with nodes?

[Seth Falcon < >]

 writes:
> knife node list shows all the nodes, knife search node id:* lists only the
> 4 nodes that checked in (most of my nodes only check in overnight)
>
> knife search <insert_data_bag> id:* shows all data bag entries, and looking
> at the expander log, it definitely reindexed all of the data bag items.
>
> It is now 7 hours later, so i'm thinking it's done and just didn't reindex
> the nodes...

Indeed, 7 hours should be quite long enough :)

I just did the following experiment with a nightly build of Chef Server
in a vm:

1. Created a few nodes and roles using knife
2. chef-server-ctl stop chef-solr
3. Nuked the solr index:
   `sudo rm -rf /var/opt/chef-server/chef-solr/data/index`
4. chef-server-ctl start chef-solr
5. Created a node and a role using knife
6. Wait 60 sec and verify data created in #5 is searchable. Also
   verified that data created in #1 was not found in search
7. chef-server-ctl reindex
8. Verify all data in search

What you're seeing with missing node data could certainly be a bug. At
this point, I would suggest attempting another c-s-c reindex with a
careful eye on the logs of chef-expander, chef-solr, and erchef.

Can you verify that your node data is hitting the expander during
reindex?

Any crash logs in the erchef logs related in time to reindexing?

Errors or logs of chef-solr?

Also worth looking at rabbitmq logs -- although a problem seems unlikely
to be located there since some data types appear to get reindexed
properly and the queue doesn't know anything about the object types.

Anyhow, hope these suggestions help you track down some more info.

+ seth

-- 
Seth Falcon | Development Lead | Opscode | @sfalcon