You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@geode.apache.org by GitBox <gi...@apache.org> on 2020/09/10 23:26:19 UTC

[GitHub] [geode] Bill commented on pull request #5502: add 1.13.0 to old versions and set as Benchmarks baseline on develop

Bill commented on pull request #5502:
URL: https://github.com/apache/geode/pull/5502#issuecomment-690783716


   I've added @bschuchardt as a reviewer since I want to be sure I'm not masking an actual problem by turning off the HTTP service in the WAN rolling upgrade.
   
   When rolling from 1.13.0 to current we were seeing this failure when the _second_ locator was started:
   
   ```
   org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo > EventProcessingMixedSiteOneOldSiteTwo[from_v1.13.0] FAILED
   …
       [error 2020/09/10 00:53:04.392 GMT <RMI TCP Connection(1)-172.17.0.33> tid=34] Jmx manager could not be started because HTTP service failed to start
   
       org.apache.geode.management.ManagementException: HTTP service failed to start
   …
       Caused by: java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:7070
   …
       Caused by: java.net.BindException: Address already in use
   ```
   
   Same for three of the other WAN rolling upgrade tests.
   
   But when rolling from older versions (before 1.13.0) to current we saw no such conflict.
   
   I would have expected the same failure on all old versions!


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org