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.

Sign up for GitHub

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

Jump to bottom

ICMP ing does not work for nodes in different boxes #211

Closed
gsbtech opened this issue Jul 17, 2012 · 1 comment
Closed

ICMP ing does not work for nodes in different boxes #211

gsbtech opened this issue Jul 17, 2012 · 1 comment
Labels
Type: Defect

Comments

@gsbtech
Copy link

gsbtech commented Jul 17, 2012

See

https://groups.google.com/forum/?fromgroups#!searchin/hazelcast/ping/hazelcast/q5gHdW5KuPM/BkO5ITcmmbAJ

Here you mentioned that timeout and number of hops could be configurable.
Will you commit to do it? Which version?

In current state, this advanced property does not serve well.
@mdogan
Copy link
Contributor

mdogan commented Jul 22, 2013

This feature is available in 2.x versions.

@mdogan mdogan closed this as completed Jul 22, 2013
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
Add rbac.yaml and related info message (hazelcast#211)
11a4931
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
@dependabot
Bump hashicorp/setup-terraform from v1 to v1.2.1 (hazelcast#211)
b95b08e 
Bumps [hashicorp/setup-terraform](https://github.com/hashicorp/setup-terraform) from v1 to v1.2.1.
- [Release notes](https://github.com/hashicorp/setup-terraform/releases)
- [Changelog](https://github.com/hashicorp/setup-terraform/blob/master/CHANGELOG.md)
- [Commits](hashicorp/setup-terraform@v1...d224448)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
devOpsHazelcast pushed a commit that referenced this issue Dec 20, 2023
@semihbkgr @actions-user
Explicit External IP check in Kubernetes Discovery Plugin [CN-296] (#211
e74f78d 
)

Import of #25324

**Original PR description:**

The problem is that it assumes the service has a type of LoadBalancer
first. If it cannot find ExternalIP there, it jumps into catch block,
assumes it has a NodePort kind, and determines ExternalIP according to
it.

The block needs to be improved in such way:
It needs to check the kind of the service, and use a specific method to
determine External IP.

Checklist:
- [x] Labels (`Team:`, `Type:`, `Source:`, `Module:`) and Milestone set
- [x] Label `Add to Release Notes` or `Not Release Notes content` set
- [x] Request reviewers if possible
- [ ] Send backports/forwardports if fix needs to be applied to
past/future releases

Imported changes:

- f63f7fa Explicit External IP check in
Kubernetes Discovery Plugin...

Closes #25324

Co-authored-by: semihbkgr <buyukgungorsemih@gmail.com>
GitOrigin-RevId: 2bb2877cfb1f876e9263616b64307ae3a1a386f8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mdogan @gsbtech