[
https://issues.apache.org/jira/browse/ACCUMULO-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137760#comment-14137760
]
Josh Elser commented on ACCUMULO-3139:
--------------------------------------
The downside here is that we have to reflect to get at the pid inside of
UNIXProcess, but I don't think that's the end of the world. We could exec out
to some bash to try to guess, but that would be error prone too.
> BalanceAfterCommsFailureIT alters other tservers on the system
> --------------------------------------------------------------
>
> Key: ACCUMULO-3139
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3139
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.6.1, 1.7.0
>
>
> BalanceAfterCommsFailureIT does a SIGSTOP and then SIGCONT to simulate some
> network outage. It uses pkill to send the signals which will send that to any
> processes on the system matching "TabletServer".
> This isn't really ideal (and I believe is actually error prone if there is a
> TabletServer running on the same node by a different user). Figuring out a
> way to target only the TabletServers running in the minicluster for this test
> is much better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
