[jira] [Commented] (GEODE-8656) Ping not sent to the right gateway receiver endpoint when several receivers have the same hostname-for-senders value
[ https://issues.apache.org/jira/browse/GEODE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239925#comment-17239925 ] ASF GitHub Bot commented on GEODE-8656: --- onichols-pivotal commented on pull request #5775: URL: https://github.com/apache/geode/pull/5775#issuecomment-735126404 Agreed! Do you happen to have a link to the concourse.apachegeode-ci.info test result to confirm this checkin broke current tests and is blocking other people's work? 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: us...@infra.apache.org > Ping not sent to the right gateway receiver endpoint when several receivers > have the same hostname-for-senders value > > > Key: GEODE-8656 > URL: https://issues.apache.org/jira/browse/GEODE-8656 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > When several gateway receivers have the same value for hostname-for-senders > (for example when running Geode under kubernetes and a load balancer balances > the load among the remote servers), the ping messages sent from the gateway > sender client are only sent to the receiver (endpoint) to which the sender > connected first. > The other receivers will not get the ping message which will imply that the > connections towards them will be closed after the configured timeout expires. > This ticket is a continuation of the work done ticket GEODE-7565. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8744) multiple versions of json-smart
Owen Nichols created GEODE-8744: --- Summary: multiple versions of json-smart Key: GEODE-8744 URL: https://issues.apache.org/jira/browse/GEODE-8744 Project: Geode Issue Type: Improvement Components: release Affects Versions: 1.13.1 Reporter: Owen Nichols develop and 1.12 release binaries contain only json-smart 2.3, but 1.13.1 contained both 1.3.1 and 2.3 due to the particular version of spring-security-oauth2-client in this release. 2.3 is preferred and should be used in all places -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8744) multiple versions of json-smart
[ https://issues.apache.org/jira/browse/GEODE-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240172#comment-17240172 ] ASF GitHub Bot commented on GEODE-8744: --- onichols-pivotal opened a new pull request #5776: URL: https://github.com/apache/geode/pull/5776 develop and 1.12 release binaries contain only json-smart 2.3, but 1.13.1 contained both 1.3.1 and 2.3 due to the particular version of spring-security-oauth2-client in this release. this change makes sure 2.3 is used in all places. try `./gradlew :geode-pulse:dependencies | grep json-smart` with and without this fix to see the issue. 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: us...@infra.apache.org > multiple versions of json-smart > --- > > Key: GEODE-8744 > URL: https://issues.apache.org/jira/browse/GEODE-8744 > Project: Geode > Issue Type: Improvement > Components: release >Affects Versions: 1.13.1 >Reporter: Owen Nichols >Priority: Major > > develop and 1.12 release binaries contain only json-smart 2.3, but 1.13.1 > contained both 1.3.1 and 2.3 due to the particular version of > spring-security-oauth2-client in this release. 2.3 is preferred and should > be used in all places -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8744) multiple versions of json-smart
[ https://issues.apache.org/jira/browse/GEODE-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-8744: -- Labels: pull-request-available (was: ) > multiple versions of json-smart > --- > > Key: GEODE-8744 > URL: https://issues.apache.org/jira/browse/GEODE-8744 > Project: Geode > Issue Type: Improvement > Components: release >Affects Versions: 1.13.1 >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > develop and 1.12 release binaries contain only json-smart 2.3, but 1.13.1 > contained both 1.3.1 and 2.3 due to the particular version of > spring-security-oauth2-client in this release. 2.3 is preferred and should > be used in all places -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8656) Ping not sent to the right gateway receiver endpoint when several receivers have the same hostname-for-senders value
[ https://issues.apache.org/jira/browse/GEODE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240175#comment-17240175 ] ASF GitHub Bot commented on GEODE-8656: --- gesterzhou commented on pull request #5775: URL: https://github.com/apache/geode/pull/5775#issuecomment-735319993 It blocked regression tests and if we are releasing 1.14, it's a release blocker. All the release blockers for 1.13 and earlier versions we resolved recently did not cause concourse.apachegeode-ci.info to fail. 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: us...@infra.apache.org > Ping not sent to the right gateway receiver endpoint when several receivers > have the same hostname-for-senders value > > > Key: GEODE-8656 > URL: https://issues.apache.org/jira/browse/GEODE-8656 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > When several gateway receivers have the same value for hostname-for-senders > (for example when running Geode under kubernetes and a load balancer balances > the load among the remote servers), the ping messages sent from the gateway > sender client are only sent to the receiver (endpoint) to which the sender > connected first. > The other receivers will not get the ping message which will imply that the > connections towards them will be closed after the configured timeout expires. > This ticket is a continuation of the work done ticket GEODE-7565. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8656) Ping not sent to the right gateway receiver endpoint when several receivers have the same hostname-for-senders value
[ https://issues.apache.org/jira/browse/GEODE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240178#comment-17240178 ] ASF GitHub Bot commented on GEODE-8656: --- onichols-pivotal commented on pull request #5775: URL: https://github.com/apache/geode/pull/5775#issuecomment-735339651 It sounds like your concern involves private code that is not part of Geode. In these cases it is especially important to communicate in as much detail as possible the nature of the problem you encountered, under what conditions, and most importantly, what the next steps will be. Will you try to add a Geode test demonstrating the problem so the original committer can submit a revised PR? Can you offer to work with the original committer to improve their change once you have a better understanding of the root cause? Can you offer to test iterations of their improved PR against your private code? If you find a workaround in your private code would you consider a straight undo of the revert? It’s all too easy to revert someone else’s fix and then forget about it. An “emergency revert” incurs a debt; there needs to be a plan to repay it. I’ll be happy to withdraw my -1, just looking for a few words about the problem area (compile failure? data loss? server hangs/crashes?), conditions (number of servers/locators? wan? upgrade? any special config settings?), and commitment to follow up after revert. 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: us...@infra.apache.org > Ping not sent to the right gateway receiver endpoint when several receivers > have the same hostname-for-senders value > > > Key: GEODE-8656 > URL: https://issues.apache.org/jira/browse/GEODE-8656 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > When several gateway receivers have the same value for hostname-for-senders > (for example when running Geode under kubernetes and a load balancer balances > the load among the remote servers), the ping messages sent from the gateway > sender client are only sent to the receiver (endpoint) to which the sender > connected first. > The other receivers will not get the ping message which will imply that the > connections towards them will be closed after the configured timeout expires. > This ticket is a continuation of the work done ticket GEODE-7565. -- This message was sent by Atlassian Jira (v8.3.4#803005)
