hazelcast-kubernetes | Kubernetes Discovery for Hazelcast | Continuous Deployment library

by hazelcast Java Version: 2.2.3 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(6)Vulnerabilities Install Support

kandi X-RAY | hazelcast-kubernetes Summary

hazelcast-kubernetes is a Java library typically used in Devops, Continuous Deployment, Docker applications. hazelcast-kubernetes has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

This repository contains a plugin which provides the automatic Hazelcast member discovery in the Kubernetes environment. You can use it in your project deployed on Kubernetes in order to make the embedded Hazelcast members discover each other automatically. This plugin is also included in Hazelcast Docker images, Hazelcast Helm Charts, and Hazelcast OpenShift Docker image.

Support

Quality

Security

License

Reuse

Support

hazelcast-kubernetes has a low active ecosystem.

It has 170 star(s) with 103 fork(s). There are 58 watchers for this library.

It had no major release in the last 12 months.

There are 20 open issues and 139 have been closed. On average issues are closed in 61 days. There are 9 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of hazelcast-kubernetes is 2.2.3

Quality

hazelcast-kubernetes has 0 bugs and 0 code smells.

Security

hazelcast-kubernetes has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

hazelcast-kubernetes code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

hazelcast-kubernetes is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

hazelcast-kubernetes releases are available to install and integrate.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

hazelcast-kubernetes saves you 1531 person hours of effort in developing the same functionality from scratch.

It has 3401 lines of code, 226 functions and 24 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed hazelcast-kubernetes and discovered the below as its top functions. This is intended to give you an instant insight into hazelcast-kubernetes implemented functionality, and help decide if they suit your requirements.

Resolves the local endpoints
Extracts nodes from a list of endpoints
Make a request
Adds public IPs to the list of public IPs
Resolves the service
Lookup a list of nodes
Validates the configuration
Retrieves the namespace from the system properties or fallback if not set

Get all kandi verified functions for this library.

hazelcast-kubernetes Key Features

No Key Features are available at this moment for hazelcast-kubernetes.

hazelcast-kubernetes Examples and Code Snippets

No Code Snippets are available at this moment for hazelcast-kubernetes.

Community Discussions

Trending Discussions on hazelcast-kubernetes

Hazelcast Scheduled Executor always starts task on newest member

Hazelcast embedded cache printing too many logs( Target is this node! -> [10.1.8.58]:5701","stack_trace":"<#d3566be0> j.l.IllegalArgumentException...)

How to change quarkus-vertx eventBus ClusterManager options

Error creating mongock bean when deploying on docker

Hazelcast Kubernetes Warning Unknown Protocol

hazelcast-kubernetes Unable to start Embedded server

QUESTION

Hazelcast Scheduled Executor always starts task on newest member

Asked 2021-Sep-17 at 12:42

I am using Hazelcast Scheduled Executor Service in order to run a specific task, on one service instance only. In order to achieve this behavior we take advantage of com.hazelcast.scheduledexecutor.TaskUtils.named(java.lang.String, java.lang.Runnable) decorator to avoid duplicate tasks.

Hazelcast dependencies used:

...

ANSWER

Answered 2021-Aug-26 at 10:30

This is not directly possible, but there is an approximation.

IScheduledExecutorService does not provide a method to provide an ordering for which members to use.

You can submit a task to a specific member, but this won't failover to a member of your choosing if the original specific member dies.
... various other options ...
Or the option in your code, scheduleAtFixedRate which will pick a member, and this may be a different member each time the cluster changes size. It should not always be the newest unless by co-incidence.

What you could do is have a scheduled task that selects a member to run an ordinary task upon. One task that launches another.

In the scheduled task, the run() could call hazelcastInstance.getCluster().getMembers() to get the list of members in the cluster. All it needs is some logic to pick a member, and then do hazelcastInstance.getExecutorService("default").executeOnMember(runnable, member).

You might pick a member with a specific attribute that you configure. Or a member with a specific IP. Perhaps simplest is to pick the oldest, since this doesn't change until the oldest leaves, in which case 2nd olest is now oldest, easy failover.

Source https://stackoverflow.com/questions/68927406

QUESTION

Hazelcast embedded cache printing too many logs( Target is this node! -> [10.1.8.58]:5701","stack_trace":"<#d3566be0> j.l.IllegalArgumentException...)

Asked 2021-Jun-07 at 07:29

I have a spring boot 2.5 application with spring spring security 5 where I am using embedded hazelcast cache to back spring sessions. This application is deployed on openshift with two pods where same application is running, hence I have used hazelcast kubernetes plugin for service discovery. Everything is working as expected. However, I can see application logs are flooded with below log lines. Any suggestion what is wrong with the hazelcast configuration ? Why so many log lines are generated ?

Generated logs

10.1.8.58 is IP address of second pod which joined cluster later and logs are printed in this pod only.

...

ANSWER

Answered 2021-Jun-07 at 07:29

The exception you get SplitBrainMergeValidationOp means that the Hazelcast cluster might have been started in the split-brain and later tries to merge into one cluster. Could you check if you follow all the Hazelcast Kubernetes recommendations?

Especially, check if you use StatefulSet (not Deployment). In the case of DNS Lookup discovery, using Deployment may cause Hazelcast to start in the split-brain mode.

Source https://stackoverflow.com/questions/67818834

QUESTION

How to change quarkus-vertx eventBus ClusterManager options

Asked 2021-Mar-29 at 08:15

I want to configure vertx at k8s by using hazelcast-kubernetes in Quarkus.

I need configure event-bus like this:

...

ANSWER

Answered 2021-Mar-29 at 08:15

I don't believe you can configure VertxOptions from code.

You could put a cluster.xml Hazelcast configuration file in the classpath instead.

Note that the Vert.x cluster managers are not supported in Quarkus yet. You can make them work in JVM mode (see this attempt with Infinispan) but not in native mode.

Source https://stackoverflow.com/questions/66842374

QUESTION

Error creating mongock bean when deploying on docker

Asked 2021-Mar-14 at 22:30

I am using Mongck to migrate data in my Spring Boot application. Spring Boot application runs perfectly locally. But when running on docker, the following error occurs:

...

ANSWER

Answered 2021-Mar-14 at 22:30

As discussed in this Github issue, the issue was resolved by upgrading to version 4.3.7.

Source https://stackoverflow.com/questions/66610729

QUESTION

Hazelcast Kubernetes Warning Unknown Protocol

Asked 2020-Oct-19 at 09:08

I was using Zookeeper Hazelcast discovery but now i have changed it to Hazelcast-Kubernetes. It seems it is working fine but some times it prints warning message like :

...

ANSWER

Answered 2020-Oct-19 at 09:08

There is a similar issue report in this GH Issue. As described there, adding the following part might solve the issue:

Source https://stackoverflow.com/questions/64388790

QUESTION

hazelcast-kubernetes Unable to start Embedded server

Asked 2020-Mar-12 at 07:43

I'm trying to start a simple embedded hazelcast server in a spring boot application on kubernetes. I'm using hazelcast-kubernetes plugin and have followed the documentation here. I tried both LoadBalancer and NodePort service types.

I also tried to deploy the sample application using this example (using the same docker image) and tried both LoadBalancer and NodePort service types.

In both cases I get the below error after 10 retries to connect to Kubernetes Master. Where a.b.c.d is the IP address of the kubernetes master node.

...

ANSWER

Answered 2020-Mar-12 at 07:43

You seem to have an issue with your Kubernetes cluster itself.

First you try to use Hazelcast Kubernetes Discovery strategy Kubernetes API, which makes a REST call to Kubernetes master. Kubernetes master should be always accessible from your POD by the hostname kubernetes.default.svc. In your case, it's not found.
Then, you try to use Hazelcast Kubernetes Discovery strategy DNS Lookup, which uses service DNS to resolve Hazelcast members. In your case, as mentioned by @Mesut, it's not resolving correctly the DNS of a service.

Source https://stackoverflow.com/questions/60623499

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install hazelcast-kubernetes

Hazelcast cluster is easily scalable within Kubernetes. You can use the standard kubectl scale command to change the cluster size. The same applies the rolling upgrade procedure, you can depend on the standard Kubernetes behavior and just update the new version to your Deployment/StatefulSet configurations.
terminationGracePeriodSeconds: in your StatefulSet (or Deployment) configuration; the value should be high enough to cover the data migration process
-Dhazelcast.shutdownhook.policy=GRACEFUL: in the JVM parameters
-Dhazelcast.graceful.shutdown.max.wait: in the JVM parameters; the value should be high enough to cover the data migration process
If you use Deployment (not StatefulSet), you need to set your strategy to RollingUpdate and ensure Pods are updated one by one.
If you upgrade by the minor version, e.g., 3.11.4 => 3.12 (Enterprise feature), you need to set the following JVM property -Dhazelcast.cluster.version.auto.upgrade.enabled=true to make sure the cluster version updates automatically.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: