Skip to content

Commit

Permalink
Merge pull request #1 from DmitriySh/develop
Browse files Browse the repository at this point in the history 
merge from develop
  • Loading branch information
@DmitriySh
DmitriySh authored Mar 21, 2017
2 parents af95976 + f9d560c commit bd01967
Show file tree
Hide file tree
Showing 49 changed files with 2,522 additions and 31 deletions.
14 changes: 10 additions & 4 deletions .gitignore
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,3 @@
# Java class files
*.class

# MacOS
*.DS_Store

Expand All @@ -16,10 +13,10 @@
*.ipr

# Maven
log/
target/

# Gradle
!/gradle/wrapper/gradle-wrapper.jar
.gradle/
*/build/
out/
Expand All @@ -31,3 +28,12 @@ out/

# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
hs_err_pid*


# Project files
*.class
*/performance*.log
performance*.log
*/logs/
logs/

260 changes: 258 additions & 2 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,261 @@
time-hz-executor
=======

My pet project.
This is a prototype of multithreaded service executes incoming tasks on a schedule time.
My pet project.
This is a prototype of multithreaded and distributed service executes incoming tasks on a scheduled time. Powered by: `Java SE`, `Guice` and `Hazelcast`. Project uses SEDA like highly customizable thread model: independent tasks to use producers, consumers and queue, distributed map between them.


## Rules:

![export-2](https://cloud.githubusercontent.com/assets/4469702/24129401/85e05708-0df3-11e7-8dd0-17f8bbb1e12e.png)

* The cluster of Hazelcast nodes accepts tasks with `LocalDateTime` and `Callable<?>`.
* `LocalDateTime` is a scheduled time and `Callable<?>` is a task for execution on that time.
* Order of the execution uses scheduled time or number of inbound order.
* Tasks could comes in a random order
* 'Hot' tasks should not waste time and executes immediately.


## Requirements:

* Java SE Development Kit 8 (or newer)
* Gradle 2.x (or you could use Gradle wrapper)


## Project configuration:

* Java SE should be installed and you need to set path variable for `JAVA_HOME`.
* Gradle doesn't need to install because you might do this automatically thanks Gradle Wrapper.


## Run

* Build project. Go to the root path `/time-hz-executor/` of the project and run:
```sh
time-hz-executor$ ./gradlew clean build
Version 0.1
:client-cli:clean UP-TO-DATE
:hz-node:clean UP-TO-DATE
:shared:clean UP-TO-DATE
:shared:compileJava
:shared:processResources
:shared:classes
:shared:jar
:client-cli:compileJava
:client-cli:processResources
:client-cli:classes
:client-cli:jar
:client-cli:assemble
:client-cli:compileTestJava NO-SOURCE
:client-cli:processTestResources NO-SOURCE
:client-cli:testClasses UP-TO-DATE
:client-cli:test NO-SOURCE
:client-cli:check UP-TO-DATE
:client-cli:build
:hz-node:compileJava
:hz-node:processResources
:hz-node:classes
:hz-node:jar
:hz-node:assemble
:hz-node:compileTestJava NO-SOURCE
:hz-node:processTestResources NO-SOURCE
:hz-node:testClasses UP-TO-DATE
:hz-node:test NO-SOURCE
:hz-node:check UP-TO-DATE
:hz-node:build
:shared:assemble
:shared:compileTestJava
:shared:processTestResources NO-SOURCE
:shared:testClasses
:shared:test
:shared:check
:shared:build

BUILD SUCCESSFUL

Total time: 5.176 secs

```
* Run Hazelcast cluster:
```sh
time-hz-executor/scripts$ ./start_hz_cluster.sh

... <cut> ...

05:43:37.025 [main] INFO r.s.c.ThreadPoolBuilder - create thread pool: node.executor, threads [8..32], idleTime: 60 SECONDS, queue: SynchronousQueue []
05:43:37.094 [main] INFO r.s.c.Node - ----- // ----- Node: 1 START 2017-03-21T05:43:37.093 ----- // -----
05:43:37.096 [node-hz-1] INFO r.s.c.Node - Node: 1 starting...
05:43:37.096 [node-hz-1] INFO r.s.c.ServiceController - Node:1 services starting...
05:43:37.096 [node-main-1] INFO r.s.c.Node - Node: 1 thread: Thread[node-main-1,5,main] await the state: IDLE to stop itself
05:43:37.097 [node-main-1] DEBUG r.s.c.Node - Thread: Thread[node-main-1,5,main] is alive
05:43:37.118 [node-hz-1] INFO r.s.h.HzService - Hz server service starting...
05:43:37.120 [node-hz-1] DEBUG r.s.h.HzBuilder - Load HZ server instance...
мар 21, 2017 5:43:37 AM com.hazelcast.config.ClasspathXmlConfig
INFO: Configuring Hazelcast from 'hazelcast.xml'.
05:43:37.197 [main] INFO r.s.c.ThreadPoolBuilder - create thread pool: node.executor, threads [8..32], idleTime: 60 SECONDS, queue: SynchronousQueue []
05:43:37.284 [main] INFO r.s.c.Node - ----- // ----- Node: 2 START 2017-03-21T05:43:37.284 ----- // -----
05:43:37.290 [node-hz-2] INFO r.s.c.Node - Node: 2 starting...
05:43:37.291 [node-hz-2] INFO r.s.c.ServiceController - Node:2 services starting...
05:43:37.291 [node-main-2] INFO r.s.c.Node - Node: 2 thread: Thread[node-main-2,5,main] await the state: IDLE to stop itself
05:43:37.291 [node-main-2] DEBUG r.s.c.Node - Thread: Thread[node-main-2,5,main] is alive
05:43:37.312 [node-hz-2] INFO r.s.h.HzService - Hz server service starting...
05:43:37.315 [node-hz-2] DEBUG r.s.h.HzBuilder - Load HZ server instance...
мар 21, 2017 5:43:37 AM com.hazelcast.config.ClasspathXmlConfig
INFO: Configuring Hazelcast from 'hazelcast.xml'.
05:43:37.412 [main] INFO r.s.c.ThreadPoolBuilder - create thread pool: node.executor, threads [8..32], idleTime: 60 SECONDS, queue: SynchronousQueue []
05:43:37.542 [main] INFO r.s.c.Node - ----- // ----- Node: 3 START 2017-03-21T05:43:37.542 ----- // -----
05:43:37.545 [node-hz-3] INFO r.s.c.Node - Node: 3 starting...
05:43:37.546 [node-hz-3] INFO r.s.c.ServiceController - Node:3 services starting...
05:43:37.546 [node-main-3] INFO r.s.c.Node - Node: 3 thread: Thread[node-main-3,5,main] await the state: IDLE to stop itself

... <cut> ...

Members [3] {
Member [127.0.0.1]:5701
Member [127.0.0.1]:5702
Member [127.0.0.1]:5703 this
}

05:43:50.659 [node-hz-1] INFO c.h.p.InternalPartitionService - [127.0.0.1]:5701 [dev-node-hz] [3.6.7] Initializing cluster partition table arrangement...
05:43:50.670 [node-hz-1] INFO c.h.i.HazelcastInstanceImpl - [127.0.0.1]:5701 [dev-node-hz] [3.6.7] HazelcastInstance starting after waiting for cluster size of 2
05:43:50.670 [node-hz-1] INFO c.h.c.LifecycleService - [127.0.0.1]:5701 [dev-node-hz] [3.6.7] Address[127.0.0.1]:5701 is STARTED
05:43:50.670 [node-hz-1] INFO r.s.h.HzService - Hz server service started
05:43:50.671 [node-hz-1] INFO r.s.c.TaskTimeService - TaskTimeService Node:1 starting...
05:43:50.675 [node-hz-1] INFO r.s.c.TaskTimeService - TaskTimeService Node:1 started
05:43:50.676 [node-hz-1] INFO r.s.c.ServiceController - Listener: Node:1 has started all services -->
05:43:50.676 [node-hz-1] INFO r.s.c.ServiceController - Node:1 services started, state: RUN
05:43:50.681 [node-hz-1] INFO r.s.c.Node - Node: 1 started, state: RUN

... <cut> ...

```
* The same log you could see in the files in current directory:
```
time-hz-executor/scripts$ tree ./logs/
./logs/
└── node.log
0 directories, 1 file
```
* Run Hazelcast client:
```sh

... <cut> ...

INFO: HazelcastClient[hz.client_0_dev-node-hz][3.6.7] is STARTED
мар 21, 2017 5:56:52 AM com.hazelcast.client.spi.impl.ClientMembershipListener
INFO:

Members [3] {
Member [127.0.0.1]:5701
Member [127.0.0.1]:5702
Member [127.0.0.1]:5703
}

мар 21, 2017 5:56:52 AM com.hazelcast.core.LifecycleService
INFO: HazelcastClient[hz.client_0_dev-node-hz][3.6.7] is CLIENT_CONNECTED
ConsoleClient: Client get ready, choose command... (/h - help)

... <cut> ...

```
* Use the command line interface to send a task on execution to Hazelcast cluster
```sh
/h
h - help
You see current message

s - send <local_date_time_pattern>:<yyyy-MM-ddTHH:mm> <message>:<string>
You send the text message at the scheduled time to execute on Hazelcast node

q - quit
End session and quit

t - utc
Get current Hazelcast cluster time in UTC

Start your command with slash symbol '/'
Author: Dmitriy Shishmakov

/s 2017-03-21T03:02:12 Test_message_hello!
Send task successfully!
```
* On a server side you could see
```sh
06:03:50.034 [node-main-3] DEBUG r.s.c.Node - Thread: Thread[node-main-3,5,main] is alive
06:03:59.102 [node.executor-0] DEBUG r.s.c.FirstLevelWatcher - <-- FirstLevelWatcher Node:2 take task 'TimeTask[orderId=1,scheduledTime=1490065332000]'; checkTime: 1490065439097, scheduledTime: 1490065332000, delta: -107097
06:03:59.102 [node.executor-0] DEBUG r.s.c.FirstLevelWatcher - --> FirstLevelWatcher Node:2 put task 'TimeTask[orderId=1,scheduledTime=1490065332000]'
06:03:59.102 [node.executor-2] DEBUG r.s.c.FirstLevelConsumer - <-- FirstLevelConsumer:1 Node:2 start process task 'TimeTask[orderId=1,scheduledTime=1490065332000]' ...
06:03:59.103 [node.executor-2] INFO r.s.h.MessageTask - Run task; time: 2017-03-21T03:02:12, message: Test_message_hello!
06:03:59.966 [node-main-1] DEBUG r.s.c.Node - Thread: Thread[node-main-1,5,main] is alive
06:04:00.018 [node-main-2] DEBUG r.s.c.Node - Thread: Thread[node-main-2,5,main] is alive
```


## Stop

* First choice for the client `time-hz-executor` is terminated in response to a user interrupt, such as typing `^C` (Ctrl + C), or a system-wide event of shutdown.
```sh

... <cut> ...

^CClient: 1 STOP 2017-03-21T06:15:23.772
Buy!
Client: 1 stopped, state: IDLE
time-hz-executor/scripts$
```
* Second choice is to use inner command line
```sh

... <cut> ...

ConsoleClient: Client get ready, choose command... (/h - help)
/h
h - help
You see current message

s - send <local_date_time_pattern>:<yyyy-MM-ddTHH:mm> <message>:<string>
You send the text message at the scheduled time to execute on Hazelcast node

q - quit
End session and quit

t - utc
Get current Hazelcast cluster time in UTC

Start your command with slash symbol '/'
Author: Dmitriy Shishmakov

/q
мар 21, 2017 6:22:09 AM com.hazelcast.core.LifecycleService
INFO: HazelcastClient[hz.client_0_dev-node-hz][3.6.7] is SHUTTING_DOWN
мар 21, 2017 6:22:09 AM com.hazelcast.core.LifecycleService
INFO: HazelcastClient[hz.client_0_dev-node-hz][3.6.7] is SHUTDOWN
Client: 1 stopped, state: IDLE
Client: 1 STOP 2017-03-21T06:22:14.996
Buy!
time-hz-executor/scripts$

```
* Stop Hazelcast cluster:
```sh
time-hz-executor/scripts$ ./stop_hz_cluster.sh

... <cut> ...

06:25:24.349 [node-2-hook-thread] INFO r.s.c.ServiceController - Listener: Node:2 has stopped all services <--
06:25:24.349 [node-2-hook-thread] INFO r.s.c.ServiceController - Node:2 services stopped, state: IDLE
06:25:24.349 [node-2-hook-thread] INFO r.s.c.Node - Node: 2 executor services stopping...
06:25:24.350 [node-2-hook-thread] INFO r.s.c.Node - Node: 2 executor services stopped
06:25:24.350 [node-2-hook-thread] INFO r.s.c.Node - Node: 2 stopped, state: IDLE

... <cut> ...

06:25:26.568 [node-1-hook-thread] INFO r.s.c.TaskTimeService - TaskTimeService Node:1 stopped
06:25:26.568 [node-1-hook-thread] INFO r.s.c.ServiceController - Listener: Node:1 has stopped all services <--
06:25:26.568 [node-1-hook-thread] INFO r.s.c.ServiceController - Node:1 services stopped, state: IDLE
06:25:26.568 [node-1-hook-thread] INFO r.s.c.Node - Node: 1 executor services stopping...
06:25:26.569 [node-1-hook-thread] INFO r.s.c.Node - Node: 1 executor services stopped
06:25:26.569 [node-1-hook-thread] INFO r.s.c.Node - Node: 1 stopped, state: IDLE
```
Loading

0 comments on commit bd01967

Please sign in to comment.