Is there any way to determine what node an issue was created on, other than the JIRA logs?
Not unless you've configured something to capture it (outside the logs)
What problem would knowing this solve for you?
Thanks Nic! I figured as much upon further reading. It's more information for us since we integrate the issues from JIRA into downstream systems and know which node the issue was created on would help us with trouble shooting some data flows. It really wouldn't "solve" any problem for us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My choice of "problem" probably was quite a bad choice, sorry.
I can phrase "knowing where your data is flowing" as a perfectly good definition of a "problem to solve".
I've seen that done in three different ways very broadly:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks.. sorry for the late response. We don't have a very large DC, but still think that knocking out one node may be the only way to do this. And these calls aren't being initiated by humans, I suspect that upstream process is making a duplicate call but we're still trying to track that down. Thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.