Skip to content

JNI Set RMM_LOG_LEVEL and RMM_LOG_ACTIVE_LEVEL to allow setting log level at compile time #19435

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

Draft
wants to merge 1 commit into
base: branch-25.08
Choose a base branch
from

Conversation

abellina
Copy link
Contributor

@abellina abellina commented Jul 18, 2025

We have confusion from the customer side when they look at logs and see ERRORs from our pinned memory pool, since it is using a pooled_memory_resource that when exhausted we handle gracefully (here's a report NVIDIA/spark-rapids#13131):

[2602819][08:08:45:815536][error ] [A][Stream 0x1][Upstream 1024B][FAILURE maximum pool size exceeded: Not enough room to grow, current/max/try size = 0.000000 B, 0.000000 B, 1024.000000 B]

The problem stems from us setting RMM_LOGGING_LEVEL in our cmake builds, but this is not getting propagated to RMM itself, somehow. I have been able to make this propagate, and silence the error @revans2 posted, but I am not 100% sure this is the right thing to do. Asking folks here for some help (@bdice) to check the CMakeLists change.

Description

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

…vel at compile time

Signed-off-by: Alessandro Bellina <[email protected]>
@abellina abellina requested a review from a team as a code owner July 18, 2025 19:00
Copy link

copy-pr-bot bot commented Jul 18, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions github-actions bot added CMake CMake build issue Java Affects Java cuDF API. labels Jul 18, 2025
@abellina abellina marked this pull request as draft July 18, 2025 19:01
@abellina abellina added Spark Functionality that helps Spark RAPIDS non-breaking Non-breaking change improvement Improvement / enhancement to an existing function labels Jul 18, 2025
@@ -141,6 +141,18 @@ if(USE_GDS)
endif()
endif()

# Set RMM logging level
set(RMM_LOGGING_LEVEL
Copy link
Contributor

Choose a reason for hiding this comment

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

@vyasr Is this the correct way to use rapids-logger? I discussed a bit with @abellina offline but I don't know the proper way to solve this problem.

Copy link
Contributor

@bdice bdice Jul 18, 2025

Choose a reason for hiding this comment

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

There's a related conversation here about what should be precompiled in RMM here: rapidsai/rmm#1983 (comment)

It feels like these two topics might be solvable in similar ways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMake CMake build issue improvement Improvement / enhancement to an existing function Java Affects Java cuDF API. non-breaking Non-breaking change Spark Functionality that helps Spark RAPIDS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants