Skip to content

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 2, 2025

Why I'm doing:

3.3.7-13.2 RELEASE (build 7afd807)
query_id:00000000-0000-0000-0000-000000000000, fragment_instance:00000000-0000-0000-0000-000000000000
tracker:process consumption: 77927381408
tracker:jemalloc_metadata consumption: 16657949088
tracker:jemalloc_fragmentation consumption: 4101717720
tracker:query_pool consumption: 2847840856
tracker:query_pool/connector_scan consumption: 0
tracker:load consumption: 0
tracker:metadata consumption: 1722083679
tracker:tablet_metadata consumption: 540785
tracker:rowset_metadata consumption: 0
tracker:segment_metadata consumption: 222142458
tracker:column_metadata consumption: 1499400436
tracker:tablet_schema consumption: 540785
tracker:segment_zonemap consumption: 152128800
tracker:short_key_index consumption: 59993257
tracker:column_zonemap_index consumption: 441565596
tracker:ordinal_index consumption: 410289224
tracker:bitmap_index consumption: 22144
tracker:bloom_filter_index consumption: 0
tracker:compaction consumption: 0
tracker:schema_change consumption: 0
tracker:column_pool consumption: 0
tracker:page_cache consumption: 40173793840
tracker:jit_cache consumption: 0
tracker:update consumption: 177860278
tracker:chunk_allocator consumption: 0
tracker:passthrough consumption: 0
tracker:clone consumption: 0
tracker:consistency consumption: 0
tracker:datacache consumption: 3439183569
tracker:replication consumption: 0
*** Aborted at 1756211321 (unix time) try "date -d @1756211321" if you are using GNU date ***
PC: @          0x625eb4f starrocks::lake::AsyncDeltaWriter::close()
*** SIGSEGV (@0x0) received by PID 982175 (TID 0x7fe3eae64700) from PID 0; stack trace: ***
    @     0x7fe6fec0620b __pthread_once_slow
    @          0x7bcd340 google::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*)
    @     0x7fe6fec0f630 (/usr/lib64/libpthread-2.17.so+0xf62f)
    @          0x625eb4f starrocks::lake::AsyncDeltaWriter::close()
    @          0x37339f9 starrocks::LakeTabletsChannel::abort()
    @          0x36dbfdb starrocks::LoadChannel::abort()
    @          0x36d7430 starrocks::LoadChannelMgr::cancel(brpc::Controller*, starrocks::PTabletWriterCancelRequest const&, starrocks::PTabletWriterCancelResult*, google::protobuf::Closure*)
    @          0x7e5a114 brpc::policy::ProcessRpcRequest(brpc::InputMessageBase*)
    @          0x7d864b7 brpc::ProcessInputMessage(void*)
    @          0x7d87835 brpc::InputMessenger::OnNewMessages(brpc::Socket*)
    @          0x7d75b2e brpc::Socket::ProcessEvent(void*)
    @          0x7d46bb2 bthread::TaskGroup::task_runner(long)
    @          0x7e9c041 bthread_make_fcontext

What I'm doing:

Fix async delta writer crash due to null pointer

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 4.0
    • 3.5
    • 3.4
    • 3.3

This is an automatic backport of pull request #62626 done by [Mergify](https://mergify.com).

Signed-off-by: xiangguangyxg <xiangguangyxg@gmail.com>
(cherry picked from commit ecc0382)

# Conflicts:
#	be/test/exprs/agg/agg_compressed_key_test.cpp
Copy link
Contributor Author

mergify bot commented Sep 2, 2025

Cherry-pick of ecc0382 has failed:

On branch mergify/bp/branch-3.3/pr-62626
Your branch is up to date with 'origin/branch-3.3'.

You are currently cherry-picking commit ecc0382e57.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   be/src/runtime/lake_tablets_channel.cpp
	modified:   be/test/runtime/lake_tablets_channel_test.cpp

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   be/test/exprs/agg/agg_compressed_key_test.cpp

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify bot added the conflicts label Sep 2, 2025
@wanpengfei-git wanpengfei-git enabled auto-merge (squash) September 2, 2025 09:24
@mergify mergify bot closed this Sep 2, 2025
auto-merge was automatically disabled September 2, 2025 09:24

Pull request was closed

Copy link
Contributor Author

mergify bot commented Sep 2, 2025

@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr

Copy link
Contributor Author

mergify bot commented Sep 2, 2025

🧪 CI Insights

Here's what we observed from your CI run for a9ed8a5.

🟢 All jobs passed!

But CI Insights is watching 👀

@xiangguangyxg xiangguangyxg reopened this Sep 2, 2025
@wanpengfei-git wanpengfei-git enabled auto-merge (squash) September 2, 2025 09:32
Signed-off-by: xiangguangyxg <xiangguangyxg@gmail.com>
Signed-off-by: xiangguangyxg <xiangguangyxg@gmail.com>
@wanpengfei-git wanpengfei-git merged commit 0ee9850 into branch-3.3 Sep 2, 2025
28 of 29 checks passed
@wanpengfei-git wanpengfei-git deleted the mergify/bp/branch-3.3/pr-62626 branch September 2, 2025 12:34
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.

2 participants