Skip to content

[DSD-10347] 1.3.1 Packet Processing Performance Tuning release#320

Merged
Prafulrakhade merged 3 commits into
release-1.3.xfrom
releas-branch
Jun 1, 2026
Merged

[DSD-10347] 1.3.1 Packet Processing Performance Tuning release#320
Prafulrakhade merged 3 commits into
release-1.3.xfrom
releas-branch

Conversation

@ckm007
Copy link
Copy Markdown
Member

@ckm007 ckm007 commented Jun 1, 2026

Automated PR for release.

Summary by CodeRabbit

  • Chores
    • Bumped release to 1.3.1-rc.1 across deployment and packages.
    • Updated container image references to the release candidate version.
    • Expanded JVM and AWS SDK logging/metrics and adjusted runtime options for improved observability.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 1, 2026

Review Change Stack

Warning

Review limit reached

@Prafulrakhade, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 33 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 21dc4d86-b950-4a2c-a8ca-c086822801de

📥 Commits

Reviewing files that changed from the base of the PR and between 92d4d75 and 730b5bd.

📒 Files selected for processing (1)
  • commons-packet/commons-packet-manager/pom.xml

Walkthrough

This PR moves deployment and build artifacts from snapshot/develop to release candidate 1.3.1-rc.1: Helm chart and installer, Helm values (image tag and JVM options), and Maven project/module/dependency versions are updated accordingly.

Changes

Release Candidate 1.3.1-rc.1 Promotion

Layer / File(s) Summary
Chart version and deployment script alignment
helm/packetmanager/Chart.yaml, deploy/install.sh
Helm chart version and CHART_VERSION in the installer changed from 1.3.1-develop to 1.3.1-rc.1.
Container image and JVM options configuration
helm/packetmanager/values.yaml
image.repository and image.tag pinned to mosipid/commons-packet-service:1.3.1-rc.1; additionalResources.javaOpts consolidated and extended with AWS SDK metrics and detailed AWS logging properties.
Maven project and dependency version updates
commons-packet/pom.xml, commons-packet/commons-packet-service/pom.xml, commons-packet/commons-packet-manager/pom.xml
Project/module versions and several Maven property pins updated from -SNAPSHOT to -rc.1 (including kernel and khazana-related properties and packet manager versions).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A version hops from -develop to -rc.1,
Chart, script, and image now align as one,
JVM whispers metrics, AWS logs gleam bright,
A hushed release candidate readies for flight! 🚀

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title references a release candidate version (1.3.1-rc.1) and the primary changes across all files involve updating versions from SNAPSHOT to rc.1, which aligns with the main objective of the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Signed-off-by: Prafulrakhade <prafulrakhade02@gmail.com>
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@helm/packetmanager/values.yaml`:
- Around line 124-125: The javaOpts string currently enables TRACE logging for
the AWS SDK via the flags -Dlogging.level.com.amazonaws=TRACE,
-Dlogging.level.com.amazonaws.request=TRACE, and
-Dlogging.level.com.amazonaws.http=TRACE; change those three flags to a less
verbose level (e.g., INFO or DEBUG) appropriate for a release candidate and
remove any stray TRACE entries so the javaOpts value uses
-Dlogging.level.com.amazonaws=INFO (or DEBUG) and updates the corresponding
.request and .http flags to the same safer level to avoid excessive/sensitive
logging while preserving the rest of the JVM options.
- Around line 49-50: The values.yaml entry uses repository:
mosipid/commons-packet-service and tag: 1.3.1-rc.1 which 404s on Docker Hub; fix
by replacing the invalid tag with a published one (or the correct image name),
e.g. update tag to an existing tag or change repository to the correct
registry/repo:tag that contains the image; verify the chosen image exists on the
registry (Docker Hub or internal), update the values.yaml fields (repository
and/or tag) accordingly, and re-deploy (helm upgrade) once the image reference
is confirmed.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: eb0b3156-16c7-4abd-b568-c70cdc519f57

📥 Commits

Reviewing files that changed from the base of the PR and between 1c2c74c and a919afd.

📒 Files selected for processing (3)
  • deploy/install.sh
  • helm/packetmanager/Chart.yaml
  • helm/packetmanager/values.yaml

Comment thread helm/packetmanager/values.yaml
Comment thread helm/packetmanager/values.yaml
Signed-off-by: Prafulrakhade <prafulrakhade02@gmail.com>
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@commons-packet/commons-packet-manager/pom.xml`:
- Around line 32-40: The pom still uses a mutable SNAPSHOT for
kernel-keymanager-service.version; update the property
kernel-keymanager-service.version from 1.4.1-SNAPSHOT to the matching
non-SNAPSHOT RC value (e.g. 1.4.1-rc.1) so the release resolves immutable
artifacts, and scan the other pom properties to ensure no remaining SNAPSHOT
entries remain.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2b9a3ec5-8378-41b2-81cf-7a2c9f8a741c

📥 Commits

Reviewing files that changed from the base of the PR and between a919afd and 92d4d75.

📒 Files selected for processing (3)
  • commons-packet/commons-packet-manager/pom.xml
  • commons-packet/commons-packet-service/pom.xml
  • commons-packet/pom.xml

Comment thread commons-packet/commons-packet-manager/pom.xml
@Prafulrakhade Prafulrakhade merged commit f9ec198 into release-1.3.x Jun 1, 2026
13 checks passed
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

Successfully merging this pull request may close these issues.

2 participants