Hi Team, I am planning to develop a Multi-tenet E-Commerce App on Elastic
Search. anyone on the same lines..
Suggestions and recommendations please..
--
Good to hear 
Do you have a specific question?
Otis
Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service
Search Analytics - Cloud Monitoring Tools & Services | Sematext
On Monday, November 19, 2012 11:21:26 AM UTC-5, Built-App-On-ES wrote:
Hi Team, I am planning to develop a Multi-tenet E-Commerce App on Elastic
Search. anyone on the same lines..Suggestions and recommendations please..
--
Hey thanks for the reply...for Multi tenant what is best practice.. create
multiple indexes or have client ID in the document
--
You may hate me for saying it, but: it depends.
Rough guidelines:
If there will be a lot of tenants, consider shared indices and routing.
If there will be a few tenants, consider separate indices.
Otis
Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service
Search Analytics - Cloud Monitoring Tools & Services | Sematext
On Monday, November 19, 2012 10:32:04 PM UTC-5, Built-App-On-ES wrote:
Hey thanks for the reply...for Multi tenant what is best practice.. create
multiple indexes or have client ID in the document
--
there will be a lot of tenants...will consider shared indices and routing
In terms of performance is it possible to place each shard in once
partition. i am planning this on AWS cloud and use EBS Volumes. if we
assign each shard a ebs will it help.
--
Hi,
Not sure off the top of my head.
However, you could also mount N EBS volumes, stripe them, and then you
don't have to worry so much about placing tenants on specific EBS volumes.
See the bottom of Compute – Amazon EC2 Instance Types – AWS
Otis
ELASTICSEARCH Performance Monitoring - Sematext Monitoring | Infrastructure Monitoring Service
Search Analytics - Cloud Monitoring Tools & Services | Sematext
On Tuesday, November 20, 2012 10:58:30 PM UTC-5, Built-App-On-ES wrote:
there will be a lot of tenants...will consider shared indices and routing
In terms of performance is it possible to place each shard in once
partition. i am planning this on AWS cloud and use EBS Volumes. if we
assign each shard a ebs will it help.
--
yes that was a good Idea..i am trying to adopt the best practices from
standard database implementations.
suggest me on this.
Store Shards on striped EBS Volumes with ZFS File System
Store Transaction logs in High IO EBS volumes for faster writes and updates.
Okk..My question is is it possible to store Transaction logs
in different partition or Path?
--
Hello,
One quick note inline:
On Wed, Nov 28, 2012 at 5:39 PM, Built-App-On-ES shaantheadmin@gmail.comwrote:
yes that was a good Idea..i am trying to adopt the best practices from
standard database implementations.suggest me on this.
Store Shards on striped EBS Volumes with ZFS File System
Store Transaction logs in High IO EBS volumes for faster writes and
updates.Okk..My question is is it possible to store Transaction logs
in different partition or Path?
While I don't know of a way to configure the path of your translog, I think
you can hack it if you need to. Since each shard has these three
directories:
$ ls $DATA_DIR/$CLUSTER_NAME/nodes/0/indices/$INDEX_NAME/$SHARD_NUMBER/
index/ _state/ translog/
I don't see why you couldn't just stop ES, mount the needed partition on
that directory, or make a symbolic link, then start ES again.
But I'd double-check to see if the translog is empty, and copy it to the
new location if it isn't. Otherwise, you might lose data.
Best regards,
Radu
http://sematext.com/ -- Elasticsearch -- Solr -- Lucene
--
Yes that is one of the possibility..
just checking if there is any configuration file or any other way of doing
it. this will be helpful if we are controlling the Nodes Dynamically in
case of adding more nodes and recovery.
--