We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ps -ef |grep "org.apache.flume.node.Application"|grep "apache-inlong-dataproxy"|grep -v grep|awk '{print $2}'|xargs kill -9
change from org.apache.flume.node.Application to org.apache.inlong.dataproxy.node.Application
sh bin/dataproxy-stop.sh ps -ef |grep "org.apache.flume.node.Application"|grep "apache-inlong-dataproxy"|grep -v grep|awk '{print $2}'|xargs kill -9
No response
0.10.0 RC1
InLong DataProxy
The text was updated successfully, but these errors were encountered:
EMsnap
Successfully merging a pull request may close this issue.
What happened
ps -ef |grep "org.apache.flume.node.Application"|grep "apache-inlong-dataproxy"|grep -v grep|awk '{print $2}'|xargs kill -9
![6128005a-4cd4-453b-8a76-e21f196950b5](https://user-images.githubusercontent.com/26538404/147563017-eddf9720-a90c-4222-bde3-f71576f7594b.png)
What you expected to happen
change from org.apache.flume.node.Application to org.apache.inlong.dataproxy.node.Application
How to reproduce
sh bin/dataproxy-stop.sh
![6128005a-4cd4-453b-8a76-e21f196950b5](https://user-images.githubusercontent.com/26538404/147563017-eddf9720-a90c-4222-bde3-f71576f7594b.png)
ps -ef |grep "org.apache.flume.node.Application"|grep "apache-inlong-dataproxy"|grep -v grep|awk '{print $2}'|xargs kill -9
Environment
No response
InLong version
0.10.0 RC1
InLong Component
InLong DataProxy
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: