Administer > Smart Analytics administration > Administrator tasks > Work with Smart Search > Modify Smart Search content servers and weight for data

Modify Smart Search contents and weight for data distribution

User Role: Administrator

Smart Search uses consistent hashing for distribution of data. In consistent hashing mode, you can add, remove, or change the weight of child servers in your DIH without having to reindex all your content.

In this mode, DIH distributes documents among a large, fixed number of virtual nodes (4096), and then assigns these nodes to one or more child servers. When you change the number or weight of the child servers, you can use the DREREDISTRIBUTE index action to redistribute the virtual nodes between the new set of servers without reindexing all the data.

In consistent hashing mode, all content is distributed in virtual nodes, which the DIH assigns to one or more child servers. When you run the DREREDISTRIBUTE index action, DIH checks whether the child server architecture has changed. If there is a change, DIH automatically exports and indexes the content in virtual nodes to redistribute your data evenly between the available child servers.

You can check current Smart Search contents and their ratio of data (including the information of data weight and vnode) by sending an action to the Smart Search proxy DIH server (20080 by default):

Action example:

http://<Smart Search Host>:<dih port>/action=enginemanagement&engineaction=showstatus

To modify the Smart Search content servers and the weight for data distribution, use the EngineMangement&EngineAction=Edit action.

  • Change the weight of data distribution.

    Action example:

    http://<Smart Search Host>:<dih port>/action=EngineManagement&EngineAction=Edit&ID=2&Weight=2

  • Update only this content server (receives document updates but does not receive new documents):

    Action example:

    http://<Smart Search Host>:<dih port>/action=EngineManagement&EngineAction=Edit&ID=2&UpdateOnly=true

  • Disable this content server (mark it as offline):

    Note When a child server is disabled, the DIH continues to assign documents to it, and queue up index actions, but it does not attempt to send them until the child server is enabled again.

    Action example:

    http://<Smart Search Host>:<dih port>/action=EngineManagement&EngineAction=Edit&ID=2&Disabled=true