indexes not appear in cluster dashboard

[crazyeva]

i have added "repFactor=auto" to each peer's indexes.conf and "rolling-restarted" them all
i have put into them some data which can be seen on searchhead
but they are still not there

[crazyeva]

after i "splunk restarted" them all, twice.
they showed up....

[adrianathome · Accepted solution]

The indexes will not show up until they receive some data. Are you sending data to the indexes?

[crazyeva]

|metadata type=sourcetypes index=idx-dn:
firstTime lastTime recentTime sourcetype totalCount type
1 1336071194 1342402517 1371955561 DNlog 1079499 sourcetypes

there are events in that index

[adrianathome]

You said that you are receiving events. Look at the events in your search head and verify the index of the events.

[crazyeva]

sorry i dont quite understand you. the index name is "idx-dn"

[adrianathome]

What is the index of the events that you are receiving?

[crazyeva]

inputs.conf and outputs.conf on FORWARDER:
[monitor:///DATA/DNlog/DN.log.*]
sourcetype = DNlog
index = IDX-DN
host = LogDB
disabled = false

[tcpout]
defaultGroup = Peer_Group
maxQueueSize = 500MB
[tcpout:Peer_Group]
autoLB = true
autoLBFrequency = 1
useACK = true
server = 172.16.40.98:9997, 172.16.40.99:9997, ......

indexes.conf on PEER-NODEs:
[IDX-DN]
repFactor = auto
coldPath = $SPLUNK_DB/idx-dn/colddb
homePath = $SPLUNK_DB/idx-dn/db
maxDataSize = auto_high_volume
thawedPath = $SPLUNK_DB/idx-dn/thaweddb

[adrianathome]

What is the value of index for the events that you are receiving? Could it be the default index? If so, you need to specify the index in the inputs.cont of your forwarder.

[crazyeva]

yes， i did，i can see data on searchhead