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

CI Failure (oversized allocation) in PartitionBalancerScaleTest.test_node_operations_at_scale #19981

Open
vbotbuildovich opened this issue Jun 24, 2024 · 1 comment
Labels
area/oversized-allocation auto-triaged used to know which issues have been opened from a CI job ci-failure

Comments

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Jun 24, 2024

https://buildkite.com/redpanda/vtools/builds/14990

Module: rptest.scale_tests.partition_balancer_scale_test
Class: PartitionBalancerScaleTest
Method: test_node_operations_at_scale
Arguments: {
    "type": "many_partitions"
}
test_id:    PartitionBalancerScaleTest.test_node_operations_at_scale
status:     FAIL
run time:   636.064 seconds

<BadLogLines nodes=ip-172-31-12-46(4) example="WARN  2024-06-24 00:38:18,671 [shard 1:main] seastar_memory - oversized allocation: 458752 bytes. This is non-fatal, but could lead to latency and/or fragmentation issues. Please report: at 0x85b04cb 0x829c82b 0x82a799f 0x8447f03 0x844e02f 0x8445ccf 0x83d9a13 0x8368497 0x83b0523 0x82ee0df /opt/redpanda/lib/libc.so.6+0x96797 /opt/redpanda/lib/libc.so.6+0x101b4b">
Traceback (most recent call last):
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 184, in _do_run
    data = self.run_test()
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/tests/runner_client.py", line 276, in run_test
    return self.test_context.function(self.test)
  File "/opt/.ducktape-venv/lib/python3.10/site-packages/ducktape/mark/_mark.py", line 535, in wrapper
    return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
  File "/home/ubuntu/redpanda/tests/rptest/services/cluster.py", line 190, in wrapped
    redpanda.raise_on_bad_logs(
  File "/home/ubuntu/redpanda/tests/rptest/services/redpanda.py", line 1570, in raise_on_bad_logs
    lsearcher.search_logs(_searchable_nodes)
  File "/home/ubuntu/redpanda/tests/rptest/services/utils.py", line 197, in search_logs
    raise BadLogLines(bad_loglines)
rptest.services.utils.BadLogLines: <BadLogLines nodes=ip-172-31-12-46(4) example="WARN  2024-06-24 00:38:18,671 [shard 1:main] seastar_memory - oversized allocation: 458752 bytes. This is non-fatal, but could lead to latency and/or fragmentation issues. Please report: at 0x85b04cb 0x829c82b 0x82a799f 0x8447f03 0x844e02f 0x8445ccf 0x83d9a13 0x8368497 0x83b0523 0x82ee0df /opt/redpanda/lib/libc.so.6+0x96797 /opt/redpanda/lib/libc.so.6+0x101b4b">

JIRA Link: CORE-4291

@vbotbuildovich vbotbuildovich added auto-triaged used to know which issues have been opened from a CI job ci-failure labels Jun 24, 2024
@michael-redpanda
Copy link
Contributor

Note: Need to grab build and decode stracktrace.

@michael-redpanda michael-redpanda changed the title CI Failure (key symptom) in PartitionBalancerScaleTest.test_node_operations_at_scale CI Failure (oversized allocation) in PartitionBalancerScaleTest.test_node_operations_at_scale Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/oversized-allocation auto-triaged used to know which issues have been opened from a CI job ci-failure
Projects
None yet
Development

No branches or pull requests

2 participants