[jira] [Comment Edited] (TIKA-3210) tika status endpoint should have a Node UUID

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Comment Edited] (TIKA-3210) tika status endpoint should have a Node UUID

Nicholas DiPiazza (Jira)

    [ https://issues.apache.org/jira/browse/TIKA-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215611#comment-17215611 ]

Nicholas DiPiazza edited comment on TIKA-3210 at 10/16/20, 7:19 PM:
--------------------------------------------------------------------

> don't you know which server you're talking to based on port and address?
no in kubernetes I'm hitting a load balancer which is hiding it from me. the remote address is always the load balancer, and the status json output has no indication what server i'm talking to.

> And next question... the UUID should be tied to the parent process, not the child process, right?
Yeah I think the parent process would be ideal.


was (Author: ndipiazza_gmail):
> don't you know which server you're talking to based on port and address?
no in kubernetes I'm hitting a load balancer which is hiding it from me. the remote address is always the load balancer, and the status json output has no indication what server i'm talking to.

> And next question... the UUID should be tied to the parent process, not the child process, right?
Yeah I think the parent process would be idea.

> tika status endpoint should have a Node UUID
> ---------------------------------------------
>
>                 Key: TIKA-3210
>                 URL: https://issues.apache.org/jira/browse/TIKA-3210
>             Project: Tika
>          Issue Type: Improvement
>          Components: server
>            Reporter: Nicholas DiPiazza
>            Priority: Minor
>
> when you call {{/status}}
> it should have a Node UUID or something. this would be useful when load balancing and you want to prove load is distributing appropriately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)