Development: Disable Eureka for single node setups

[bensofficial]

Checklist

General

• This is a small issue that I tested on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

See: #8693

Description

We need the same change as in #8693 also for the test servers, so that there are no misleading errors in the logs.

We added the configuration in the global docker configuration as this is not a special configuration option, but rather should be the default for single node docker setups.

Steps for Testing

1. Deploy to TS2 or TS4
2. Open the server logs in Grafana (https://grafana.gchq.ase.in.tum.de/d/uBBKO8qnk/nodes-detailed-view?orgId=1&refresh=10s&var-DS_PROMETHEUS=default&var-job=artemis_test&var-name=artemis-test4.artemis.cit.tum.de&var-node=artemis-test-vm4.artemis.cit.tum.de&var-port=9100) and select the server you have chosen.
3. Check that there are no errors like: DiscoveryClient_ARTEMIS/Artemis:1 - was unable to send heartbeat!

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.

Review Progress

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Summary by CodeRabbit

• New Features
  • Introduced a configuration file for single-node deployment of the Artemis service, optimizing it for standalone operation.
  • Adjusted settings to prevent the service from registering with the Eureka server and fetching the service registry, enhancing performance and reducing complexity.

[coderabbitai]

Walkthrough

The update introduces a new configuration file, prod-singlenode.env, for the Artemis service, optimizing it for a single-node deployment. This file disables service registration and registry fetching with the Eureka server, streamlining operations in standalone scenarios. By avoiding unnecessary network interactions, the configuration enhances performance and simplifies the service’s deployment, making it suitable for testing and specific production environments where service discovery is not required.

Changes

File Path	Change Summary
docker/artemis/config/prod-singlenode.env	Added configuration parameters: EUREKA_CLIENT_REGISTERWITHEUREKA=false, EUREKA_CLIENT_FETCHREGISTRY=false.

Sequence Diagram(s)

sequenceDiagram
    participant Service
    participant Eureka

    Service->>Eureka: Register Service (disabled)
    Service->>Eureka: Fetch Service Registry (disabled)
    Note over Service: Operates independently without registration or fetching

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[pzdr7]

Tested on TS4. Logs are no longer flooded with Eureka messages 👍

[Hialus]

Tested locally and it works 👍🏻

[iyannsch]

LGTM