Skip to content

Conversation

@morningman
Copy link
Contributor

bp #48280

Related to apache/doris-thirdparty#267
Fix potential coredump like:

```
1# PosixSignals::chained_handler(int, siginfo*, void*) [clone .part.0] in /usr/lib/jvm/java-17-openjdk-amd64/lib/server/libjvm.so
 2# JVM_handle_linux_signal in /usr/lib/jvm/java-17-openjdk-amd64/lib/server/libjvm.so
 3# 0x00007F40E3728520 in /lib/x86_64-linux-gnu/libc.so.6
 4# getLastTLSExceptionRootCause at /home/zcp/repo_center/doris_branch-3.0/doris/thirdparty/src/doris-thirdparty-hadoop-3.3.6.3-for-doris/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfs/jni_helper.c:866
 5# doris::io::hdfs_error[abi:cxx11]() in /mnt/hdd01/PERFORMANCE_ENV/be/lib/doris_be
 6# doris::io::HdfsFileWriter::append_hdfs_file(std::basic_string_view<char, std::char_traits<char> >) at /home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/fs/hdfs_file_writer.cpp:381
 7# doris::io::HdfsFileWriter::_flush_buffer() at /home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/fs/hdfs_file_writer.cpp:390
 8# doris::io::HdfsFileWriter::_close_impl() at /home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/fs/hdfs_file_writer.cpp:255
 9# doris::io::HdfsFileWriter::close(bool) at /home/zcp/repo_center/doris_branch-3.0/doris/be/src/io/fs/hdfs_file_writer.cpp:248
10# doris::vectorized::ParquetOutputStream::Close() at /home/zcp/repo_center/doris_branch-3.0/doris/be/src/vec/runtime/vparquet_transformer.cpp:84
11# doris::vectorized::ParquetOutputStream::~ParquetOutputStream() at /home/zcp/repo_center/doris_branch-3.0/doris/be/src/vec/runtime/vparquet_transformer.cpp:57
```
@Thearas
Copy link
Contributor

Thearas commented Feb 26, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@morningman
Copy link
Contributor Author

run buildall

@doris-robot
Copy link

TeamCity be ut coverage result:
Function Coverage: 36.59% (9635/26330)
Line Coverage: 28.20% (80010/283692)
Region Coverage: 26.82% (40981/152828)
Branch Coverage: 23.57% (20782/88166)
Coverage Report: http://coverage.selectdb-in.cc/coverage/f38a36b04df3f502ab321f9a100f44d50d761c51_f38a36b04df3f502ab321f9a100f44d50d761c51/report/index.html
Increment Report: http://coverage.selectdb-in.cc/coverage/f38a36b04df3f502ab321f9a100f44d50d761c51_f38a36b04df3f502ab321f9a100f44d50d761c51/increment_report/index.html

@morningman morningman merged commit 6da6168 into apache:branch-2.1 Feb 26, 2025
19 of 20 checks passed
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.

3 participants