Skip to content
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

cloud_storage: Log client address in batch parser #14957

Conversation

abhijat
Copy link
Contributor

@abhijat abhijat commented Nov 14, 2023

The client address is added to the remote segment batch parser logs. The address cannot be set as a member because a remote segment reader may be cached and have its configuration reset. The client address is always read from the configuration to make sure we get the latest address.

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v23.2.x
  • v23.1.x
  • v22.3.x

Release Notes

  • none

@abhijat abhijat marked this pull request as ready for review November 14, 2023 06:57
andijcr
andijcr previously approved these changes Nov 14, 2023
Copy link
Contributor

@andijcr andijcr left a comment

Choose a reason for hiding this comment

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

lgtm

vlog(_ctxlog.debug, "remote_segment_batch_reader::stop");
vlog(
_ctxlog.debug,
"remote_segment_batch_reader::stop: {}",
Copy link
Contributor

Choose a reason for hiding this comment

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

minor nit, to have the same structure of the other logs

Suggested change
"remote_segment_batch_reader::stop: {}",
"[{}] remote_segment_batch_reader::stop",

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good point, fixed both

vlog(_ctxlog.debug, "remote_segment_batch_reader::stop - parser-close");
vlog(
_ctxlog.debug,
"remote_segment_batch_reader::stop - parser-close: {}",
Copy link
Contributor

Choose a reason for hiding this comment

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

nit, same as above

Suggested change
"remote_segment_batch_reader::stop - parser-close: {}",
"[{}] remote_segment_batch_reader::stop - parser-close",

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

@abhijat abhijat force-pushed the log-client-address-in-remote-batch-parser branch from 9b097b0 to f81ee32 Compare November 14, 2023 08:49
@abhijat abhijat requested a review from andijcr November 14, 2023 08:49
The client address is added to the remote segment batch parser logs. The
address cannot be set as a member because a remote segment reader may be
cached and have its configuration reset. The client address is always
read from the configuration to make sure we get the latest address.

(cherry picked from commit 0996d4f)
@piyushredpanda piyushredpanda merged commit 5dd38e6 into redpanda-data:dev Nov 14, 2023
14 of 17 checks passed
@vbotbuildovich
Copy link
Collaborator

/backport v23.2.x

@vbotbuildovich
Copy link
Collaborator

new failures in https://buildkite.com/redpanda/redpanda/builds/41078#018bcd30-f580-4166-93df-4c82eab37ae5:

"rptest.tests.partition_move_interruption_test.PartitionMoveInterruption.test_cancelling_partition_move.replication_factor=3.unclean_abort=True.recovery=restart_recovery.compacted=False"

@vbotbuildovich
Copy link
Collaborator

Copy link
Member

@dotnwat dotnwat left a comment

Choose a reason for hiding this comment

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

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants