Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Boot-time Mapping Definitions #86

Closed
BubDZombie opened this issue Mar 24, 2010 · 3 comments
Closed

Boot-time Mapping Definitions #86

BubDZombie opened this issue Mar 24, 2010 · 3 comments

Comments

@BubDZombie
Copy link

Allow for mappings to be defined in a config file so that they will be pre-defined to the cluster when it starts up.

@kimchy
Copy link
Member

kimchy commented Mar 25, 2010

I am going to allow for mappings to be defined under the config/mappings location. Each mapping should be in its own file, and the file name should be [mappingName].json. For example, under config/mappings you will have person.json that will have the person mappings.

Also, note that the mappings must exists on all nodes/servers in the cluster.

@kimchy
Copy link
Member

kimchy commented Mar 25, 2010

Boot-time Mapping Definitions, closed by e5cd594.

@kimchy
Copy link
Member

kimchy commented Apr 9, 2010

Change the default location to config/mappings/_default, and also config/mappings/[index_name] can be used for specific indices.

dadoonet added a commit that referenced this issue Jun 5, 2015
When a Snapshot does not exist, we should raise a `SnapshotMissingException`.
Add also tests for GET/DELETE on non existing repo

Closes #86.

(cherry picked from commit 77ab672)
kblincoe added a commit to gwyneth-bassett/elasticsearch that referenced this issue Mar 21, 2017
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…elastic#86)

Only exec certbot if the certificates do not already exist

* This commit changes the rc.local on both the engageli and ems
instances so that it will only exec certbot when the certificates
do not already exist.  Executing certbot too many times leads to
a rate limit failure, and once created the certs are set to auto
renew on a schedule.  Reference:
https://community.letsencrypt.org/t/is-the-renew-timer-running-on-my-machine-as-it-is-supposed-to/118206

This commit is for https://engageli.atlassian.net/browse/MPC-1496
modified:   instance-files/ems/etc/rc.local
modified:   instance-files/engageli/etc/rc.local

Approved-by: Gideon Avida
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we raise the network timeout for all benchmarks
(regardless whether they have specified client options before or not)
from the previous default value of 60 seconds to 240 seconds. We have
seen some bulk requests fail with a network timeout in recent benchmarks
and hence we bump it so we don't skew results due to timeouts.

Relates elastic#86
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants