Apache Storm - LocalCluster stopped logging but java process still running
We are running a LocalCluster of Apache Storm as a java process i.e via nohup.
We are running a simple Topology with following configuration.
Config config = new Config();
config.setMessageTimeoutSecs(120);
config.setNumWorkers(1);
config.setDebug(false);
config.setMaxSpoutPending(1);
We are submitting the Topology to LocalCluster. Our shutdown hook is the default one found across sources.
Runtime.getRuntime().addShutdownHook(new Thread() {
@Override
public void run() {
cluster.killTopology(TOPOLOGY_NAME);
cluster.shutdown();
}
});
Lately we were facing Java Heap issues which might have been solved by increasing Xms, Xmx and using MarkSweepGC.
However, we are running into new problem. The spout logs are not being written to after sometime. There will be no trace of any storm relate Exception/Error.
The main problem is the java process i.e. via nohup is still showing up in ps -ef. What issue would be happening?
java apache-storm nohup
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
add a comment |
We are running a LocalCluster of Apache Storm as a java process i.e via nohup.
We are running a simple Topology with following configuration.
Config config = new Config();
config.setMessageTimeoutSecs(120);
config.setNumWorkers(1);
config.setDebug(false);
config.setMaxSpoutPending(1);
We are submitting the Topology to LocalCluster. Our shutdown hook is the default one found across sources.
Runtime.getRuntime().addShutdownHook(new Thread() {
@Override
public void run() {
cluster.killTopology(TOPOLOGY_NAME);
cluster.shutdown();
}
});
Lately we were facing Java Heap issues which might have been solved by increasing Xms, Xmx and using MarkSweepGC.
However, we are running into new problem. The spout logs are not being written to after sometime. There will be no trace of any storm relate Exception/Error.
The main problem is the java process i.e. via nohup is still showing up in ps -ef. What issue would be happening?
java apache-storm nohup
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
add a comment |
We are running a LocalCluster of Apache Storm as a java process i.e via nohup.
We are running a simple Topology with following configuration.
Config config = new Config();
config.setMessageTimeoutSecs(120);
config.setNumWorkers(1);
config.setDebug(false);
config.setMaxSpoutPending(1);
We are submitting the Topology to LocalCluster. Our shutdown hook is the default one found across sources.
Runtime.getRuntime().addShutdownHook(new Thread() {
@Override
public void run() {
cluster.killTopology(TOPOLOGY_NAME);
cluster.shutdown();
}
});
Lately we were facing Java Heap issues which might have been solved by increasing Xms, Xmx and using MarkSweepGC.
However, we are running into new problem. The spout logs are not being written to after sometime. There will be no trace of any storm relate Exception/Error.
The main problem is the java process i.e. via nohup is still showing up in ps -ef. What issue would be happening?
java apache-storm nohup
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
We are running a LocalCluster of Apache Storm as a java process i.e via nohup.
We are running a simple Topology with following configuration.
Config config = new Config();
config.setMessageTimeoutSecs(120);
config.setNumWorkers(1);
config.setDebug(false);
config.setMaxSpoutPending(1);
We are submitting the Topology to LocalCluster. Our shutdown hook is the default one found across sources.
Runtime.getRuntime().addShutdownHook(new Thread() {
@Override
public void run() {
cluster.killTopology(TOPOLOGY_NAME);
cluster.shutdown();
}
});
Lately we were facing Java Heap issues which might have been solved by increasing Xms, Xmx and using MarkSweepGC.
However, we are running into new problem. The spout logs are not being written to after sometime. There will be no trace of any storm relate Exception/Error.
The main problem is the java process i.e. via nohup is still showing up in ps -ef. What issue would be happening?
java apache-storm nohup
java apache-storm nohup
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
asked Nov 23 '18 at 6:36
CS_noobCS_noob
4571313
4571313
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can try enabling debug logging with config.setDebug(true);, which might let you tell what is happening.
Also next time your topology hangs, you should be able to tell what it's doing by either using jstack or sending the Java process a SIGQUIT (kill -3). This will cause the process to dump stack traces for each thread in the JVM, which should let you figure out why it's hanging.
As an aside in case you're doing it, please don't use LocalCluster in production. It's intended for testing.
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53441688%2fapache-storm-localcluster-stopped-logging-but-java-process-still-running%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can try enabling debug logging with config.setDebug(true);, which might let you tell what is happening.
Also next time your topology hangs, you should be able to tell what it's doing by either using jstack or sending the Java process a SIGQUIT (kill -3). This will cause the process to dump stack traces for each thread in the JVM, which should let you figure out why it's hanging.
As an aside in case you're doing it, please don't use LocalCluster in production. It's intended for testing.
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
add a comment |
You can try enabling debug logging with config.setDebug(true);, which might let you tell what is happening.
Also next time your topology hangs, you should be able to tell what it's doing by either using jstack or sending the Java process a SIGQUIT (kill -3). This will cause the process to dump stack traces for each thread in the JVM, which should let you figure out why it's hanging.
As an aside in case you're doing it, please don't use LocalCluster in production. It's intended for testing.
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
add a comment |
You can try enabling debug logging with config.setDebug(true);, which might let you tell what is happening.
Also next time your topology hangs, you should be able to tell what it's doing by either using jstack or sending the Java process a SIGQUIT (kill -3). This will cause the process to dump stack traces for each thread in the JVM, which should let you figure out why it's hanging.
As an aside in case you're doing it, please don't use LocalCluster in production. It's intended for testing.
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
You can try enabling debug logging with config.setDebug(true);, which might let you tell what is happening.
Also next time your topology hangs, you should be able to tell what it's doing by either using jstack or sending the Java process a SIGQUIT (kill -3). This will cause the process to dump stack traces for each thread in the JVM, which should let you figure out why it's hanging.
As an aside in case you're doing it, please don't use LocalCluster in production. It's intended for testing.
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
answered Nov 23 '18 at 13:08
Stig Rohde DøssingStig Rohde Døssing
1,881235
1,881235
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53441688%2fapache-storm-localcluster-stopped-logging-but-java-process-still-running%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
