[
https://issues.apache.org/jira/browse/CASSANDRA-16057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198157#comment-17198157
]
Stefan Miklosovic commented on CASSANDRA-16057:
-----------------------------------------------
[~ifesdjeen] [~yifanc]
I have implemented this here https://github.com/apache/cassandra/pull/711/files
If you go over that PR you will see what I mean. Maybe that one might go in
instead? Anyway, I like the idea this would be directly in dtest api, we had an
intention to add it there _sometimes_ as I do not have time to do that so if
we do it _the proper way_ and I can reuse it in my PR, that would be awesome.
We are just exposing there stdout and stderr. Please keep in mind that I need
to do this _against an instance_, meaning I need to be able to do it such way
that it will be executed in the "scope" of that node because I can spin up more
clusters and I need to have "stdout" per each "jvm / classloader".
If all this is met, we might reuse whatever solution but please keep in mind
that I would love to merge 15406 very soon because it was there literally for
months and it was blocked by few other tickets so I am personally little
impatient here :)
Looking forward to have a feedback.
> Should update in-jvm dtest to expose stdout and stderr for nodetool
> -------------------------------------------------------------------
>
> Key: CASSANDRA-16057
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16057
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/java
> Reporter: David Capwell
> Assignee: Yifan Cai
> Priority: Normal
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Many nodetool commands output to stdout or stderr so running nodetool using
> in-jvm dtest should expose that to tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
