are
discovered after changing elasticsearch.yml file .
But for load balancing of custom plugin invocation is there any built-in
plugin or elastic search feature available and it should also switch node
when one node goes down
Thanks,
Chetana
--
Please update your bookmarks! We have moved to https
I have to deploy ES version 0.90.10 on AWS. For that I have installed
cloud-aws plugin having the version 1.17.0-SNAPSHOT.
But I want to use *local* gateway instead of S3 gateway. I have
added/uncommented these 2 lines in elasticsearch.yml
cloud.aws.discovery.type: ec2
gateway.type: local
I
I am using index template to store metadata of my application. There are
many templates (including nested) created.
1. Is template a good idea for application metadata (not all are search
related) storage?
2. Does ES store template details in each node or like index data is it
possible to
I have a secondary index storage where I have both snapshot (taken from ES
server) and valid lucene index (content is same as snapshot). If ES server
index is cleared/deleted though the mapping is retained, could someone tell
me which is the better option to restore in terms of time taken:
a)
Could please suggest a best option for merging index data stored in HDFS
with the index data stored in ES node
On Saturday, May 31, 2014 1:45:13 AM UTC+5:30, Binh Ly wrote:
No I don't believe so. The snapshot data is not really a valid Lucene
index, per se. It does contain segment files, but
I have some index data stored in hdfs (ES compatible indexing) and rest in
ES and also ES and hdfs clusters are different. Is there any other better
alternative than below options
1. Bulk index request - but it is unnecessary as the data is already in
indexed format
2. Move/copy periodically
I have a requirment where for some data setting the '_source' in
indexrequest is strightforward but for some huge amount of data I need to
run long running activity to generate data which needs to be indexed. So
frequently I plan to take a snapshot from ES to Hadoop and want to add new
lucene
I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the
Tranpsort client of ES 1.1.1 and create mapping on Windows 2010. But I get
a 'No node available' exception on Ubantu 12.x
Here is the code I use for connecting to ES
ImmutableSettings.Builder settingsBuilder =
ES log shows this warning message, 'transport.netty- Message not fully read
(request) for [0] and action [], resetting'
On Wednesday, May 28, 2014 12:07:39 PM UTC+5:30, Chetana wrote:
I have ugraded ES from 0.90.2 to ES 1.1.1 recently. I am able to get the
Tranpsort client of ES 1.1.1
I want to create an index repo with multiple (3) shards and
use explict/custom _routing while indexing. I have a couple of questions,
can somebody please answer
1. If I explictly set _routing,
does ES take care of load balancing of index data,
indexrequest, search request
The call to prepareGetSnapshots(...) for getting a snapshot which is not
existing, throws SnapshotMissingException. But I expect instead it should
return response with a list of zero snapshots(getSnapshots()) or atleast
isExist=false
Is there any other way one can check the existence of a
I am using ES 1.1.1 and Hadoop hortonworks 2.2.2 and have installed the
plugin '*repository-hdfs'
(https://github.com/elasticsearch/elasticsearch-hadoop/tree/master/repository-hdfs
https://github.com/elasticsearch/elasticsearch-hadoop/tree/master/repository-hdfs)*
in
ES. I have created one
, make sure you properly configure log4j for your Hadoop
environment - it depends on what version you are
using and what libraries.
If the job is complete, you can always tests the results by querying ES
for the data that was just indexed.
On 4/28/14 9:20 AM, Chetana wrote:
I am using now
to upgrade
to their latest HDP (2.1) release.
Hope this helps,
[1] http://www.elasticsearch.org/overview/marvel/
[2]
http://www.elasticsearch.org/guide/en/elasticsearch/hadoop/current/logging.html
On 4/24/14 7:30 AM, Chetana wrote:
I am using elasticsearch-hadoop plugin (
https
I have downloaded elasticsearch-hadoop-1.2.0.jar from github and trying to
search. The code to search looks like
*
Configuration conf = new Configuration();
conf.set(es.nodes, localhost);
conf.set(es.port, 9200);
conf.set(es.resource, test_index/test_mapping);
conf.set(es.query,
We are developing an application which requires cascaded (flow based)
search where the search result of one will become the input criteria for
the next search.
Is there a way to do this in ES ? If not, can you suggest some third party
library which can provide cascading functionality over ES
Sorry it is alias not alice
On Friday, March 21, 2014 10:11:53 AM UTC+5:30, Chetana wrote:
I am planning to use elasticsearch (ES) for storing event logs. Per day,
the application should store nearly 3000+ events and size will be around
30-50K.
I need to take some statistics monthly
I am planning to use elasticsearch (ES) for storing event logs. Per day,
the application should store nearly 3000+ events and size will be around
30-50K.
I need to take some statistics monthly, half yearly, yearly also year
old data can be ignored sometimes but data should be retained for
I have indexed some records by making test_field to be 'analyzed'. If the
analyzed field causing this issue, is there any other facet type/work
around which can solve the problem?
On Tuesday, January 21, 2014 12:15:45 PM UTC+5:30, Chetana wrote:
I have an application where I need both
I am using the 'term facet' functionality of ElasticSearch 0.90.2 on a
paticular field (datatype). The field (datatype) stores one of the enum
values in camel case (example : sampleType). I am using a standard analyzer
for index and search which internally uses lowercase filter. The strange
I have observed this behavior on Ubantu 11.10 version.
On Wednesday, January 15, 2014 10:29:41 AM UTC+5:30, Chetana wrote:
I am using the 'term facet' functionality of ElasticSearch 0.90.2 on a
paticular field (datatype). The field (datatype) stores one of the enum
values in camel case
I have created a timestamp field (not be confused with _timestamp) and want
to sort timestamp field in descending order. But the result contains some
records out of order.
Mapping and the sorting criteria look like :
timestamp:{type
:date,format:dateOptionalTime,include_in_all:false}
My application has the pagination requirement for search. I am using the
offset and size option to achieve the pagination.
Making quick clicks on pagination sometimes does not give results at all.
Does the asynchronous search call bringing any side effects like this?
Thanks,
--
You
23 matches
Mail list logo
