[GitHub] [incubator-brpc] haolujun closed issue #767: 使用redis客户端时奇怪的200ms问题

haolujun closed issue #767: 使用redis客户端时奇怪的200ms问题 URL: https://github.com/apache/incubator-brpc/issues/767 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [incubator-brpc] haolujun commented on issue #767: 使用redis客户端时奇怪的200ms问题

haolujun commented on issue #767: 使用redis客户端时奇怪的200ms问题 URL: https://github.com/apache/incubator-brpc/issues/767#issuecomment-522968251 > 看一下机器的 tcp 重传监控，是否tcp重传很高 。 200ms看起来是触发了 tcp重传 导致部分请求+200ms 是的，应该是网络流量大，有偶尔的丢包现象，导致触发tcp重传，重传是的ttl最小值一般为200ms。

[GitHub] [incubator-brpc] jamesge commented on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？

jamesge commented on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？ URL: https://github.com/apache/incubator-brpc/issues/896#issuecomment-522974958 https://github.com/apache/incubator-brpc/blob/8c32109de6d697f4c14bf808e19f251fb3a47e9d/src/brpc/details/http_message.cpp#L164

[GitHub] [incubator-brpc] jamesge commented on issue #893: fix bug: bthread_cond_timedwait not return when timeout

jamesge commented on issue #893: fix bug: bthread_cond_timedwait not return when timeout URL: https://github.com/apache/incubator-brpc/pull/893#issuecomment-522977038 看下 #617 This is an automated message from the Apache Git

[GitHub] [incubator-brpc] Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？

Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？ URL: https://github.com/apache/incubator-brpc/issues/896#issuecomment-522983524 > https://github.com/apache/incubator-brpc/blob/8c32109de6d697f4c14bf808e19f251fb3a47e9d/src/brpc/details/http_message.cpp#L164

[GitHub] [incubator-brpc] Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？

Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？ URL: https://github.com/apache/incubator-brpc/issues/896#issuecomment-522983524 > https://github.com/apache/incubator-brpc/blob/8c32109de6d697f4c14bf808e19f251fb3a47e9d/src/brpc/details/http_message.cpp#L164

[GitHub] [incubator-brpc] Re-bin commented on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？

Re-bin commented on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？ URL: https://github.com/apache/incubator-brpc/issues/896#issuecomment-522983524 > https://github.com/apache/incubator-brpc/blob/8c32109de6d697f4c14bf808e19f251fb3a47e9d/src/brpc/details/http_message.cpp#L164

[GitHub] [incubator-brpc] Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？

Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？ URL: https://github.com/apache/incubator-brpc/issues/896#issuecomment-522983524 > https://github.com/apache/incubator-brpc/blob/8c32109de6d697f4c14bf808e19f251fb3a47e9d/src/brpc/details/http_message.cpp#L164

[GitHub] [incubator-brpc] Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？

Re-bin edited a comment on issue #896: 有个疑惑，想知道brpc中的controller里面的uri数据一般是怎么获得的？ URL: https://github.com/apache/incubator-brpc/issues/896#issuecomment-522983524 > https://github.com/apache/incubator-brpc/blob/8c32109de6d697f4c14bf808e19f251fb3a47e9d/src/brpc/details/http_message.cpp#L164

[GitHub] [incubator-brpc] zyearn commented on issue #894: 随着运行时间的增长出现很多未释放的close wait的连接和bthread

zyearn commented on issue #894: 随着运行时间的增长出现很多未释放的close wait的连接和bthread URL: https://github.com/apache/incubator-brpc/issues/894#issuecomment-523282324 worker全部都阻塞住了么（可以通过curl 'ip:port/health'判断，如果没有返回就是阻塞了）？如果阻塞住的话，EventDispatcher就不工作了，fd可能不会被close

[GitHub] [incubator-brpc] zyearn edited a comment on issue #894: 随着运行时间的增长出现很多未释放的close wait的连接和bthread

zyearn edited a comment on issue #894: 随着运行时间的增长出现很多未释放的close wait的连接和bthread URL: https://github.com/apache/incubator-brpc/issues/894#issuecomment-523282324 worker全部都阻塞住了么（可以通过curl 'ip:port/health'判断，如果没有返回就是阻塞了）？如果阻塞住的话，EventDispatcher就不工作了，fd可能不会被close

[GitHub] [incubator-brpc] liupengs commented on issue #866: bthread_cond_timedwait 偶尔出现超时不返回

liupengs commented on issue #866: bthread_cond_timedwait 偶尔出现超时不返回 URL: https://github.com/apache/incubator-brpc/issues/866#issuecomment-522992234 见 #617 This is an automated message from the Apache Git Service. To respond

[GitHub] [incubator-brpc] liupengs closed issue #866: bthread_cond_timedwait 偶尔出现超时不返回

liupengs closed issue #866: bthread_cond_timedwait 偶尔出现超时不返回 URL: https://github.com/apache/incubator-brpc/issues/866 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [incubator-brpc] liupengs commented on issue #893: fix bug: bthread_cond_timedwait not return when timeout

liupengs commented on issue #893: fix bug: bthread_cond_timedwait not return when timeout URL: https://github.com/apache/incubator-brpc/pull/893#issuecomment-522990934 这个问题在我们使用场景中出现频率挺高，我们在百度内部和社区提 issues 都是一直无人理。 问题根源就是函数 erase_from_butex 和 wait_for_butex 中操作 container 的顺序不确定，