Indexing performance with doc values (particularly with larger number of fields)

2014-03-23 Thread Alex at Ikanow 
This might be more of a Lucene question, but a quick google didn't throw up 
anything.

Has anyone done/seen any benchmarking on indexing performance (overhead) 
due to using doc values?

I often index quite large JSON objects, with many fields (eg 50), I'm 
trying to get a feel for whether I can just let all of them be doc values 
on the off chance I'll want to aggregate over them, or whether I need to 
pick beforehand which fields will support aggregation.

(A related question: presumably allowing a mix of doc values fields and 
"legacy" fields is a bad idea, because if you use doc values fields you 
want a low max heap so that the file cache has lots of memory available, 
whereas if you use the field cache you need a large heap - is that about 
right, or am i missing something?)

Thanks for any insight!

Alex
Ikanow

-- 
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/0361eda4-ab39-4536-b91a-ccb710921edd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Install issues with Kibana3 vs elasticsearch 0.19.11

2014-03-20 Thread Alex at Ikanow 
Never mind, I'm an idiot, it clearly mentions it needs 0.90.x in the README 
:(

On Wednesday, March 19, 2014 12:49:46 PM UTC-4, Alex at Ikanow wrote:
>
>
> I downloaded the latest Kibana3, popped it on a tomcat instance sharing 
> space with my elasticsearch (0.19.11) instance and tried to connect (both: 
> using an ssh tunnel to connect localhost:9200 back to the server, and 
> opening port 9200 in the firewall)
>
> In both cases, the browser makes a call to _nodes (eg returns 
> "{"ok":true,"cluster_name":"infinite-dev","nodes":{"Yup-Cmn0QwCrkYI6l7SdRw":{"name":"Firefrost","transport_address":"inet[/
> 10.113.42.186:9300]","hostname":"ip-10-113-42-186","http_address":"inet[/
> 10.113.42.186:9200]"}}}")
>
> and then returns the following error:
>
> TypeError: Cannot call method 'split' of undefined at 
> http://SERVER/kibana-3.0.0/app/app.js:22:11260<http://dev.ikanow.com/kibana-3.0.0/app/app.js>at
>  he (
> http:// 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>SERVER<http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:7:20041)
>  
> at Function.Yb (http:// <http://dev.ikanow.com/kibana-3.0.0/app/app.js>
> SERVER 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:7:7025)
>  
> at http:// 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>SERVER<http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:22:11204
>  
> at i (http:// 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>SERVER<http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:9:458)
>  
> at i (http:// 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>SERVER<http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:9:458)
>  
> at http:// 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>SERVER<http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:9:1014
>  
> at Object.f.$eval (http:// <http://dev.ikanow.com/kibana-3.0.0/app/app.js>
> SERVER 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:9:6963)
>  
> at Object.f.$digest (http://<http://dev.ikanow.com/kibana-3.0.0/app/app.js>
> SERVER 
> <http://dev.ikanow.com/kibana-3.0.0/app/app.js>/kibana-3.0.0/app/app.js:9:5755)
>  
> at Object.f.$apply (http://<http://dev.ikanow.com/kibana-3.0.0/app/app.js>
> SERVER <http://dev.ikanow.com/kibana-3.0.0/app/app.js>
> /kibana-3.0.0/app/app.js:9:7111) 
>
> I don't see any other calls back to elasticseach
>
> I couldn't find a statement anywhere of which versions Kibana3 is 
> compatible with - does it just need a later version (anyone know the 
> earliest with which it is compatible, out of curiosity; though I'm planning 
> to move to 1.0 anyway soon), or am I doing something wrong
>
> Thanks for any insight/help anyone can provide!
>
> Alex
>
>
>
>
>

-- 
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/c6a2f998-89a9-4794-bdf8-15d1dcd26aae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Install issues with Kibana3 vs elasticsearch 0.19.11

2014-03-19 Thread Alex at Ikanow 

I downloaded the latest Kibana3, popped it on a tomcat instance sharing 
space with my elasticsearch (0.19.11) instance and tried to connect (both: 
using an ssh tunnel to connect localhost:9200 back to the server, and 
opening port 9200 in the firewall)

In both cases, the browser makes a call to _nodes (eg returns 
"{"ok":true,"cluster_name":"infinite-dev","nodes":{"Yup-Cmn0QwCrkYI6l7SdRw":{"name":"Firefrost","transport_address":"inet[/10.113.42.186:9300]","hostname":"ip-10-113-42-186","http_address":"inet[/10.113.42.186:9200]"}}}")

and then returns the following error:

TypeError: Cannot call method 'split' of undefined at 
http://SERVER/kibana-3.0.0/app/app.js:22:11260at
 he (
http:// 
SERVER/kibana-3.0.0/app/app.js:7:20041)
 
at Function.Yb (http:// 
SERVER 
/kibana-3.0.0/app/app.js:7:7025) 
at http:// 
SERVER/kibana-3.0.0/app/app.js:22:11204
 
at i (http:// 
SERVER/kibana-3.0.0/app/app.js:9:458)
 
at i (http:// 
SERVER/kibana-3.0.0/app/app.js:9:458)
 
at http:// 
SERVER/kibana-3.0.0/app/app.js:9:1014
 
at Object.f.$eval (http:// 
SERVER 
/kibana-3.0.0/app/app.js:9:6963) 
at Object.f.$digest (http:// 
SERVER 
/kibana-3.0.0/app/app.js:9:5755) 
at Object.f.$apply (http:// 
SERVER 
/kibana-3.0.0/app/app.js:9:7111) 

I don't see any other calls back to elasticseach

I couldn't find a statement anywhere of which versions Kibana3 is 
compatible with - does it just need a later version (anyone know the 
earliest with which it is compatible, out of curiosity; though I'm planning 
to move to 1.0 anyway soon), or am I doing something wrong

Thanks for any insight/help anyone can provide!

Alex




-- 
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/ed77f1e7-547d-4c87-b23f-ee97dece9533%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.