Skip to content

Zen Discovery: Increase Ping timeouts #177

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

Closed
kimchy opened this issue May 16, 2010 · 1 comment
Closed

Zen Discovery: Increase Ping timeouts #177

kimchy opened this issue May 16, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented May 16, 2010

Change ping timeout to 30 seconds, and retries to 3. Note, this does not mean that 1.5 minutes will pass till a node will be detected as failed, since it also detects connection close.

@kimchy
Copy link
Member Author

kimchy commented May 16, 2010

Zen Discovery: Increase Ping timeouts, closed by ab57fa8.

dadoonet pushed a commit that referenced this issue Jun 5, 2015
Based on PR #178 by @paul-e-cooley. Thanks Paul!

In addition to:

```yaml
cloud:
    aws:
        protocol: https
        proxy_host: proxy1.company.com
        proxy_port: 8083
```

You can also set different proxies for `ec2` and `s3`:

```yaml
cloud:
    aws:
        s3:
            proxy_host: proxy1.company.com
            proxy_port: 8083
        ec2:
            proxy_host: proxy2.company.com
            proxy_port: 8083
```

PR rebased on master and lastest changes about component settings removal.
Documentation added.
Changes in tests. If a proxy is provided we run the tests, otherwise we ignore the test.

Closes #177.
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
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

1 participant