Re: Upcoming Event: Apache Dubbo(incubating) Guangzhou Meetup
Hi Mark, On Fri, Jan 11, 2019 at 8:48 PM Mark Thomas wrote: > > On 10/01/2019 08:59, chenwei qi wrote: > > Hi Mark, > > > > Thanks for your kindly review. I will answer your questions orderly as > > following: > > > >> Who is the "we" that will be checking? > > The PPMC members will check the list and they will decide the checking > > date. As the meetup will be held on Jan.19, I suggest the check works from > > Jan.14 to Jan.16, last 3 days. > > > >> What will they be checking for? > > As it is the 1st time Apache Dubbo™ Meetup will be held in Guangzhou, face > > to face discussion among deep users there can be useful. But the meetup > > registration can be up to 300-400, too many for discussion. Check from the > > registration information is to select out the deep user. > > > >> Where is the on-list discussion that decided a) that checking was > > required and b) what to check for? > > The criteria of user selection is not suitable to be discussed publicly, I > > think it is better to discuss with Dubbo PPMC privately. > > You appear to have missed the key point. > > A whole bunch of decisions appear to have been made about a Dubbo event > with ZERO discussion of those decisions on any Dubbo mailing list. > Public or private. The discussion happened on mailing list from initializing the event[1], calling for talks [2] to the schedule[3]. The process for invite a small group of users was discussed there[3]. [1] https://lists.apache.org/thread.html/ff3a0797e15256738280647f6604e7f5f8eaf6299efe859ced85b5f0@%3Cdev.dubbo.apache.org%3E [2] https://lists.apache.org/thread.html/45364fe72f1b2c7bfb1d01f736316775c9ca99a0d9964c68dfa043e3@%3Cdev.dubbo.apache.org%3E [3] https://lists.apache.org/thread.html/ef1b4e039954554082a15faa78bc04b234d04348aaa46d816a690339@%3Cdev.dubbo.apache.org%3E > That is simply not how podlings are expected to > operate. What is most worrying is that at no point did any PPMC member > say during these off-list discussions "Hang on. We should be doing this > on the mailing list." I think there is some misunderstanding about who should be running the event. It is the PPMCs who should be running this event, but the fact is that most of the work are done by organizers, rather than PPMCs. I didn't pay too much attention on this, which is my fault and I agree that the event organizers should work more closely with the PPMC. The organizers are fresh to Apache way, which is quite different from their day-to-day work, so I think it may take some time for them to get used to it. I will keep an eye on this, and trying my best to encourage them to be on the list. > > I also disagree that the criteria need to be discussed in private but > that point is debatable. I am not sure it should go public or not until I see the criteria, so I think we should discuss it privately first, if the PPMC decides that it can go publicly, then we can announce it later. > > Mark -- Best Regards！ Huxing
Re: [Proposal] A proposal to use IdleStateHandler to replace using Timer to send HeartBeat.
Hi The changes don’t follow my attentions, I will submit my design later. Maybe we need describe the problem more detailedly, then the problem has solved for a half. > 在 2019年1月12日，下午7:45，Jun Alpha 写道： > > Hello everyone, I have commit a pull request[1] to optimize Dubbo's > heartbeat mechanise, > witch is mentioned in this email and this issue[2],pls review it. > > [1] https://github.com/apache/incubator-dubbo/pull/3213 > [2] https://github.com/apache/incubator-dubbo/issues/3151 > > 徐靖峰 <250577...@qq.com> 于2019年1月11日周五 上午7:46写道： > >> @Jun Alpha great, I am glad to review your changes and wait for your pull >> request. >> >>> 在 2019年1月10日，下午8:00，Jun Alpha 写道： >>> >>> I'll try it. >>> >>> Ian Luo 于2019年1月10日周四 下午2:21写道： >>> It is a good suggestion any way, we should give it a try at least. -Ian. On Thu, Jan 10, 2019 at 10:21 AM yuhang xiu wrote: > hi, @jun alpha > > I agree. > If netty can do more precise heartbeat control, we can integrate its design > in our heartbeat. Would you like to try it? > > Jun Alpha 于2019年1月9日周三 下午9:21写道： > >> Hi,I left a comment in this issue[1],I think it's worth to learn from >> netty's heartbeat mechanism. >> >> [1] https://github.com/apache/incubator-dubbo/issues/3151 >> >> Ian Luo 于2019年1月7日周一 下午10:47写道： >> >>> Thanks >>> >>> On Mon, Jan 7, 2019 at 2:50 PM yuhang xiu wrote: >>> Hi, I left some comments in this issue[1] Thanks to beiwei for reminding. I forgot that we have some non-netty servers. In this case, I personally prefer all heartbeats to use the >> same set of mechanisms to guarantee. But we can learn from netty's > heartbeat mechanism to ensure more accurate heartbeat control. [1] https://github.com/apache/incubator-dubbo/issues/3151 Ian Luo 于2019年1月7日周一 下午1:09写道： > It is an interesting topic. It is worthy to give it a try when > Dubbo >>> uses > Netty, but pls. keep in mind that Dubbo has the ability to use > other > servers. I am not sure whether this suggestion will introduce >>> unnecessary > complexity. > > JingFeng, would you mind to file an issue and give it a try if you >> have > time? > > Thanks, > -Ian. > > > On Mon, Jan 7, 2019 at 11:03 AM 徐靖峰 <250577...@qq.com> wrote: > >> Hi all >> >> 现状： >> >> Dubbo >> > >>> >> > >> 在应用层面发送心跳包保证连接的可用性，使用了定时器的设计，在客户端和服务端分别设置一个定时器，发送心跳，当发现连接断开时，客户端负责重连，服务端负责 >> close。使用定时器并不是一个好的设计，在忙通信时，心跳是不必要的。建议使用 Netty 的 >> IdleStateHandler，仅仅在检测到空闲连接时发送心跳。 >> >> 修改建议： >> >> 使用 IdleStateHandler 代替 Timer 发送心跳 >> 关闭 ChannelOption.SO_KEEPALIVE，网络层面的 TCP 断连需要在机器级别设置，默认是 2 >> 小时，几乎没有必要存在，却发出了无必要的 TCP 探测包，仅仅依赖于应用层的心跳来给连接保活即可。 >> For now: >> >> Dubbo sends a heartbeat packet at the application level to ensure >> the >> availability of the connection. A timer is set on the client and >> the > server >> to send a heartbeat. When the connection is found to be >> disconnected, the >> client is responsible for reconnection and the server is >> responsible for >> close. Using a timer is not a good design, and the heartbeat is > unnecessary >> when communicating busy. It is recommended to use Netty's > IdleStateHandler >> to send a heartbeat only when an idle connection is detected. >> >> Proposed changes: >> >> Send heartbeats using IdleStateHandler instead of Timer >> Close ChannelOption.SO_KEEPALIVE, TCP disconnection at the > network level >> needs to be set at the machine level. The default is 2 hours. > There >>> is >> almost no need to exist, but an unnecessary TCP probe packet is >>> issued. > It >> only depends on the heartbeat of the application layer to keep > the >> connection alive. Just fine. >> >> > >>> >> > >> >> >> >>
Re: [Proposal] A proposal to use IdleStateHandler to replace using Timer to send HeartBeat.
Hello everyone, I have commit a pull request[1] to optimize Dubbo's heartbeat mechanise, witch is mentioned in this email and this issue[2],pls review it. [1] https://github.com/apache/incubator-dubbo/pull/3213 [2] https://github.com/apache/incubator-dubbo/issues/3151 徐靖峰 <250577...@qq.com> 于2019年1月11日周五 上午7:46写道： > @Jun Alpha great, I am glad to review your changes and wait for your pull > request. > > > 在 2019年1月10日，下午8:00，Jun Alpha 写道： > > > > I'll try it. > > > > Ian Luo 于2019年1月10日周四 下午2:21写道： > > > >> It is a good suggestion any way, we should give it a try at least. > >> > >> -Ian. > >> > >> On Thu, Jan 10, 2019 at 10:21 AM yuhang xiu wrote: > >> > >>> hi, @jun alpha > >>> > >>> I agree. > >>> If netty can do more precise heartbeat control, we can integrate its > >> design > >>> in our heartbeat. Would you like to try it? > >>> > >>> Jun Alpha 于2019年1月9日周三 下午9:21写道： > >>> > Hi,I left a comment in this issue[1],I think it's worth to learn from > netty's heartbeat mechanism. > > [1] https://github.com/apache/incubator-dubbo/issues/3151 > > Ian Luo 于2019年1月7日周一 下午10:47写道： > > > Thanks > > > > On Mon, Jan 7, 2019 at 2:50 PM yuhang xiu > >> wrote: > > > >> Hi, I left some comments in this issue[1] > >> > >> Thanks to beiwei for reminding. I forgot that we have some > >> non-netty > >> servers. In this case, I personally prefer all heartbeats to use > >> the > same > >> set of mechanisms to guarantee. But we can learn from netty's > >>> heartbeat > >> mechanism to ensure more accurate heartbeat control. > >> > >> [1] https://github.com/apache/incubator-dubbo/issues/3151 > >> > >> Ian Luo 于2019年1月7日周一 下午1:09写道： > >> > >>> It is an interesting topic. It is worthy to give it a try when > >>> Dubbo > > uses > >>> Netty, but pls. keep in mind that Dubbo has the ability to use > >>> other > >>> servers. I am not sure whether this suggestion will introduce > > unnecessary > >>> complexity. > >>> > >>> JingFeng, would you mind to file an issue and give it a try if > >> you > have > >>> time? > >>> > >>> Thanks, > >>> -Ian. > >>> > >>> > >>> On Mon, Jan 7, 2019 at 11:03 AM 徐靖峰 <250577...@qq.com> wrote: > >>> > Hi all > > 现状： > > Dubbo > > >>> > >> > > > > >>> > >> > 在应用层面发送心跳包保证连接的可用性，使用了定时器的设计，在客户端和服务端分别设置一个定时器，发送心跳，当发现连接断开时，客户端负责重连，服务端负责 > close。使用定时器并不是一个好的设计，在忙通信时，心跳是不必要的。建议使用 Netty 的 > IdleStateHandler，仅仅在检测到空闲连接时发送心跳。 > > 修改建议： > > 使用 IdleStateHandler 代替 Timer 发送心跳 > 关闭 ChannelOption.SO_KEEPALIVE，网络层面的 TCP 断连需要在机器级别设置，默认是 2 > 小时，几乎没有必要存在，却发出了无必要的 TCP 探测包，仅仅依赖于应用层的心跳来给连接保活即可。 > For now: > > Dubbo sends a heartbeat packet at the application level to > >> ensure > the > availability of the connection. A timer is set on the client > >> and > the > >>> server > to send a heartbeat. When the connection is found to be > disconnected, > >> the > client is responsible for reconnection and the server is > responsible > >> for > close. Using a timer is not a good design, and the heartbeat is > >>> unnecessary > when communicating busy. It is recommended to use Netty's > >>> IdleStateHandler > to send a heartbeat only when an idle connection is detected. > > Proposed changes: > > Send heartbeats using IdleStateHandler instead of Timer > Close ChannelOption.SO_KEEPALIVE, TCP disconnection at the > >>> network > >> level > needs to be set at the machine level. The default is 2 hours. > >>> There > > is > almost no need to exist, but an unnecessary TCP probe packet is > > issued. > >>> It > only depends on the heartbeat of the application layer to keep > >>> the > connection alive. Just fine. > > > >>> > >> > > > > >>> > >> > > > >
Re: Dubbo snapshot version
https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/ Yunkun Huang 于2019年1月12日周六 下午4:26写道： > hey team, > > I try to find snapshot version for dubbo 2.7 but it seems not exsited in > http://repository.apache.org/snapshots/. > > I can't find any related configuration in travis ci configuration, so > would like to confirm if there is any snapshot version in any repository? > > >
Dubbo snapshot version
hey team, I try to find snapshot version for dubbo 2.7 but it seems not exsited in http://repository.apache.org/snapshots/. I can't find any related configuration in travis ci configuration, so would like to confirm if there is any snapshot version in any repository?
