Check if we can switch serialization/deser between IO and Dubbo Threads.

[chickenlj]

Here's the doc describing Dubbo's ThreadPool Model: http://dubbo.apache.org/#!/docs/user/demos/thread-model.md?lang=zh-cn

Here's the code deciding Serialization thread
https://github.com/apache/incubator-dubbo/blob/70e1e6220b82fd20611d7ec2624726442671bf95/dubbo-rpc/dubbo-rpc-dubbo/src/main/java/org/apache/dubbo/rpc/protocol/dubbo/DubboCodec.java#L88

[tswstarplanet]

Excuse me. What is the meaning of "switch serialization/deser between IO and Dubbo Threads"?

[zonghaishang]

Netty io thread & dubbo thread pool

[tswstarplanet]

@zonghaishang So it just means that we should check if the serialization/deser will succeed ?

[zonghaishang]

You are right, but more likely to provide a parameter configuration, the internal decision of the framework

[tswstarplanet]

But how do we know if the serialization/deser will succeed?

[ranchoswang]

In default , decode in io is open , You can use
<ddubbo:protocol decode.in.io="false"> in xml to close it (when you think deser takes long enough time).

[sinmaystar]

we can switch serialization thread like this:
<dubbo:protocol name="dubbo" port="20880">
<dubbo:parameter key="decode.in.io" value="false"/>
</dubbo:protocol>

there is no need to modify source code or add user define xml schema

[diecui1202]

@chickenlj IMO, there is nothing we can do from the comments, I'll close it. Any thoughts ?