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

mlaccetti 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.

Show comment
Hide comment
@smsiebe

smsiebe Apr 25, 2012

+1 this would be a cool feature.

smsiebe commented Apr 25, 2012

+1 this would be a cool feature.

@Treydone

This comment has been minimized.

Show comment
Hide comment
@Treydone

Treydone Jun 1, 2012

+1, it could be really nice!

Treydone commented Jun 1, 2012

+1, it could be really nice!

@micklev

This comment has been minimized.

Show comment
Hide comment
@micklev

micklev Aug 16, 2012

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

micklev commented Aug 16, 2012

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

@chen56

This comment has been minimized.

Show comment
Hide comment
@chen56

chen56 Sep 3, 2012

+1, waiting this feature

chen56 commented Sep 3, 2012

+1, waiting this feature

@fandayrockworld

This comment has been minimized.

Show comment
Hide comment
@fandayrockworld

fandayrockworld Sep 11, 2012

+n, this is necessarily

fandayrockworld commented Sep 11, 2012

+n, this is necessarily

@ejain

This comment has been minimized.

Show comment
Hide comment
@ejain

ejain Nov 7, 2012

+1, this would be a killer feature.

ejain commented Nov 7, 2012

+1, this would be a killer feature.

@antoine-galataud

This comment has been minimized.

Show comment
Hide comment
@antoine-galataud

antoine-galataud commented Aug 28, 2013

+1

@jeromebenois

This comment has been minimized.

Show comment
Hide comment
@jeromebenois

jeromebenois commented Sep 13, 2013

+1

@alexsyd

This comment has been minimized.

Show comment
Hide comment
@alexsyd

alexsyd Sep 18, 2013

+1, it's required by my current project

alexsyd commented Sep 18, 2013

+1, it's required by my current project

@imhazige

This comment has been minimized.

Show comment
Hide comment
@imhazige

imhazige May 15, 2014

+1, I am looking for it.

imhazige 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.

Show comment
Hide comment
@mdogan

mdogan May 16, 2014

Member

ScheduledExecutorService is going to be introduced in version 3.4.

Member

mdogan commented May 16, 2014

ScheduledExecutorService is going to be introduced in version 3.4.

@logemann

This comment has been minimized.

Show comment
Hide comment
@logemann

logemann May 16, 2014

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

logemann commented May 16, 2014

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

@peruzzo

This comment has been minimized.

Show comment
Hide comment
@peruzzo

peruzzo commented May 29, 2014

+1

@pratik-patel

This comment has been minimized.

Show comment
Hide comment
@pratik-patel

pratik-patel Jul 29, 2014

+1 it is really a useful feature

pratik-patel commented Jul 29, 2014

+1 it is really a useful feature

@mhurne

This comment has been minimized.

Show comment
Hide comment
@mhurne

mhurne Sep 15, 2014

Looking forward to a distributed ScheduledExecutorService!

mhurne 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.

Show comment
Hide comment
@bwzhang2011

bwzhang2011 Oct 30, 2014

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

bwzhang2011 commented Oct 30, 2014

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

@mateo41

This comment has been minimized.

Show comment
Hide comment
@mateo41

mateo41 commented Nov 17, 2014

+1

@jamesmmchugh

This comment has been minimized.

Show comment
Hide comment
@jamesmmchugh

jamesmmchugh commented Nov 20, 2014

+1

@enesakar

This comment has been minimized.

Show comment
Hide comment
@enesakar

enesakar Nov 20, 2014

Member

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

Member

enesakar 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.

Show comment
Hide comment
@gurbuzali

gurbuzali Nov 26, 2014

Member

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

Member

gurbuzali 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.

Show comment
Hide comment
@bwzhang2011

bwzhang2011 Dec 6, 2014

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

bwzhang2011 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.

Show comment
Hide comment
@mhurne

mhurne 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. :-/

mhurne 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.

Show comment
Hide comment
@jamesmmchugh

jamesmmchugh 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.

jamesmmchugh 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.

Show comment
Hide comment
@isaeedm

isaeedm Jan 25, 2015

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

isaeedm 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.

Show comment
Hide comment
@sertugkaya

sertugkaya commented Oct 28, 2015

+1

@Petikoch

This comment has been minimized.

Show comment
Hide comment
@Petikoch

Petikoch commented Dec 9, 2015

+1

@edoparo

This comment has been minimized.

Show comment
Hide comment
@edoparo

edoparo commented Feb 2, 2016

+1

@logemann

This comment has been minimized.

Show comment
Hide comment
@logemann

logemann Feb 17, 2016

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

logemann commented Feb 17, 2016

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

@sertugkaya

This comment has been minimized.

Show comment
Hide comment
@sertugkaya

sertugkaya Feb 17, 2016

@logemann it has a milestone set for 3.7

sertugkaya commented Feb 17, 2016

@logemann it has a milestone set for 3.7

@marcolattarulo

This comment has been minimized.

Show comment
Hide comment
@marcolattarulo

marcolattarulo commented Feb 23, 2016

+1

@olivergg

This comment has been minimized.

Show comment
Hide comment
@olivergg

olivergg commented Feb 25, 2016

+1

@drshriveer

This comment has been minimized.

Show comment
Hide comment
@drshriveer

drshriveer commented Mar 29, 2016

+1

@mikemainguy

This comment has been minimized.

Show comment
Hide comment
@mikemainguy

mikemainguy commented Apr 11, 2016

+1

@danfink

This comment has been minimized.

Show comment
Hide comment
@danfink

danfink commented Apr 11, 2016

+1

@JAC2703

This comment has been minimized.

Show comment
Hide comment
@JAC2703

JAC2703 commented Apr 22, 2016

+1

@wneild

This comment has been minimized.

Show comment
Hide comment
@wneild

wneild commented Apr 25, 2016

+1

@tommagowan

This comment has been minimized.

Show comment
Hide comment
@tommagowan

tommagowan commented May 13, 2016

+1

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

@cristcost

This comment has been minimized.

Show comment
Hide comment
@cristcost

cristcost 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...)

cristcost 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.

Show comment
Hide comment
@jerrinot

jerrinot May 23, 2016

Contributor

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.

Contributor

jerrinot 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.

Show comment
Hide comment
@kfatih

kfatih commented May 25, 2016

+1

@liefra

This comment has been minimized.

Show comment
Hide comment
@liefra

liefra commented May 31, 2016

+1

@MatthiasGerth

This comment has been minimized.

Show comment
Hide comment
@MatthiasGerth

MatthiasGerth commented Jun 6, 2016

+1

@bjoernw

This comment has been minimized.

Show comment
Hide comment
@bjoernw

bjoernw commented Sep 12, 2016

+1

@dasbh

This comment has been minimized.

Show comment
Hide comment
@dasbh

dasbh commented Oct 12, 2016

+1

@pedrohsd

This comment has been minimized.

Show comment
Hide comment
@pedrohsd

pedrohsd commented Oct 21, 2016

+1

@lucasmogari

This comment has been minimized.

Show comment
Hide comment
@lucasmogari

lucasmogari commented Nov 15, 2016

+1

@oksyque

This comment has been minimized.

Show comment
Hide comment
@oksyque

oksyque commented Nov 16, 2016

+1

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

@jerrinot

This comment has been minimized.

Show comment
Hide comment
@jerrinot

jerrinot Dec 6, 2016

Contributor

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.

Contributor

jerrinot 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.

Show comment
Hide comment
@cristcost

cristcost Dec 7, 2016

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

cristcost commented Dec 7, 2016

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

@jerrinot

This comment has been minimized.

Show comment
Hide comment
@jerrinot

jerrinot Dec 7, 2016

Contributor

all the credits go to @tkountis ;-)

Contributor

jerrinot 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