Hi Mark,
I don't get any errors in the logs.
Froma ES 1.4 node Kibana returns:
"*No results* There were no results because no indices were found that 
match your selected time span"

So for some reason Kibana can't find the index if I don't set an index 
alias.

"_aliases?pretty" output from ES1.4 where I manually set alias1,2,3 and 
that all I see
{
    "logstash-2015.03.20": {
        "aliases": {
            "alias3": {}
        }
    },
    "logstash-2015.03.19": {
        "aliases": {
            "alias1": {}
        }
    },
    "logstash-2015.03.18": {
        "aliases": {
            "alias2": {}
        }
    }
}




"_aliases?pretty" output from ES1.3 node (same cluster) and I see all 
indices
{
    "logstash-2015.03.17": {
        "aliases": {}
    },
    "logstash-2015.03.18": {
        "aliases": {
            "alias2": {}
        }
    },
    "logstash-2015.03.16": {
        "aliases": {}
    },
    "logstash-2015.03.19": {
        "aliases": {
            "alias1": {}
        }
    },
    "kibana-int": {
        "aliases": {}
    },
    "grafana-dash": {
        "aliases": {}
    },
    "logstash-2015.03.15": {
        "aliases": {}
    },
    "logstash-2015.03.20": {
        "aliases": {
            "alias3": {}
        }
    },
    "logstash-2015.03.14": {
        "aliases": {}
    },
    ".marvel-kibana": {
        "aliases": {}
    }
}


How can I trouble shoot this further?


Den fredag 20 mars 2015 kl. 07:04:24 UTC+1 skrev Mark Walkom:
>
> Can you provide the errors you are seeing?
>
> On 19 March 2015 at 17:20, Mathias Adler <[email protected] 
> <javascript:>> wrote:
>
>> Hi,
>> I just upgraded my four node ES cluster to 1.4.2. After restart I cant 
>> retrieve data using Kibana3 unless I manually creates an alias for each 
>> index? I still have one ES1.3.x left in the cluster where kibana works fine.
>>
>> If I run "_aliases?pretty " on an ES 1.4. node it returns "{}" only and 
>> kibana cant find any data.
>> If I run the same from a ES1.3.x node I get the following (same cluster):
>> {
>>     "logstash-2015.03.17": {
>>         "aliases": {}
>>     },
>>     "logstash-2015.03.18": {
>>         "aliases": {
>>         }
>>     },
>>     "logstash-2015.03.16": {
>>         "aliases": {}
>>
>> etc and Kibana works fine
>>
>> Any ideas?
>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/b2f7d7ee-4aa5-49d0-9c57-ac11a1924cf6%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/elasticsearch/b2f7d7ee-4aa5-49d0-9c57-ac11a1924cf6%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/7337667f-2bed-4411-84ef-22803f596aa3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to