[ 
https://issues.apache.org/jira/browse/IGNITE-5183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045194#comment-16045194
 ] 

Ryan Ripken commented on IGNITE-5183:
-------------------------------------

I understand but I'm somewhat disappointed.  

I require a concurrency guarantee and I now need to devise my own 
implementation.

The documentation here https://apacheignite.readme.io/v1.5/docs/job-scheduling 
sure makes it sound like its meant as a concurrency guarantee:
"Note that by setting parallelJobsNumber to 1, you can guarantee that all jobs 
will be executed one-at-a-time, and no two jobs will be executed concurrently."

If this is not going to be the case I suggest the language be changed to make 
this non-guarantee explicit:
"Note that by setting parallelJobsNumber to 1, you cannot guarantee that all 
jobs will be executed one-at-a-time, two jobs may be executed concurrently."

The javadoc here: https://ignite.apache.org/releases/2.0.0/javadoc/index.html 
also includes language ( "only", "will be", etc) that should be changed to 
include wiggle words ("usually", "may be").  


> parallelJobsNumber does not prevent concurrent execution
> --------------------------------------------------------
>
>                 Key: IGNITE-5183
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5183
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>    Affects Versions: 1.5.0.final, 1.9, 2.0
>         Environment: Windows7, WIndows 8, Windows 10
>            Reporter: Ryan Ripken
>         Attachments: IgniteTest.7z
>
>
> Using FifoQueueCollisionSpi with parallelJobsNumber == 1 does not prevent 
> multiple jobs from executing at the same time.
> Emails sent to Users list April 10th, 11th, 12th.
> Attached example which reproduces issue in Ignite 1.5.
> One node needs to run node.bat
> Another node should execute IgniteTest class.
> This example looks for concurrent execution using a static AtomicInteger, 
> when multiple executions are detected it prints a message with lots of 
> asterisks.
> The example also exhibits the issue in Ignite 1.9
> Example output:
>     Apr 11, 2017 5:02:48 PM org.apache.ignite.logger.java.JavaLogger warning
>     WARNING: Peer class loading is enabled (disable it in production for 
> performance and deployment consistency reasons)
>     Apr 11, 2017 5:02:48 PM org.apache.ignite.logger.java.JavaLogger warning
>     WARNING: This operating system has been tested less rigorously: Windows 
> 10 10.0 amd64. Our team will appreciate the feedback if you experience any 
> problems running ignite in this environment.
>     Apr 11, 2017 5:02:48 PM org.apache.ignite.logger.java.JavaLogger warning
>     WARNING: Checkpoints are disabled (to enable configure any 
> GridCheckpointSpi implementation)
>     Apr 11, 2017 5:02:48 PM org.apache.ignite.logger.java.JavaLogger warning
>     WARNING: Swap space is disabled. To enable use FileSwapSpaceSpi.
>     SLF4J: Class path contains multiple SLF4J bindings.
>     SLF4J: Found binding in 
> [jar:file:/J:/ignite/modules/rest-http/target/libs/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
>     SLF4J: Found binding in 
> [jar:file:/J:/ignite/modules/visor-plugins/target/libs/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
>     SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
>     SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
>     Apr 11, 2017 5:02:48 PM org.apache.ignite.logger.java.JavaLogger warning
>     WARNING: TcpDiscoveryMulticastIpFinder has no pre-configured addresses 
> (it is recommended in production to specify at least one address in 
> TcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
>     Apr 11, 2017 5:03:43 PM ignitetest.TestJob execute
>     WARNING: *******Multiple jobs in progress. NOT GOOD 
> ************************
>     *******Multiple jobs in progress. NOT GOOD ************************
>     Apr 11, 2017 5:03:43 PM ignitetest.TestJob execute
>     WARNING: *******Multiple jobs in progress. NOT GOOD 
> ************************
>     *******Multiple jobs in progress. NOT GOOD ************************



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to