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

JGroups: Upgrade to 2.10 (check sys proper preferIpX) #49

Closed
kimchy opened this issue Mar 2, 2010 · 1 comment
Closed

JGroups: Upgrade to 2.10 (check sys proper preferIpX) #49

kimchy opened this issue Mar 2, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 2, 2010

When upgrading to 2.10, check if we can remove the system property of preferIpv4. Consider simulating the logic for choosing first non loopback ip in es (for transport, http, and jgroups bind_addr)

@kimchy
Copy link
Member Author

kimchy commented Jun 29, 2010

not going to be added since the jgroups plugin was removed.

dadoonet added a commit that referenced this issue Jun 5, 2015
Based on issue #43, we want to support both notations:

* group name first
* group id if it does not work with group name

Closes #49.
johtani added a commit that referenced this issue Jun 5, 2015
dadoonet added a commit that referenced this issue Jun 5, 2015
This has been added in elasticsearch 2.0.0. See #8782

Wondering if this PR should be split in two parts:

* one that clean the code and which is portable to 1.4, 1.x and master
* one that simply add move() method for master branch

@imotov WDYT?

Closes #49.
dadoonet added a commit that referenced this issue Jun 5, 2015
GCE API have been updated to `v1-rev59-1.20.0`.

We now can depend only on:

```xml
<dependency>
  <groupId>com.google.apis</groupId>
  <artifactId>google-api-services-compute</artifactId>
  <version>v1-rev59-1.20.0</version>
</dependency>
```

It comes with all needed dependencies.

Closes #49.
(cherry picked from commit f95dc16)
(cherry picked from commit 4ee6c95)
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue May 24, 2018
The MasterService ensures that only one publication is in progress at once.
However, the Legislator also currently tracks the set of active publications so
that they can be cancelled quickly by the fault-detection mechanism. Today we
stop tracking a publication once it is committed, but in future we must track
the publication until it either times out or receives a response from every
node.

This change modifies the Legislator's publication-tracking mechanism to track
publications until they complete, and also enforces that that there is only a
single active publication.
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we leverage new functionality in Rally to spin up a
cluster before all challenges are executed. This allows us to run
challenges which depend on others (e.g. query only challenges that rely
on another challenge to actually put the data into the cluster).

Closes elastic#49
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
As described in elastic/rally#450 Rally
needs to support java-10 to be able to compile Elasticsearch from
source.

Change the ini file to reflect the java-10 path and use the new
java10.home parameter (and also bump the config version number).

This depends on elastic/rally#451 and should
be merge only after the former has merged.

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

No branches or pull requests

1 participant