pnowojski commented on a change in pull request #6355: 
[FLINK-9878][network][ssl] add more low-level ssl options
URL: https://github.com/apache/flink/pull/6355#discussion_r210531098
 
 

 ##########
 File path: 
flink-runtime/src/test/java/org/apache/flink/runtime/io/network/netty/NettyClientServerSslTest.java
 ##########
 @@ -65,6 +68,60 @@ public void testValidSslConnection() throws Exception {
 
                Channel ch = NettyTestUtil.connect(serverAndClient);
 
+               SslHandler sslHandler = (SslHandler) ch.pipeline().get("ssl");
+               assertTrue("default value should not be propagated", 
sslHandler.getHandshakeTimeoutMillis() >= 0);
+               assertTrue("default value should not be propagated", 
sslHandler.getCloseNotifyTimeoutMillis() >= 0);
+
+               // should be able to send text data
+               ch.pipeline().addLast(new StringDecoder()).addLast(new 
StringEncoder());
+               assertTrue(ch.writeAndFlush("test").await().isSuccess());
+
+               NettyTestUtil.shutdown(serverAndClient);
+       }
+
+       /**
+        * Verify valid (advanced) ssl configuration and connection.
+        */
+       @Test
+       public void testValidSslConnectionAdvanced() throws Exception {
 
 Review comment:
   Yes, you are right regarding `handshake-timeout` and 
`close-notify-flush-timeout`, but as I wrote previously, I do not see how 
`SESSION_CACHE_SIZE` and `SESSION_TIMEOUT` are tested at all. And regardless of 
that, it still would be better to add a stress test/benchmark for that. Depends 
how important this feature is... However if it's not important one could argue 
why even bother supporting this? 
   
   On a side note. Couldn't we provide some generic way to configure netty? 
Like passing any config option prefixed `taskmanager.netty.client` to 
taskmanager's netty client, without manually specifying and handling them by us?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to