https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #23 from Remy Maucherat ---
(In reply to Diego Rivera from comment #22)
> (In reply to Diego Rivera from comment #21)
> >>channelStartOptions="3"
> >channelSendOptions="8">
>
> Apparently tho
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
Diego Rivera changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #21 from Diego Rivera ---
(In reply to romain.manni-bucau from comment #16)
So... I tried to configure the K8s provider as per the docs, and other
resources I found (https://github.com/devlinx9/k8s_tomcat_custer). Per those
resour
All,
On 6/21/23 13:14, bugzi...@apache.org wrote:
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #20 from Diego Rivera ---
(In reply to romain.manni-bucau from comment #16)
Sounds like what you want is to start the cluster only after which means you
assume that none of the N
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #20 from Diego Rivera ---
(In reply to romain.manni-bucau from comment #16)
> Sounds like what you want is to start the cluster only after which means you
> assume that none of the N-1 pods serve anything before pod N is started.
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #19 from Diego Rivera ---
(In reply to jfclere from comment #17)
> I need the pod.yaml and the service.yaml you are using, otherwise it is just
> guessing.
Trust me, they wouldn't make a difference.
Services are designed to be bla
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #18 from jfclere ---
Try https://github.com/jfclere/DNSPing-tomcat too
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe,
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #17 from jfclere ---
I need the pod.yaml and the service.yaml you are using, otherwise it is just
guessing.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #16 from romain.manni-bucau ---
Sounds like what you want is to start the cluster only after which means you
assume that none of the N-1 pods serve anything before pod N is started.
Think this is a high assumptiong for tomcat.
If n
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #15 from Diego Rivera ---
To clarify re: the Service only returning its own IP.
In K8s, the pods behind the Service facade may change at any time, and without
warning. DNS caches are also a thing. So imagine this scenario: from you
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
Diego Rivera changed:
What|Removed |Added
Resolution|WONTFIX |---
Status|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=0
--- Comment #13 from jfclere ---
The DNS service and the logic in tomcat cluster expects the pods to be ready
otherwise the whole stuff is useless.
The lookup is done on the service which returns all the available pods
Probably your problems ar
sheikhoo commented on PR #628:
URL: https://github.com/apache/tomcat/pull/628#issuecomment-1601089024
> Please provide an updated screenshot showing the results of all your
changes as there have been additional changes since the PR was opened.
This is screenshot of last change
