Reactor: change Scheduler from elastic to worker
I have the pipeline like this (contextMono is Mono):
contextMono
.map(this::doLogic)
.map(this::doLogic1)
.flatMap(ctx -> Mono
.fromCallable(() -> doWithData(ctx))
.publishOn(Schedulers.elastic())
.map(this::buildReturnValue)
This pipeline executes in thread called like http-server-epoll-65 (epoll worker group). From flatMap executes in elastic's thread (because of publishOn(Schedulers.elastic())). This group (elastic) of threads uses for flatMap and for last map (buildReturnValue).
But I want buildReturnValue to be executed in group of epoll-workers threads (server-epoll-65 or other).
I do not want to use Schedulers.elastic() for non-I/O (blocking) tasks.
How I can change back to workers-epoll group of Schedulers?
java project-reactor
add a comment |
I have the pipeline like this (contextMono is Mono):
contextMono
.map(this::doLogic)
.map(this::doLogic1)
.flatMap(ctx -> Mono
.fromCallable(() -> doWithData(ctx))
.publishOn(Schedulers.elastic())
.map(this::buildReturnValue)
This pipeline executes in thread called like http-server-epoll-65 (epoll worker group). From flatMap executes in elastic's thread (because of publishOn(Schedulers.elastic())). This group (elastic) of threads uses for flatMap and for last map (buildReturnValue).
But I want buildReturnValue to be executed in group of epoll-workers threads (server-epoll-65 or other).
I do not want to use Schedulers.elastic() for non-I/O (blocking) tasks.
How I can change back to workers-epoll group of Schedulers?
java project-reactor
You could use publishOn after the flatMap but don't know how to retrieve the previous scheduler used before the flatMap.
– JEY
Nov 27 '18 at 12:31
@JEY yes, I know this trick, I can use publishOn(Schedulers.parallel()) but it is not good enough, because it will use extra threads.
– mchernyakov
Nov 27 '18 at 13:07
add a comment |
I have the pipeline like this (contextMono is Mono):
contextMono
.map(this::doLogic)
.map(this::doLogic1)
.flatMap(ctx -> Mono
.fromCallable(() -> doWithData(ctx))
.publishOn(Schedulers.elastic())
.map(this::buildReturnValue)
This pipeline executes in thread called like http-server-epoll-65 (epoll worker group). From flatMap executes in elastic's thread (because of publishOn(Schedulers.elastic())). This group (elastic) of threads uses for flatMap and for last map (buildReturnValue).
But I want buildReturnValue to be executed in group of epoll-workers threads (server-epoll-65 or other).
I do not want to use Schedulers.elastic() for non-I/O (blocking) tasks.
How I can change back to workers-epoll group of Schedulers?
java project-reactor
I have the pipeline like this (contextMono is Mono):
contextMono
.map(this::doLogic)
.map(this::doLogic1)
.flatMap(ctx -> Mono
.fromCallable(() -> doWithData(ctx))
.publishOn(Schedulers.elastic())
.map(this::buildReturnValue)
This pipeline executes in thread called like http-server-epoll-65 (epoll worker group). From flatMap executes in elastic's thread (because of publishOn(Schedulers.elastic())). This group (elastic) of threads uses for flatMap and for last map (buildReturnValue).
But I want buildReturnValue to be executed in group of epoll-workers threads (server-epoll-65 or other).
I do not want to use Schedulers.elastic() for non-I/O (blocking) tasks.
How I can change back to workers-epoll group of Schedulers?
java project-reactor
java project-reactor
edited Nov 27 '18 at 12:13
Nicholas K
7,33661536
7,33661536
asked Nov 27 '18 at 11:15
mchernyakovmchernyakov
4616
4616
You could use publishOn after the flatMap but don't know how to retrieve the previous scheduler used before the flatMap.
– JEY
Nov 27 '18 at 12:31
@JEY yes, I know this trick, I can use publishOn(Schedulers.parallel()) but it is not good enough, because it will use extra threads.
– mchernyakov
Nov 27 '18 at 13:07
add a comment |
You could use publishOn after the flatMap but don't know how to retrieve the previous scheduler used before the flatMap.
– JEY
Nov 27 '18 at 12:31
@JEY yes, I know this trick, I can use publishOn(Schedulers.parallel()) but it is not good enough, because it will use extra threads.
– mchernyakov
Nov 27 '18 at 13:07
You could use publishOn after the flatMap but don't know how to retrieve the previous scheduler used before the flatMap.
– JEY
Nov 27 '18 at 12:31
You could use publishOn after the flatMap but don't know how to retrieve the previous scheduler used before the flatMap.
– JEY
Nov 27 '18 at 12:31
@JEY yes, I know this trick, I can use publishOn(Schedulers.parallel()) but it is not good enough, because it will use extra threads.
– mchernyakov
Nov 27 '18 at 13:07
@JEY yes, I know this trick, I can use publishOn(Schedulers.parallel()) but it is not good enough, because it will use extra threads.
– mchernyakov
Nov 27 '18 at 13:07
add a comment |
0
active
oldest
votes
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%2f53498456%2freactor-change-scheduler-from-elastic-to-worker%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53498456%2freactor-change-scheduler-from-elastic-to-worker%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
You could use publishOn after the flatMap but don't know how to retrieve the previous scheduler used before the flatMap.
– JEY
Nov 27 '18 at 12:31
@JEY yes, I know this trick, I can use publishOn(Schedulers.parallel()) but it is not good enough, because it will use extra threads.
– mchernyakov
Nov 27 '18 at 13:07