Opscode
Home     Cookbooks     Blog     GitHub     Tickets 

Chef Indexer

The Chef Indexer listens to a Message Queue via Stomp for changes to Search Indexes. It then either creates or deletes entries in the index according to the information it is passed.

Search indexes changing!

We've got big plans for Search Indexing - and they likely include totally tossing out this implementation. It's very useful today, and you need to use it - just make sure that you are aware that sometime in the future we're going to replace it with something far cooler.

Table of Contents

Stomp

In order for the Indexer to run, it must be connected to a stomp server. If you followed the Installation instructions and built your Chef Server with our solo cookbooks, you have a simple ruby based stomp server running. Other alternatives include ActiveMQ and RabbitMQ

Ferret

The indexer is writing to Ferret indexes. We've seen issues with Ferret eating a lot of CPU if it's indexes disappear or become corrupted. If that happens to you, just remove the index and it will rebuild naturally.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Copyright © 2009 Opscode, Inc. All Rights Reserved.