Skip to content
New issue

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

Add support for ScheduledExecutorService #115

Closed
mlaccetti opened this issue Apr 6, 2012 · 63 comments

Comments

Projects
None yet
@mlaccetti
Copy link

commented Apr 6, 2012

Would be delightful to be able to use a distributed ScheduledExecutorService that could guarantee execution of something across a cluster, on each node, etc, etc.

@smsiebe

This comment has been minimized.

Copy link

commented Apr 25, 2012

+1 this would be a cool feature.

@Treydone

This comment has been minimized.

Copy link

commented Jun 1, 2012

+1, it could be really nice!

@micklev

This comment has been minimized.

Copy link

commented Aug 16, 2012

+1, it's already required by my current project

@chen56

This comment has been minimized.

Copy link

commented Sep 3, 2012

+1, waiting this feature

@fandayrockworld

This comment has been minimized.

Copy link

commented Sep 11, 2012

+n, this is necessarily

@ejain

This comment has been minimized.

Copy link

commented Nov 7, 2012

+1, this would be a killer feature.

@antoine-galataud

This comment has been minimized.

Copy link

commented Aug 28, 2013

+1

@jeromebenois

This comment has been minimized.

Copy link

commented Sep 13, 2013

+1

@alexsyd

This comment has been minimized.

Copy link

commented Sep 18, 2013

+1, it's required by my current project

@imhazige

This comment has been minimized.

Copy link

commented May 15, 2014

+1, I am looking for it.

@mdogan mdogan added the 3.x label May 16, 2014

@mdogan mdogan added this to the 3.++ milestone May 16, 2014

@mdogan

This comment has been minimized.

Copy link
Member

commented May 16, 2014

ScheduledExecutorService is going to be introduced in version 3.4.

@logemann

This comment has been minimized.

Copy link

commented May 16, 2014

+1 will use it right away when its there....

@peruzzo

This comment has been minimized.

Copy link

commented May 29, 2014

+1

@pratik-patel

This comment has been minimized.

Copy link

commented Jul 29, 2014

+1 it is really a useful feature

@mhurne

This comment has been minimized.

Copy link

commented Sep 15, 2014

Looking forward to a distributed ScheduledExecutorService!

@ajermakovics ajermakovics added Team: Core and removed Team: Core labels Oct 14, 2014

@bwzhang2011

This comment has been minimized.

Copy link

commented Oct 30, 2014

@mdogan, will HZ 3.4 add the support for ScheduledExecutorService ?

@mateo41

This comment has been minimized.

Copy link

commented Nov 17, 2014

+1

1 similar comment
@jamesmmchugh

This comment has been minimized.

Copy link

commented Nov 20, 2014

+1

@enesakar

This comment has been minimized.

Copy link
Member

commented Nov 20, 2014

It is too late for 3.4 but I will talk with team if we can do it for 3.5

@gurbuzali

This comment has been minimized.

Copy link
Member

commented Nov 26, 2014

here is a non-production scheduled-executor which I've implemented using Hazelcast SPI
https://github.com/gurbuzali/scheduled-executor/wiki

@bwzhang2011

This comment has been minimized.

Copy link

commented Dec 6, 2014

@gurbuzali , it's better to make more integration work just like some efforts with quartz for distribute schedule implementation.

@mhurne

This comment has been minimized.

Copy link

commented Dec 6, 2014

Indeed, a HazelcastJobStore would be handy! I considered working on one in the past, but was intimidated by what I saw when I looked at TerracottaJobStore. :-/

@jamesmmchugh

This comment has been minimized.

Copy link

commented Dec 7, 2014

@mhurne Very true, I tried the same but that interface is a mess. Also tried looking at some of the provided implementations - also a complete mess.

@isaeedm

This comment has been minimized.

Copy link

commented Jan 25, 2015

+1
Is this feature going to be released with Hazelcast 3.5? if yes when will 3.5 be released?

@sertugkaya

This comment has been minimized.

Copy link

commented Oct 28, 2015

+1

2 similar comments
@Petikoch

This comment has been minimized.

Copy link

commented Dec 9, 2015

+1

@edoparo

This comment has been minimized.

Copy link

commented Feb 2, 2016

+1

@logemann

This comment has been minimized.

Copy link

commented Feb 17, 2016

it was on the radar a year ago and now its dropped?

@sertugkaya

This comment has been minimized.

Copy link

commented Feb 17, 2016

@logemann it has a milestone set for 3.7

@marcolattarulo

This comment has been minimized.

Copy link

commented Feb 23, 2016

+1

7 similar comments
@olivergg

This comment has been minimized.

Copy link

commented Feb 25, 2016

+1

@drshriveer

This comment has been minimized.

Copy link

commented Mar 29, 2016

+1

@mikemainguy

This comment has been minimized.

Copy link

commented Apr 11, 2016

+1

@danfink

This comment has been minimized.

Copy link

commented Apr 11, 2016

+1

@JAC2703

This comment has been minimized.

Copy link

commented Apr 22, 2016

+1

@wneild

This comment has been minimized.

Copy link

commented Apr 25, 2016

+1

@tommagowan

This comment has been minimized.

Copy link

commented May 13, 2016

+1

@jerrinot jerrinot modified the milestones: 3.8, 3.7 May 23, 2016

@cristcost

This comment has been minimized.

Copy link

commented May 23, 2016

Hi all,
may I ask you please why this feature is being delayed since 4 years?
Is there any technical problem in implementing it or nobody care?
Or maybe it exist a workaround to schedule execution of Runnable etc. with a delay on an Hazelcast Cluster?

anyway, +1 also for me

(please note the irony: I've discovered the issue just now, "one hour" after it has been postponed again to the next release...)

@jerrinot

This comment has been minimized.

Copy link
Contributor

commented May 23, 2016

Hi @cristcost:

it's easy to implement the happy scenario. However things can become very hairy when you have members joining&leaving a cluster. We are now on the edge of the feature-freeze for 3.7 hence it's not possible to have in this release.

That being said there is VERY visible interest in this feature and I hope to have this included in Hazelcast 3.8 plans.

@kfatih

This comment has been minimized.

Copy link

commented May 25, 2016

+1

5 similar comments
@liefra

This comment has been minimized.

Copy link

commented May 31, 2016

+1

@MatthiasGerth

This comment has been minimized.

Copy link

commented Jun 6, 2016

+1

@bjoernw

This comment has been minimized.

Copy link

commented Sep 12, 2016

+1

@dasbh

This comment has been minimized.

Copy link

commented Oct 12, 2016

+1

@pedrohsd

This comment has been minimized.

Copy link

commented Oct 21, 2016

+1

@lucasmogari

This comment has been minimized.

Copy link

commented Nov 15, 2016

+1

1 similar comment
@oksyque

This comment has been minimized.

Copy link

commented Nov 16, 2016

+1

@tkountis tkountis closed this in 4c046c7 Dec 5, 2016

@jerrinot

This comment has been minimized.

Copy link
Contributor

commented Dec 6, 2016

ScheduledExecutorService is available in the latest snapshot version.

It'll be also included in the Hazelcast 3.8 Early Access which should be released very soon.

@cristcost

This comment has been minimized.

Copy link

commented Dec 7, 2016

Already noted the issue was closed yesterday,
thank you very much!

@jerrinot

This comment has been minimized.

Copy link
Contributor

commented Dec 7, 2016

all the credits go to @tkountis ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.