-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.3.x] MODCLUSTER-824 Improve handling of overlapping aliases in APP commands #840
base: 1.3.x
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the commit message so that the Jira ID is the first in the commit message.
Upstream is merged, marking ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we please validate the removal behavior? Just to make sure there isn't a side-effect that we are missing.
Before the patch, two virtual hosts with overlapping aliases are created. When REMOVE-APP is sent to the overlapping alias, only one of the hosts gets removed. (That does no affect the case when the remove command is sent with With this PR, only one virtual hosts is present because in case of an overlap, the two get merged. Then the removal removes the only host as expected. |
@rhusar any updates on this? |
while (host == NULL && i + start < strlen(vhost->host)) { | ||
while (vhost->host[start+i] != ',' && vhost->host[start+i] != '\0') { | ||
i++; | ||
} | ||
|
||
strncpy(hostinfo.host, vhost->host + start, i); | ||
hostinfo.host[i] = '\0'; | ||
host = read_host(hoststatsmem, &hostinfo); | ||
start = start + i + 1; | ||
i = 0; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jajik Sorry for delay, but I am under suspicion this is still a little wrong / problematic. While the 'matching' fix is correct and should really result in 1 vhost if any of the aliases are overlapping - the result bit should not be a merge, but a replace.
E.g. an existing vhost with aliases A,B
receives update with B,C
, the resulting vhost should be B,C
rather than a merge of A,B,C
.
Let me know if I misunderstood.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfclere What do you think? May that result in some node infighting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhusar hm do we want to merge?... because if the back-end send a ENABLE context/hosts, so you are thinking of:
- /test A,B
- /other B, C
that means you have in the back-end
VM1 : A, B
VM2: B, C
So a request to /test on A should go to test on host1 and a request to /test on C (host2) should give a 404 (well look to find other context/hosts).
so merging looks wrong that way... B, C also looks wrong no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
host1, host2 are jvmroutes and A, B, C aliases in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and:
/test A,B (VM1)
/test B,C (VM2)
Should be rejected : we don't know how to route /test B ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But in case of different JVMRoutes the merge does not happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jajik correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would create
Node host1
- Contexts
- /test
- Aliases
- A, B
Node host2
- Contexts
- /other
- Aliases
- B, C
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the merge would happen only if new ENABLE-APP with /test B, C went from host1, so that it would be like this afterwards
Node host1
- Contexts
- /test
- Aliases
- A, B, C
Node host2
- Contexts
- /other
- Aliases
- B, C
instead of the current behaviour
Node host1
- Context
- /test
- Aliases
- A, B
- Context
- /test
- Aliases
- B, C
Node host2
- Contexts
- /other
- Aliases
- B, C
Alright, so it seems we have come to a conclusion that replace is the correct action (instead of the proposed merge). I'll fix this PR once I fix the upstream. |
Or maybe not. In case of following configuration of tomcat <Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Alias>default.example.com</Alias>
</Host>
<Host name="testing" appBase="webapps-example"
unpackWARs="true" autoDeploy="true">
<Alias>default.example.com</Alias>
</Host> the merge seems the right way... |
in server.xml:
deploy demo-1.0.war in HostA... you have in mod_proxy_cluster Alias a, b. undeploy test.war in HostB.... you still have Alias a, b, c ... so c still has demo-1.0 which is wrong. |
Right, so we have multiple levels at which both the current state and the proposed fix are not working. 😄 I'll mark this as draft, we should think it through first. |
A partial fix went into upstream/main, so just make sure we don't forget to fix there too. 👍🏼 |
Another funny thing:
deploy demo-1.0 in Aapps, then in Bapps, wait and later undeploy demo-1.0 in Aapps, the VirtualHost is gone :-( I don't see how to handle this "configuration error"... |
gives an error in tomcat, as expected. |
Hm, but it gives an error due to Although thinking about it, maybe this is something to fix in tomcat directly, isn't it? |
Resolves MODCLUSTER-824
Opening as a draft since it's a backport.