Skip to content

HDDS-15486 Remove excessive debug logging in BlockOutputStream and Bu…#10439

Open
yandrey321 wants to merge 2 commits into
apache:masterfrom
yandrey321:HDDS-15486
Open

HDDS-15486 Remove excessive debug logging in BlockOutputStream and Bu…#10439
yandrey321 wants to merge 2 commits into
apache:masterfrom
yandrey321:HDDS-15486

Conversation

@yandrey321
Copy link
Copy Markdown
Contributor

Remove excessive debug logging in BlockOutputStream and BufferPool

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-15486

How was this patch tested?

Unit tests

releaser.start();
allocator.join();
assertEquals(toRelease, allocated.get());
assertTrue(logCapturer.getOutput().contains("Allocation needs to wait the pool is at capacity"));
Copy link
Copy Markdown
Contributor

@amaliujia amaliujia Jun 5, 2026

Choose a reason for hiding this comment

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

I think we are losing testing coverage if you remove this line.

We might be able to do the following above

assertTrue(pool.allocated.size() == pool.capacity)
allocated.set(pool.allocateBuffer(0));

However I am not completely sure.

To be safe, we can keep this type of verification. Other removals over LOG_DEBUG look ok.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'd avoid validation through log messages and prefer to do it via actual state check

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

there is a check if pool is full at the beginning of the function:
assertFull(pool);

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