Re: [Discuss] About Doris Improvement Proposals

[Willem Jiang]

+1 for this DIP to collect the improvement proposals.
My suggestion is create a subdirectory for the DIP to hold all the DIPs.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Mar 10, 2022 at 1:25 PM 陈明雨  wrote:
>
> Hi All:
> I would like to start using "Doris Improvement Proposals(DSIP)" to save all 
> design doc of major features of Doris.
> The motivation of DSIP and details can be found here[1].
>
>
> Please feel free to discuss.
>
>
> [1] 
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org
For additional commands, e-mail: dev-h...@doris.apache.org

Re: [Discuss] About Doris Improvement Proposals

[ling miao]

+ 1 agree with DIP.
The DIP is unified in the wiki directory, which is convenient for
management and community people can quickly participate.

Ling Miao

Willem Jiang  于2022年3月10日周四 16:21写道：

> +1 for this DIP to collect the improvement proposals.
> My suggestion is create a subdirectory for the DIP to hold all the DIPs.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Mar 10, 2022 at 1:25 PM 陈明雨  wrote:
> >
> > Hi All:
> > I would like to start using "Doris Improvement Proposals(DSIP)" to save
> all design doc of major features of Doris.
> > The motivation of DSIP and details can be found here[1].
> >
> >
> > Please feel free to discuss.
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> >
> >
> >
> > --
> >
> > 此致！Best Regards
> > 陈明雨 Mingyu Chen
> >
> > Email:
> > chenmin...@apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org
> For additional commands, e-mail: dev-h...@doris.apache.org
>
>

[Volunteer recruitment] Open source the P0 test

[ling miao]

At present, the new testing framework of Doris has been integrated into the
community.
We hope to recruit a volunteer to help us open source the P0 level tests.
Purpose:
1. Contributors can pre-test P0 through thread scripts and casts before
submitting code.
2. When the P0 pipeline fails, the failed cast can be reproduced locally
and corrected by itself.

If anyone is interested, please reply to the email~

How to use the test framework [1]

Ling Miao

[1]
https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5

Re: [Volunteer recruitment] Open source the P0 test

[ling miao]

Sorry for the Misspell

At present, the new testing framework of Doris has been integrated into the
community.
We hope to recruit a volunteer to help us open source the P0 level tests.
Purpose:
1. Contributors can pre-test P0 cases through scripts before submitting
code.
2. When the P0 pipeline fails, the failed case can be reproduced locally
and corrected by itself.

If anyone is interested, please reply to the email~

How to use the test framework [1]

Ling Miao

[1]
https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5

ling miao  于2022年3月10日周四 17:04写道：

> At present, the new testing framework of Doris has been integrated into
> the community.
> We hope to recruit a volunteer to help us open source the P0 level tests.
> Purpose:
> 1. Contributors can pre-test P0 through thread scripts and casts before
> submitting code.
> 2. When the P0 pipeline fails, the failed cast can be reproduced locally
> and corrected by itself.
>
> If anyone is interested, please reply to the email~
>
> How to use the test framework [1]
>
> Ling Miao
>
> [1]
> https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5
>
>
>

?????? [Discuss] About Doris Improvement Proposals

[41108453]

+1


This is a very good way to facilitate community member participation and 
community management




--  --
??: 
   "dev"

https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> >
> >
> >
> > --
> >
> > ??Best Regards
> > ?? Mingyu Chen
> >
> > Email:
> > chenmin...@apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org
> For additional commands, e-mail: dev-h...@doris.apache.org
>
>

??????[Discuss] About Doris Improvement Proposals

[luzhijing]

+1 




--  --
??: 
   "dev"
https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals



--

??Best Regards
?? Mingyu Chen

Email:
chenmin...@apache.org

Re:Re: [Volunteer recruitment] Open source the P0 test

[陈明雨]

This P0 test is currently belongs to Baidu, inc.
We may need some internal discussion about.
But IMO, P0 is a good start to improve our regression test cases.



--

此致！Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





At 2022-03-10 17:08:44, "ling miao"  wrote:
>Sorry for the Misspell
>
>At present, the new testing framework of Doris has been integrated into the
>community.
>We hope to recruit a volunteer to help us open source the P0 level tests.
>Purpose:
>1. Contributors can pre-test P0 cases through scripts before submitting
>code.
>2. When the P0 pipeline fails, the failed case can be reproduced locally
>and corrected by itself.
>
>If anyone is interested, please reply to the email~
>
>How to use the test framework [1]
>
>Ling Miao
>
>[1]
>https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5
>
>ling miao  于2022年3月10日周四 17:04写道：
>
>> At present, the new testing framework of Doris has been integrated into
>> the community.
>> We hope to recruit a volunteer to help us open source the P0 level tests.
>> Purpose:
>> 1. Contributors can pre-test P0 through thread scripts and casts before
>> submitting code.
>> 2. When the P0 pipeline fails, the failed cast can be reproduced locally
>> and corrected by itself.
>>
>> If anyone is interested, please reply to the email~
>>
>> How to use the test framework [1]
>>
>> Ling Miao
>>
>> [1]
>> https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5
>>
>>
>>

Re: Re: [Volunteer recruitment] Open source the P0 test

[ling miao]

> We may need some internal discussion about.
OK

BTW, Looking forward to the first step in improving stability after P0 is
open sourced.

Volunteer Recruitment Closed

Ling Miao

陈明雨  于2022年3月10日周四 18:33写道：

> This P0 test is currently belongs to Baidu, inc.
> We may need some internal discussion about.
> But IMO, P0 is a good start to improve our regression test cases.
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org
>
>
>
>
>
> At 2022-03-10 17:08:44, "ling miao"  wrote:
> >Sorry for the Misspell
> >
> >At present, the new testing framework of Doris has been integrated into
> the
> >community.
> >We hope to recruit a volunteer to help us open source the P0 level tests.
> >Purpose:
> >1. Contributors can pre-test P0 cases through scripts before submitting
> >code.
> >2. When the P0 pipeline fails, the failed case can be reproduced locally
> >and corrected by itself.
> >
> >If anyone is interested, please reply to the email~
> >
> >How to use the test framework [1]
> >
> >Ling Miao
> >
> >[1]
> >
> https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5
> >
> >ling miao  于2022年3月10日周四 17:04写道：
> >
> >> At present, the new testing framework of Doris has been integrated into
> >> the community.
> >> We hope to recruit a volunteer to help us open source the P0 level
> tests.
> >> Purpose:
> >> 1. Contributors can pre-test P0 through thread scripts and casts before
> >> submitting code.
> >> 2. When the P0 pipeline fails, the failed cast can be reproduced locally
> >> and corrected by itself.
> >>
> >> If anyone is interested, please reply to the email~
> >>
> >> How to use the test framework [1]
> >>
> >> Ling Miao
> >>
> >> [1]
> >>
> https://doris.apache.org/zh-CN/developer-guide/regression-testing.html#%E6%A6%82%E5%BF%B5
> >>
> >>
> >>
>

Re: [Discuss] About Doris Improvement Proposals

[OpenInx]

> Probably most of the current Doris development comes from China, so we do
not refuse to use Chinese to write DSIP, because when describing some
complex content, it may be
> easier to express clearly in Chinese.
> For DSIPs written in Chinese, Doris PMC members will assist with English
translation when appropriate.

Although Apache Doris was born from China and its core contributors come
from China, I still don't think it's reasonable to accept any technical
design document which is not written in English.  Indeed,  it may be easier
to express technical details clearly in Chinese for people from China,  but
it also implies:  it will be harder to understand & get the points for a
non-Chinese speaker.  I believe this is not good for growing the diversity
of the Apache project , according to my several apache experience.

In general,  I will suggest accepting the standard English technical design
document in the apache doris community, so that everyone from everywhere
can discuss, understand, comment, share their thoughts.


On Thu, Mar 10, 2022 at 5:27 PM luzhijing <543881...@qq.com.invalid> wrote:

> +1 
>
>
>
>
> -- 原始邮件 --
> 发件人:
>   "dev"
> <
> morning...@163.com>;
> 发送时间: 2022年3月10日(星期四) 中午1:25
> 收件人: "doris-dev"
> 主题: [Discuss] About Doris Improvement Proposals
>
>
>
> Hi All:
> I would like to start using "Doris Improvement Proposals(DSIP)" to save
> all design doc of major features of Doris.
> The motivation of DSIP and details can be found here[1].
>
>
> Please feel free to discuss.
>
>
> [1]
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org

Re: [Discuss] About Doris Improvement Proposals

[OpenInx]

Besides,   the wiki page from apache org is a good place to share the
design idea,  but it is not a perfect tool for others to comment and
discuss.  we cannot just select the specific line to share the
thoughts from reviewers.  In general,  the wiki page is friendly for
writers but it's not for reviewers.  The google document is a perfect tool
in my mind for both writers and reviewers.  Let me take an example document
[1] from apache iceberg community.  In this page, we can see a lot of
interaction like questions and replies.  That's really helpful for the
authors & reviewers to exchange their thoughts.  So I will recommend
adopting the google document, and we can create a page (in wiki page or
apache doris official document page) to collect all those google design
documents.

[1].
https://docs.google.com/document/d/1bN6rdLNcYOHnT3xVBfB33BoiPO06aKBo56SZmuU9pnY/edit

On Thu, Mar 10, 2022 at 8:54 PM OpenInx  wrote:

> > Probably most of the current Doris development comes from China, so we
> do not refuse to use Chinese to write DSIP, because when describing some
> complex content, it may be
> > easier to express clearly in Chinese.
> > For DSIPs written in Chinese, Doris PMC members will assist with English
> translation when appropriate.
>
> Although Apache Doris was born from China and its core contributors come
> from China, I still don't think it's reasonable to accept any technical
> design document which is not written in English.  Indeed,  it may be easier
> to express technical details clearly in Chinese for people from China,  but
> it also implies:  it will be harder to understand & get the points for a
> non-Chinese speaker.  I believe this is not good for growing the diversity
> of the Apache project , according to my several apache experience.
>
> In general,  I will suggest accepting the standard English technical
> design document in the apache doris community, so that everyone from
> everywhere can discuss, understand, comment, share their thoughts.
>
>
> On Thu, Mar 10, 2022 at 5:27 PM luzhijing <543881...@qq.com.invalid>
> wrote:
>
>> +1 
>>
>>
>>
>>
>> -- 原始邮件 --
>> 发件人:
>>   "dev"
>> <
>> morning...@163.com>;
>> 发送时间: 2022年3月10日(星期四) 中午1:25
>> 收件人: "doris-dev">
>> 主题: [Discuss] About Doris Improvement Proposals
>>
>>
>>
>> Hi All:
>> I would like to start using "Doris Improvement Proposals(DSIP)" to save
>> all design doc of major features of Doris.
>> The motivation of DSIP and details can be found here[1].
>>
>>
>> Please feel free to discuss.
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
>>
>>
>>
>> --
>>
>> 此致！Best Regards
>> 陈明雨 Mingyu Chen
>>
>> Email:
>> chenmin...@apache.org
>
>

Re:Re: [Discuss] About Doris Improvement Proposals

[陈明雨]

Thanks for you suggestions:
1. About language:
I agree that using Chinese exclusively will not promote diversity in the 
community. But I would like to have a lower threshold to help the Doris 
community quickly establish a mechanism for DSIP. This is equivalent to a cold 
start process. In the meantime, PMC members will help with the translation of 
the Chinese documentation.
Once the mechanism is up and running, we will promote full English 
documentation.


2. About Google Doc
That is great! 




--

此致！Best Regards
陈明雨 Mingyu Chen

Email:
morning...@163.com;
morningman@gmail.com





At 2022-03-10 21:08:53, "OpenInx"  wrote:
>Besides,   the wiki page from apache org is a good place to share the
>design idea,  but it is not a perfect tool for others to comment and
>discuss.  we cannot just select the specific line to share the
>thoughts from reviewers.  In general,  the wiki page is friendly for
>writers but it's not for reviewers.  The google document is a perfect tool
>in my mind for both writers and reviewers.  Let me take an example document
>[1] from apache iceberg community.  In this page, we can see a lot of
>interaction like questions and replies.  That's really helpful for the
>authors & reviewers to exchange their thoughts.  So I will recommend
>adopting the google document, and we can create a page (in wiki page or
>apache doris official document page) to collect all those google design
>documents.
>
>[1].
>https://docs.google.com/document/d/1bN6rdLNcYOHnT3xVBfB33BoiPO06aKBo56SZmuU9pnY/edit
>
>On Thu, Mar 10, 2022 at 8:54 PM OpenInx  wrote:
>
>> > Probably most of the current Doris development comes from China, so we
>> do not refuse to use Chinese to write DSIP, because when describing some
>> complex content, it may be
>> > easier to express clearly in Chinese.
>> > For DSIPs written in Chinese, Doris PMC members will assist with English
>> translation when appropriate.
>>
>> Although Apache Doris was born from China and its core contributors come
>> from China, I still don't think it's reasonable to accept any technical
>> design document which is not written in English.  Indeed,  it may be easier
>> to express technical details clearly in Chinese for people from China,  but
>> it also implies:  it will be harder to understand & get the points for a
>> non-Chinese speaker.  I believe this is not good for growing the diversity
>> of the Apache project , according to my several apache experience.
>>
>> In general,  I will suggest accepting the standard English technical
>> design document in the apache doris community, so that everyone from
>> everywhere can discuss, understand, comment, share their thoughts.
>>
>>
>> On Thu, Mar 10, 2022 at 5:27 PM luzhijing <543881...@qq.com.invalid>
>> wrote:
>>
>>> +1 
>>>
>>>
>>>
>>>
>>> -- 原始邮件 --
>>> 发件人:
>>>   "dev"
>>> <
>>> morning...@163.com>;
>>> 发送时间: 2022年3月10日(星期四) 中午1:25
>>> 收件人: "doris-dev">>
>>> 主题: [Discuss] About Doris Improvement Proposals
>>>
>>>
>>>
>>> Hi All:
>>> I would like to start using "Doris Improvement Proposals(DSIP)" to save
>>> all design doc of major features of Doris.
>>> The motivation of DSIP and details can be found here[1].
>>>
>>>
>>> Please feel free to discuss.
>>>
>>>
>>> [1]
>>> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
>>>
>>>
>>>
>>> --
>>>
>>> 此致！Best Regards
>>> 陈明雨 Mingyu Chen
>>>
>>> Email:
>>> chenmin...@apache.org
>>
>>

Re: [Discuss] About Doris Improvement Proposals

[Willem Jiang]

It's great to compose the design document and review the document with
google doc.
My suggestion is once we finish the review process it is better to use
ASF wiki to host these documentation.
Because some people may have some trouble to access the google doc.

Just my 2 cents.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Mar 10, 2022 at 9:09 PM OpenInx  wrote:
>
> Besides,   the wiki page from apache org is a good place to share the
> design idea,  but it is not a perfect tool for others to comment and
> discuss.  we cannot just select the specific line to share the
> thoughts from reviewers.  In general,  the wiki page is friendly for
> writers but it's not for reviewers.  The google document is a perfect tool
> in my mind for both writers and reviewers.  Let me take an example document
> [1] from apache iceberg community.  In this page, we can see a lot of
> interaction like questions and replies.  That's really helpful for the
> authors & reviewers to exchange their thoughts.  So I will recommend
> adopting the google document, and we can create a page (in wiki page or
> apache doris official document page) to collect all those google design
> documents.
>
> [1].
> https://docs.google.com/document/d/1bN6rdLNcYOHnT3xVBfB33BoiPO06aKBo56SZmuU9pnY/edit
>
> On Thu, Mar 10, 2022 at 8:54 PM OpenInx  wrote:
>
> > > Probably most of the current Doris development comes from China, so we
> > do not refuse to use Chinese to write DSIP, because when describing some
> > complex content, it may be
> > > easier to express clearly in Chinese.
> > > For DSIPs written in Chinese, Doris PMC members will assist with English
> > translation when appropriate.
> >
> > Although Apache Doris was born from China and its core contributors come
> > from China, I still don't think it's reasonable to accept any technical
> > design document which is not written in English.  Indeed,  it may be easier
> > to express technical details clearly in Chinese for people from China,  but
> > it also implies:  it will be harder to understand & get the points for a
> > non-Chinese speaker.  I believe this is not good for growing the diversity
> > of the Apache project , according to my several apache experience.
> >
> > In general,  I will suggest accepting the standard English technical
> > design document in the apache doris community, so that everyone from
> > everywhere can discuss, understand, comment, share their thoughts.
> >
> >
> > On Thu, Mar 10, 2022 at 5:27 PM luzhijing <543881...@qq.com.invalid>
> > wrote:
> >
> >> +1 
> >>
> >>
> >>
> >>
> >> -- 原始邮件 --
> >> 发件人:
> >>   "dev"
> >> <
> >> morning...@163.com>;
> >> 发送时间: 2022年3月10日(星期四) 中午1:25
> >> 收件人: "doris-dev" >>
> >> 主题: [Discuss] About Doris Improvement Proposals
> >>
> >>
> >>
> >> Hi All:
> >> I would like to start using "Doris Improvement Proposals(DSIP)" to save
> >> all design doc of major features of Doris.
> >> The motivation of DSIP and details can be found here[1].
> >>
> >>
> >> Please feel free to discuss.
> >>
> >>
> >> [1]
> >> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> >>
> >>
> >>
> >> --
> >>
> >> 此致！Best Regards
> >> 陈明雨 Mingyu Chen
> >>
> >> Email:
> >> chenmin...@apache.org
> >
> >

-
To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org
For additional commands, e-mail: dev-h...@doris.apache.org

Re: [Discuss] About Doris Improvement Proposals

[王博]

+1
I have two more questions.
Frist:
For many projects that have been already completed or doing, do I need to
supplement this wiki?
Such as Vectorization or Stability optimization of Load Process .
Second:
How to ensure that this rule can be implemented for a long time?
Maybe we can review the wiki is filled every month by hosting regular
developer conferences.

陈明雨  于2022年3月10日周四 13:25写道：

> Hi All:
> I would like to start using "Doris Improvement Proposals(DSIP)" to save
> all design doc of major features of Doris.
> The motivation of DSIP and details can be found here[1].
>
>
> Please feel free to discuss.
>
>
> [1]
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org



-- 
王博  Wang Bo

Re: [Discuss] About Doris Improvement Proposals

[ling miao]

> How to ensure that this rule can be implemented for a long time?
Maybe we can review the wiki is filled every month by hosting regular
developer conferences.

We can put the writing DIP wiki in the development process description
document. (Just like the development process description for other projects)
For those who submit PR directly without DIP, contributors can comment to
remind him to submit DIP first.

Ling Miao

王博  于2022年3月11日周五 13:48写道：

> +1
> I have two more questions.
> Frist:
> For many projects that have been already completed or doing, do I need to
> supplement this wiki?
> Such as Vectorization or Stability optimization of Load Process .
> Second:
> How to ensure that this rule can be implemented for a long time?
> Maybe we can review the wiki is filled every month by hosting regular
> developer conferences.
>
> 陈明雨  于2022年3月10日周四 13:25写道：
>
> > Hi All:
> > I would like to start using "Doris Improvement Proposals(DSIP)" to save
> > all design doc of major features of Doris.
> > The motivation of DSIP and details can be found here[1].
> >
> >
> > Please feel free to discuss.
> >
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> >
> >
> >
> > --
> >
> > 此致！Best Regards
> > 陈明雨 Mingyu Chen
> >
> > Email:
> > chenmin...@apache.org
>
>
>
> --
> 王博  Wang Bo
>

Re: be异常退出

[王博]

当发生宕机时，你可以在be.out里找到这样的堆栈，这种是有效的信息

PC: @  0x25fd94b tcmalloc::CentralFreeList::FetchFromOneSpans()

*** SIGSEGV (@0x0) received by PID 71566 (TID 0x7f46785f8700) from PID 0;
stack trace: ***

@ 0x7f46e6dea5d0 (unknown)

@  0x25fd94b tcmalloc::CentralFreeList::FetchFromOneSpans()

@  0x25fdc1c tcmalloc::CentralFreeList::FetchFromOneSpansSafe()

@  0x25fdd17 tcmalloc::CentralFreeList::RemoveRange()

@  0x260a1e3 tcmalloc::ThreadCache::FetchFromCentralCache()

@  0x23c4818
google::protobuf::internal::RepeatedPtrFieldBase::InternalExtend()

@   0xdaac98 doris::ColumnWriter::finalize()

@   0xdb5038 doris::DoubleColumnWriterBase<>::finalize()

@   0xd91adb doris::SegmentWriter::_make_file_header()

@   0xd9254b doris::SegmentWriter::finalize()

@   0xd67e76 doris::ColumnDataWriter::_finalize_segment()

@   0xd694de doris::ColumnDataWriter::finalize()

@   0xd2db3c doris::SchemaChangeDirectly::process()

@   0xd3043c doris::SchemaChangeHandler::_alter_table()

@   0xd340f9 doris::SchemaChangeHandler::_do_alter_table()

@   0xd35283 doris::SchemaChangeHandler::process_alter_table()

@   0xcaa28b doris::OLAPEngine::schema_change()

@  0x11bf8be doris::TaskWorkerPool::_alter_table()

@  0x11c9a55
doris::TaskWorkerPool::_alter_table_worker_thread_callback()

@ 0x7f46e6de2dd5 start_thread

@ 0x7f46e61e802d __clone


又或者你可以使用gdb得到更详细的代码堆栈

从你目前给出的堆栈中，我没有看到有效的信息

刘波 <270309...@qq.com.invalid> 于2022年3月9日周三 14:59写道：

> 尊敬的开发者，您好：
>  今天be再次异常，其中be.out信息如下
>
>
> gdb结果如下
>
>
>
> -- 原始邮件 --
> *发件人:* "dev" ;
> *发送时间:* 2022年3月4日(星期五) 中午1:31
> *收件人:* "dev";
> *主题:* Re: be异常退出
>
> 目前的堆栈看起来不足以支撑做出判断；
> 如果线上有开core dump的话，可以用gdb palo_be core_dump文件看看堆栈
> 后者看下be.out是否进程怪盗时的堆栈
>
> 刘波 <270309...@qq.com.invalid> 于2022年3月4日周五 12:25写道：
>
> > 尊敬的开发者，您好：
> >  我们的doris
> > be节点经常会挂掉其中几个，经分析资源情况正常，具体信息可参见附件，日志层面未发现是OOM，未能定位出异常，请求协助，具体信息如下：
> >*时间： 2022-03-04 10:54:43*
> >doris报错*：detailMessage = tablet 45664199 has few replicas: 1,
> > alive backends: [10004]*
> >环境信息：华为云cetnos 8 64位，16核64G
> >
> >系统日志： less /var/log/message（*非OOM*）
> >
> > Mar  4 10:54:38 narwal-doris-be-0004 systemd[1]: Started Process Core
> Dump
> > (PID 1881819/UID 0).
> >
> > Mar  4 10:54:41 narwal-doris-be-0004 systemd-coredump[1881820]: Core file
> > was truncated to 2147483648 bytes.
> >
> > Mar  4 10:55:00 narwal-doris-be-0004 systemd-coredump[1881820]: Process
> > 2800630 (palo_be) of user 0 dumped core.#012#012Stack trace of thread
> > 1877601:#012#0  0x039480a2 memcpy
> >
> >  (/mnt/be/lib/palo_be)#012#012Stack trace of thread 2800630:#012#0
> > 0x7fccb330efc8 n/a (n/a)
> >
> > Mar  4 10:55:01 narwal-doris-be-0004 systemd[1]:
> > systemd-coredump@1-1881819-0.service: Succeeded.
> >
> > Mar  4 10:55:03 narwal-doris-be-0004 systemd[1]: session-12.scope:
> > Succeeded.
> >
> >
> >   dump信息：*coredumpctl info 2800630*
> >
> >PID: 2800630 (palo_be)
> >UID: 0 (root)
> >GID: 0 (root)
> > Signal: 11 (SEGV)
> >  Timestamp: Fri 2022-03-04 10:54:38 CST (1h 10min ago)
> >   Command Line: /mnt/be/lib/palo_be
> > Executable: /mnt/be/lib/palo_be
> >  Control Group: /
> >  Slice: -.slice
> >Boot ID: ca3ef395d7c547d2aecb1c251097066f
> > Machine ID: 501f93b5c19d4ca38db845c29176e3c5
> >   Hostname: narwal-doris-be-0004
> >Storage:
> >
> /var/lib/systemd/coredump/core.palo_be.0.ca3ef395d7c547d2aecb1c251097066f.2800630.164636247800.lz4
> > (truncated)
> >Message: Process 2800630 (palo_be) of user 0 dumped core.
> >
> > Stack trace of thread 1877601:
> > #0  0x039480a2 memcpy (/mnt/be/lib/palo_be)
> >
> > Stack trace of thread 2800630:
> > #0  0x7fccb330efc8 n/a (n/a)
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org
> > For additional commands, e-mail: dev-h...@doris.apache.org
>
>
>
> --
> 王博  Wang Bo
>
>

-- 
王博  Wang Bo

Re:Re: [Discuss] About Doris Improvement Proposals

[陈明雨]

1. For the existed or developing feature, this depends on the situation, such 
as the subsequent vectorization transformation related to Compaction or Stream 
load, I think it is necessary to form a DSIP.
2. How to ensure that this rule can be implemented for a long time?
As reviewers, we can ask for the DSIP, for example: 
https://github.com/apache/incubator-doris/pull/8437




--

此致！Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2022-03-11 13:53:31，"ling miao"  写道：
>> How to ensure that this rule can be implemented for a long time?
>Maybe we can review the wiki is filled every month by hosting regular
>developer conferences.
>
>We can put the writing DIP wiki in the development process description
>document. (Just like the development process description for other projects)
>For those who submit PR directly without DIP, contributors can comment to
>remind him to submit DIP first.
>
>Ling Miao
>
>王博  于2022年3月11日周五 13:48写道：
>
>> +1
>> I have two more questions.
>> Frist:
>> For many projects that have been already completed or doing, do I need to
>> supplement this wiki?
>> Such as Vectorization or Stability optimization of Load Process .
>> Second:
>> How to ensure that this rule can be implemented for a long time?
>> Maybe we can review the wiki is filled every month by hosting regular
>> developer conferences.
>>
>> 陈明雨  于2022年3月10日周四 13:25写道：
>>
>> > Hi All:
>> > I would like to start using "Doris Improvement Proposals(DSIP)" to save
>> > all design doc of major features of Doris.
>> > The motivation of DSIP and details can be found here[1].
>> >
>> >
>> > Please feel free to discuss.
>> >
>> >
>> > [1]
>> >
>> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
>> >
>> >
>> >
>> > --
>> >
>> > 此致！Best Regards
>> > 陈明雨 Mingyu Chen
>> >
>> > Email:
>> > chenmin...@apache.org
>>
>>
>>
>> --
>> 王博  Wang Bo
>>

Re: Re: [Discuss] About Doris Improvement Proposals

[ling miao]

Same as this PR: https://github.com/apache/incubator-doris/pull/8393/files

Ling Miao

陈明雨  于2022年3月11日周五 14:02写道：

> 1. For the existed or developing feature, this depends on the situation,
> such as the subsequent vectorization transformation related to Compaction
> or Stream load, I think it is necessary to form a DSIP.
> 2. How to ensure that this rule can be implemented for a long time?
> As reviewers, we can ask for the DSIP, for example:
> https://github.com/apache/incubator-doris/pull/8437
>
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org
>
>
>
>
>
> 在 2022-03-11 13:53:31，"ling miao"  写道：
> >> How to ensure that this rule can be implemented for a long time?
> >Maybe we can review the wiki is filled every month by hosting regular
> >developer conferences.
> >
> >We can put the writing DIP wiki in the development process description
> >document. (Just like the development process description for other
> projects)
> >For those who submit PR directly without DIP, contributors can comment to
> >remind him to submit DIP first.
> >
> >Ling Miao
> >
> >王博  于2022年3月11日周五 13:48写道：
> >
> >> +1
> >> I have two more questions.
> >> Frist:
> >> For many projects that have been already completed or doing, do I need
> to
> >> supplement this wiki?
> >> Such as Vectorization or Stability optimization of Load Process .
> >> Second:
> >> How to ensure that this rule can be implemented for a long time?
> >> Maybe we can review the wiki is filled every month by hosting regular
> >> developer conferences.
> >>
> >> 陈明雨  于2022年3月10日周四 13:25写道：
> >>
> >> > Hi All:
> >> > I would like to start using "Doris Improvement Proposals(DSIP)" to
> save
> >> > all design doc of major features of Doris.
> >> > The motivation of DSIP and details can be found here[1].
> >> >
> >> >
> >> > Please feel free to discuss.
> >> >
> >> >
> >> > [1]
> >> >
> >>
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > 此致！Best Regards
> >> > 陈明雨 Mingyu Chen
> >> >
> >> > Email:
> >> > chenmin...@apache.org
> >>
> >>
> >>
> >> --
> >> 王博  Wang Bo
> >>
>

Re: Re: [Discuss] About Doris Improvement Proposals

[Gabriel Lee]

This will be a useful part and I have one more suggestion.
We should re-organize our roadmap with DIP just like Apache
 Airflow community
. This will help developers
a lot to understand what we are doing and participate in some jobs.

On Fri, 11 Mar 2022 at 14:02, 陈明雨  wrote:

> 1. For the existed or developing feature, this depends on the situation,
> such as the subsequent vectorization transformation related to Compaction
> or Stream load, I think it is necessary to form a DSIP.
> 2. How to ensure that this rule can be implemented for a long time?
> As reviewers, we can ask for the DSIP, for example:
> https://github.com/apache/incubator-doris/pull/8437
>
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org
>
>
>
>
>
> 在 2022-03-11 13:53:31，"ling miao"  写道：
> >> How to ensure that this rule can be implemented for a long time?
> >Maybe we can review the wiki is filled every month by hosting regular
> >developer conferences.
> >
> >We can put the writing DIP wiki in the development process description
> >document. (Just like the development process description for other
> projects)
> >For those who submit PR directly without DIP, contributors can comment to
> >remind him to submit DIP first.
> >
> >Ling Miao
> >
> >王博  于2022年3月11日周五 13:48写道：
> >
> >> +1
> >> I have two more questions.
> >> Frist:
> >> For many projects that have been already completed or doing, do I need
> to
> >> supplement this wiki?
> >> Such as Vectorization or Stability optimization of Load Process .
> >> Second:
> >> How to ensure that this rule can be implemented for a long time?
> >> Maybe we can review the wiki is filled every month by hosting regular
> >> developer conferences.
> >>
> >> 陈明雨  于2022年3月10日周四 13:25写道：
> >>
> >> > Hi All:
> >> > I would like to start using "Doris Improvement Proposals(DSIP)" to
> save
> >> > all design doc of major features of Doris.
> >> > The motivation of DSIP and details can be found here[1].
> >> >
> >> >
> >> > Please feel free to discuss.
> >> >
> >> >
> >> > [1]
> >> >
> >>
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > 此致！Best Regards
> >> > 陈明雨 Mingyu Chen
> >> >
> >> > Email:
> >> > chenmin...@apache.org
> >>
> >>
> >>
> >> --
> >> 王博  Wang Bo
> >>
>

Re: Re: [Discuss] About Doris Improvement Proposals

[OpenInx]

> But I would like to have a lower threshold to help the Doris community
quickly establish a mechanism for DSIP. This is equivalent to a cold start
process. In the meantime, PMC members will help with the translation of the
Chinese documentation.

Personally,  I will not suggest changing the normal apache way to establish
some kinds of mechanism. The correct direction is accepting general English
design document to apache doris board.  If there is a contributor who is
really not good at English technical writing, then he/she can request
PMC/committers from community to help to do the translate & pre-review
privately. But if he/she plan to publish the design document to apache
doris community,  it should be a general English document so that everyone
from the community can start do the reviewing in the same baseline.


On Fri, Mar 11, 2022 at 2:20 PM Gabriel Lee 
wrote:

> This will be a useful part and I have one more suggestion.
> We should re-organize our roadmap with DIP just like Apache
>  Airflow community
> . This will help
> developers
> a lot to understand what we are doing and participate in some jobs.
>
> On Fri, 11 Mar 2022 at 14:02, 陈明雨  wrote:
>
> > 1. For the existed or developing feature, this depends on the situation,
> > such as the subsequent vectorization transformation related to Compaction
> > or Stream load, I think it is necessary to form a DSIP.
> > 2. How to ensure that this rule can be implemented for a long time?
> > As reviewers, we can ask for the DSIP, for example:
> > https://github.com/apache/incubator-doris/pull/8437
> >
> >
> >
> >
> > --
> >
> > 此致！Best Regards
> > 陈明雨 Mingyu Chen
> >
> > Email:
> > chenmin...@apache.org
> >
> >
> >
> >
> >
> > 在 2022-03-11 13:53:31，"ling miao"  写道：
> > >> How to ensure that this rule can be implemented for a long time?
> > >Maybe we can review the wiki is filled every month by hosting regular
> > >developer conferences.
> > >
> > >We can put the writing DIP wiki in the development process description
> > >document. (Just like the development process description for other
> > projects)
> > >For those who submit PR directly without DIP, contributors can comment
> to
> > >remind him to submit DIP first.
> > >
> > >Ling Miao
> > >
> > >王博  于2022年3月11日周五 13:48写道：
> > >
> > >> +1
> > >> I have two more questions.
> > >> Frist:
> > >> For many projects that have been already completed or doing, do I need
> > to
> > >> supplement this wiki?
> > >> Such as Vectorization or Stability optimization of Load Process .
> > >> Second:
> > >> How to ensure that this rule can be implemented for a long time?
> > >> Maybe we can review the wiki is filled every month by hosting regular
> > >> developer conferences.
> > >>
> > >> 陈明雨  于2022年3月10日周四 13:25写道：
> > >>
> > >> > Hi All:
> > >> > I would like to start using "Doris Improvement Proposals(DSIP)" to
> > save
> > >> > all design doc of major features of Doris.
> > >> > The motivation of DSIP and details can be found here[1].
> > >> >
> > >> >
> > >> > Please feel free to discuss.
> > >> >
> > >> >
> > >> > [1]
> > >> >
> > >>
> >
> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > 此致！Best Regards
> > >> > 陈明雨 Mingyu Chen
> > >> >
> > >> > Email:
> > >> > chenmin...@apache.org
> > >>
> > >>
> > >>
> > >> --
> > >> 王博  Wang Bo
> > >>
> >
>