Re: [DISCUSSION] Ignite integration testing framework.

[Ilya Suntsov]

t;>>> >
> > >>>>>> > An Ultimate, DR and Compatibility suites that performs
> > >>> functional
> > >>>>>>regression testing of GridGain Ultimate Edition features like
> > >>>>>>snapshots, security, data replication, rolling upgrades, etc.
> > >>>>>> >
> > >>>>>> > A Regression and some IEPs testing suites, like IEP-14,
> > IEP-15,
> > >>>>>>etc, etc, etc.
> > >>>>>> >
> > >>>>>> > Most of the suites above use another in-house developed Java
> > >>> tool
> > >>>>>>– PiClient – to perform actual loading and miscellaneous
> > operations
> > >>>>>>with Ignite under test. We use py4j Python-Java gateway library
> > to
> > >>>>>&

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

[Ilya Suntsov]

Congrats, Slava!

ср, 19 февр. 2020 г. в 10:59, Andrey Mashenkov :

> Congratulations, Slava!
>
> вт, 18 февр. 2020 г., 22:20 Dmitriy Pavlov :
>
> > Hello Ignite Community,
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Vyacheslav Koptilin to become a committer and we are pleased to announce
> > that he has accepted.
> >
> > Vyacheslav investigated and fixed a number of non-trivial issues in the
> > Ignite Native persistent store, was a reviewer of Read Repair (ex.
> > Consistency Check).
> >
> > Being a committer enables easier contribution to the project since there
> is
> > no need to go via the patch submission process. This should enable better
> > productivity.
> >
> > Vyacheslav, thanks for supporting the community and keep the pace!
> >
> > Best Regards,
> > Dmitriy Pavlov
> > on behalf of Apache Ignite PMC
> >
>


-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

[jira] [Created] (IGNITE-12233) Merge benchmarks sql index benchmarks from ignite-2.7 to master

[Ilya Suntsov (Jira)]

Ilya Suntsov created IGNITE-12233:
-

 Summary: Merge benchmarks sql index benchmarks from ignite-2.7 to 
master
 Key: IGNITE-12233
 URL: https://issues.apache.org/jira/browse/IGNITE-12233
 Project: Ignite
  Issue Type: Task
  Components: yardstick
Reporter: Ilya Suntsov
Assignee: Ilya Suntsov


The following benchmarks are missed in master but exist in ignite-2.7:
* IgniteSqlMergeIndexedValue1Benchmark
* IgniteSqlMergeIndexedValue2Benchmark
* IgniteSqlMergeIndexedValue8Benchmark
* IgniteSqlDeleteFilteredBenchmark
* IgniteSqlUpdateBenchmark
* IgniteSqlUpdateFilteredBenchmark
* IgniteSqlInsertIndexedValue1Benchmark
* IgniteSqlInsertIndexedValue2Benchmark
* IgniteSqlInsertIndexedValue8Benchmark 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-11319) ignitevisorcmd can't handle incorrect !q parameter

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-11319:
-

 Summary: ignitevisorcmd can't handle incorrect !q parameter
 Key: IGNITE-11319
 URL: https://issues.apache.org/jira/browse/IGNITE-11319
 Project: Ignite
  Issue Type: Task
Reporter: Ilya Suntsov


Please take a look at difference between "!q" and "\q" parameters:

{noformat}

visor> !q

[ERROR] Could not expand event

java.lang.IllegalArgumentException: !q: event not found

at jline.console.ConsoleReader.expandEvents(ConsoleReader.java:779)

at jline.console.ConsoleReader.finishBuffer(ConsoleReader.java:631)

at jline.console.ConsoleReader.accept(ConsoleReader.java:2019)

at jline.console.ConsoleReader.readLine(ConsoleReader.java:2666)

at jline.console.ConsoleReader.readLine(ConsoleReader.java:2269)

at 
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)

at 
org.gridgain.visor.commands.VisorGridGainConsole$.delayedEndpoint$org$gridgain$visor$commands$VisorGridGainConsole$1(VisorGridGainConsole.scala:88)

at 
org.gridgain.visor.commands.VisorGridGainConsole$delayedInit$body.apply(VisorGridGainConsole.scala:77)

at scala.Function0$class.apply$mcV$sp(Function0.scala:34)

at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)

at scala.App$$anonfun$main$1.apply(App.scala:76)

at scala.App$$anonfun$main$1.apply(App.scala:76)

at scala.collection.immutable.List.foreach(List.scala:392)

at 
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)

at scala.App$class.main(App.scala:76)

at 
org.gridgain.visor.commands.VisorGridGainConsole$.main(VisorGridGainConsole.scala:77)

at 
org.gridgain.visor.commands.VisorGridGainConsole.main(VisorGridGainConsole.scala)

 

visor> \q

[WARN ] Invalid command name: '\q'

[WARN ] Type 'help' to print commands list.

{noformat}

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-11306) NativeSqlJoinQueryRangeBenchmark doesn't work

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-11306:
-

 Summary: NativeSqlJoinQueryRangeBenchmark doesn't work
 Key: IGNITE-11306
 URL: https://issues.apache.org/jira/browse/IGNITE-11306
 Project: Ignite
  Issue Type: Task
  Components: yardstick
Affects Versions: 2.7
Reporter: Ilya Suntsov


Config:

{noformat}

*now0**=*`date +'%H%M%S'`

# JVM options.

*JVM_OPTS**=**${JVM_OPTS}*" -DIGNITE_QUIET*=**false*"

# Uncomment to enable concurrent garbage collection (GC) if you encounter long 
GC pauses.

*JVM_OPTS**=**${JVM_OPTS}*" *\*

-Xms8g *\*

-Xmx8g *\*

-Xloggc:./gc*${now0}*.log *\*

-XX:+PrintGCDetails *\*

-verbose:gc *\*

-XX:+UseParNewGC *\*

-XX:+UseConcMarkSweepGC *\*

-XX:+PrintGCDateStamps *\*

"

#Ignite version

*ver**=*ver-*2*.*8*.*0*-SNAPSHOT-rev-816f435d-

# List of default probes.

# Add DStatProbe or VmStatProbe if your OS supports it (e.g. if running on 
Linux).

*BENCHMARK_DEFAULT_PROBES**=*ThroughputLatencyProbe,PercentileProbe,DStatProbe

# Packages where the specified benchmark is searched by reflection mechanism.

*BENCHMARK_PACKAGES**=*org.yardstickframework,org.apache.ignite.yardstick

# Flag which indicates to restart the servers before every benchmark execution.

*RESTART_SERVERS**=**true*

# Probe point writer class name.

# BENCHMARK_WRITER=

# Comma-separated list of the hosts to run BenchmarkServers on.

*SERVER_HOSTS**=172*.*25*.*1*.*30*,*172*.*25*.*1*.*27*,*172*.*25*.*1*.*28*,*172*.*25*.*1*.*29*

# Comma-separated list of the hosts to run BenchmarkDrivers on.

*DRIVER_HOSTS**=172*.*25*.*1*.*11*

# Remote username.

# REMOTE_USER=

# Number of nodes, used to wait for the specified number of nodes to start.

*nodesNum**=*$((`echo *${SERVER_HOSTS}* | tr ',' '\n' | wc -l` + `echo 
*${DRIVER_HOSTS}* | tr ',' '\n' | wc -l`))

# Backups count.

*b**=1*

# Warmup.

*w**=60*

# Duration.

*d**=180*

# Threads count.

*t**=64*

# Sync mode.

*sm**=*PRIMARY_SYNC

# Jobs.

*j**=10*

# Run configuration which contains all benchmarks.

# Note that each benchmark is set to run for 300 seconds (5 min) with warm-up 
set to 60 seconds (1 minute).

*CONFIGS**=*"*\*

-cfg *${SCRIPT_DIR}*/../config/ignite-config.xml -nn *${nodesNum}* -b *${b}* -w 
*${w}* -d *${d}* -t *${t}* -sm *${sm}* -pc *2* -r *10* *-*-sqlRange *1*  
*-*-client 

 *-dn* NativeSqlJoinQueryRangeBenchmark -sn IgniteNode -ds 
*${ver}*sql-select-native-join-r1-*${b}*-backup,*\*

"

{noformat}

Exception:

{noformat}

<12:50:49> Populate 9

<12:50:50> Populate 10

<12:50:50> Probe writer is not configured (using default CSV 
writer)

<12:50:50> ThroughputLatencyProbe is started.

<12:50:50> PercentileProbe is started.

<12:50:50> DStatProbe is started. Command: 'dstat -m --all 
--noheaders --noupdate 1'

<12:50:50> Starting warmup.

Finishing main test [ts=1550051451762, date=Wed Feb 13 12:50:51 MSK 2019]

ERROR: Shutting down benchmark driver to unexpected exception.

Type '--help' for usage.

java.lang.Exception: Invalid result set size [actual=0, expected=1]

*<-->*at 
org.apache.ignite.yardstick.jdbc.NativeSqlJoinQueryRangeBenchmark.test(NativeSqlJoinQueryRangeBenchmark.java:84)

*<-->*at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)

*<-->*at java.lang.Thread.run(Thread.java:748)

[2019-02-13 12:50:51,810][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=compute]

[2019-02-13 12:50:51,812][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=query]

[2019-02-13 12:50:51,813][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=atomic-index-with-eviction]

[2019-02-13 12:50:51,813][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=atomic-index]

[2019-02-13 12:50:51,813][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=tx]

[2019-02-13 12:50:51,815][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=atomic]

[2019-02-13 12:50:51,815][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=ignite-sys-cache]

[2019-02-13 12:50:51,815][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=SQL_PUBLIC_PERSON]

[2019-02-13 12:50:51,816][INFO ][Thread-8][GridCacheProcessor] Stopped cache 
[cacheName=SQL_PUBLIC_ORGANIZATION]

[2019-02-13 12:50:51,825][INFO ][Thread-8][IgniteKernal]*.*

 

{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-11307) SqlNative benchmarks failed with more than 1 client

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-11307:
-

 Summary: SqlNative benchmarks failed with more than 1 client
 Key: IGNITE-11307
 URL: https://issues.apache.org/jira/browse/IGNITE-11307
 Project: Ignite
  Issue Type: Task
  Components: yardstick
Affects Versions: 2.7
Reporter: Ilya Suntsov


I saw the exception below when tried to run NativeSqlInsertDeleteBenchmark, 
NativeSqlQueryRangeBenchmark, NativeSqlUpdateRangeBenchmark with 4 servers and 
8 clients. Looks like we need to use "*create* *table* *if* *not* *exists*" 
instead of "*create* *table*"

{noformat}

<19:55:12> Create table...
<19:55:12> Creating table with schema: CREATE TABLE test_long 
(id LONG PRIMARY KEY, val LONG) WITH "wrap_value=true";
[2019-02-12 19:55:12,876][INFO 
][exchange-worker-#58][GridDhtPartitionsExchangeFuture] Finish exchange future 
[startVer=AffinityTopologyVersion [topVer=12, minorTopVer=0], 
resVer=AffinityTopologyVersion [topVer=12, minorTopVer=0], err=null]
[2019-02-12 19:55:12,881][INFO 
][exchange-worker-#58][GridDhtPartitionsExchangeFuture] Completed partition 
exchange [localNode=f5594085-054c-492f-9112-301b196ff8b3, 
exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion 
[topVer=12, minorTopVer=0],.
evt=NODE_JOINED, evtNode=TcpDiscoveryNode 
[id=0a475055-ad4c-46e4-88e9-ebeba9c846ce, addrs=ArrayList [127.0.0.1, 
172.17.0.1, 172.25.1.26], sockAddrs=HashSet [/172.17.0.1:0, /127.0.0.1:0, 
lab26.gridgain.local/172.25.1.26:0], discPort=0, order=12, intOrder=12, 
lastExchangeTime=1549990512845,
 loc=false, ver=2.8.0#20190211-sha1:e59aa879, isClient=true], done=true], 
topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0]]
[2019-02-12 19:55:12,881][INFO 
][exchange-worker-#58][GridDhtPartitionsExchangeFuture] Exchange timings 
[startVer=AffinityTopologyVersion [topVer=12, minorTopVer=0], 
resVer=AffinityTopologyVersion [topVer=12, minorTopVer=0], stage="Waiting in 
exchange queue" (0 ms),.
stage="Exchange parameters initialization" (0 ms), stage="Determine exchange 
type" (5 ms), stage="Exchange done" (4 ms), stage="Total time" (9 ms)]
[2019-02-12 19:55:12,881][INFO 
][exchange-worker-#58][GridDhtPartitionsExchangeFuture] Exchange longest local 
stages [startVer=AffinityTopologyVersion [topVer=12, minorTopVer=0], 
resVer=AffinityTopologyVersion [topVer=12, minorTopVer=0]]
[2019-02-12 19:55:12,881][INFO ][exchange-worker-#58][time] Finished exchange 
init [topVer=AffinityTopologyVersion [topVer=12, minorTopVer=0], crd=false]
[2019-02-12 19:55:12,882][INFO 
][exchange-worker-#58][GridCachePartitionExchangeManager] Skipping rebalancing 
(no affinity changes) [top=AffinityTopologyVersion [topVer=12, minorTopVer=0], 
rebTopVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], evt=NODE_JOINED, e
vtNode=0a475055-ad4c-46e4-88e9-ebeba9c846ce, client=true]
[2019-02-12 19:55:12,972][INFO ][exchange-worker-#58][time] Started exchange 
init [topVer=AffinityTopologyVersion [topVer=12, minorTopVer=1], crd=false, 
evt=DISCOVERY_CUSTOM_EVT, evtNode=da386c99-7b45-4c5b-913b-95eb5b70118f, 
customEvt=DynamicCacheChangeBatch.
[id=5ac22a2e861-fb1a5341-6a6e-4ef8-8a74-072c95cb2e08, reqs=ArrayList 
[DynamicCacheChangeRequest [cacheName=SQL_PUBLIC_TEST_LONG, hasCfg=true, 
nodeId=da386c99-7b45-4c5b-913b-95eb5b70118f, clientStartOnly=false, stop=false, 
destroy=false, disabledAfterStartfalse]], exchangeActions=ExchangeActions
 [startCaches=[SQL_PUBLIC_TEST_LONG], stopCaches=null, 
startGrps=[SQL_PUBLIC_TEST_LONG], stopGrps=[], resetParts=null, 
stateChangeRequest=null], startCaches=false], allowMerge=false]
[2019-02-12 19:55:12,986][INFO ][exchange-worker-#58][time] Finished exchange 
init [topVer=AffinityTopologyVersion [topVer=12, minorTopVer=1], crd=false]
[2019-02-12 19:55:13,063][INFO ][sys-#66][GridDhtPartitionsExchangeFuture] 
Received full message, will finish exchange 
[node=e301e555-2a31-4bdd-a574-9ec412f4c435, resVer=AffinityTopologyVersion 
[topVer=12, minorTopVer=1]]
[2019-02-12 19:55:13,064][INFO ][sys-#66][GridDhtPartitionsExchangeFuture] 
Finish exchange future [startVer=AffinityTopologyVersion [topVer=12, 
minorTopVer=1], resVer=AffinityTopologyVersion [topVer=12, minorTopVer=1], 
err=null]
[2019-02-12 19:55:13,075][INFO ][sys-#66][GridDhtPartitionsExchangeFuture] 
Completed partition exchange [localNode=f5594085-054c-492f-9112-301b196ff8b3, 
exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion 
[topVer=12, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT, evtNode=TcpDiscoveryNode.
[id=da386c99-7b45-4c5b-913b-95eb5b70118f, addrs=ArrayList [127.0.0.1, 
172.17.0.1, 172.25.1.13], sockAddrs=HashSet [/172.17.0.1:0, 
lab13.gridgain.local/172.25.1.13:0, /127.0.0.1:0], discPort=0, order=7, 
intOrder=7, lastExchangeTime=1549990507545, loc=false, 
ver=2.8.0#20190211-sha1:e59aa879, isClient=true],
 don

[jira] [Created] (IGNITE-10918) Implement C++, .Net thin benchmarks

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-10918:
-

 Summary: Implement C++, .Net thin benchmarks 
 Key: IGNITE-10918
 URL: https://issues.apache.org/jira/browse/IGNITE-10918
 Project: Ignite
  Issue Type: Task
Reporter: Ilya Suntsov
 Attachments: put.cpp, put.cs

We need the following list of benchmarks:

{noformat}

IgniteThinGetBenchmark
IgniteThinGetTxBenchmark
IgniteThinPutAllBenchmark
IgniteThinPutAllTxBenchmark
IgniteThinPutGetBenchmark
IgniteThinPutTxBenchmark

{noformat}

You can find examples of benchmarks in attachment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10842) Exception during node stopping

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-10842:
-

 Summary: Exception during node stopping
 Key: IGNITE-10842
 URL: https://issues.apache.org/jira/browse/IGNITE-10842
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7
 Environment: branch: master

 ver. 2.8.0-SNAPSHOT#20181228-sha1:e2edf41b
Reporter: Ilya Suntsov
 Fix For: 2.8
 Attachments: ticket-logs.zip

Steps:
 # Start 3 nodes
 # Almost simultaneously start all nodes

Result:

I see the following messages in log:

{noformat}

2018-12-28 12:30:06,606][ERROR][sys-stripe-8-#9][TcpCommunicationSpi] Failed to 
send message to remote node [node=TcpDiscoveryNode 
[id=8e884f80-f55d-4b32-9dcd-39e1af0ed2ef, addrs=ArrayList [1

class org.apache.ignite.spi.IgniteSpiException: Node is stopping.

*<-->*at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2883)

*<-->*at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2743)

*<-->*at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)

*<-->*at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)

*<-->*at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)

*<-->*at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1240)

*<-->*at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1279)

*<-->*at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3548)

*<-->*at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$3300(GridDhtAtomicCache.java:139)

*<-->*at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3794)

*<-->*at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:508)

*<-->*at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)

*<-->*at java.lang.Thread.run(Thread.java:745)

[2018-12-28 12:30:06,658][ERROR][sys-stripe-12-#13][TcpCommunicationSpi] Failed 
to send message to remote node [node=TcpDiscoveryNode 
[id=8e884f80-f55d-4b32-9dcd-39e1af0ed2ef, addrs=ArrayList

class org.apache.ignite.spi.IgniteSpiException: Node is stopping.

*<-->*at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2883)

*<-->*at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2743)

*<-->*at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2702)

*<-->*at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1652)

*<-->*at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1726)

*<-->*at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1240)

*<-->*at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1279)

*<-->*at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3548)

*<-->*at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$3300(GridDhtAtomicCache.java:139)

*<-->*at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3794)

*<-->*at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:508)

*<-->*at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)

*<-->*at java.lang.Thread.run(Thread.java:745)

{noformat}

I guess it is redundant information on *Node stopping* stage.

Please take a look at logs in the attachement.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10800) Add wal_mode parameter to properties file

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-10800:
-

 Summary: Add wal_mode parameter to properties file
 Key: IGNITE-10800
 URL: https://issues.apache.org/jira/browse/IGNITE-10800
 Project: Ignite
  Issue Type: Bug
  Components: yardstick
Affects Versions: 2.7
Reporter: Ilya Suntsov


As I understand we can enable persistence with properties file parameter. I 
guess we need to add a parameter for WAL mode.

Expected behavior:
 * When we have in configuration region with persistence should be used this 
configuration and wal_mode value from properties should be ignored. Also should 
be added warnings in all nodes logs with configuration details. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10170) .NET: Services.ServicesTestAsync fails

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-10170:
-

 Summary: .NET: Services.ServicesTestAsync fails
 Key: IGNITE-10170
 URL: https://issues.apache.org/jira/browse/IGNITE-10170
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


Test run: 
[https://ci.ignite.apache.org/viewLog.html?buildId=2263939=buildResultsDiv=IgniteTests24Java8_PlatformNet]

Error message:

{noformat}Test(s) failed. Expected: True
 But was: False

at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, 
String message, Object[] args)
 at Apache.Ignite.Core.Tests.Services.ServicesTest.CheckServiceStarted(IIgnite 
grid, Int32 count, String svcName) in 
c:\BuildAgent\work\9198da4c51c3e112\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Services\ServicesTest.cs:line
 1010
 at Apache.Ignite.Core.Tests.Services.ServicesTest.TestCancelException() in 
c:\BuildAgent\work\9198da4c51c3e112\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Services\ServicesTest.cs:line
 745
--- Stderr: ---
[07-11-2018 14:20:33][INFO ][srvc-deploy-#18766%grid1%][GridServiceProcessor] 
Starting service instance [name=Service1, 
execId=e0264c92-3df3-49d8-bac7-d9b40f749161]
[07-11-2018 14:20:34][INFO ][srvc-deploy-#18816%grid2%][GridServiceProcessor] 
Starting service instance [name=Service1, 
execId=f920c229-b91e-4c92-8efe-f19b0fc03d0b]
[07-11-2018 14:20:34][INFO ][srvc-deploy-#18816%grid2%][GridServiceProcessor] 
Cancelled service instance [name=Service1, 
execId=f920c229-b91e-4c92-8efe-f19b0fc03d0b]
[07-11-2018 14:20:34][INFO ][srvc-deploy-#18766%grid1%][GridServiceProcessor] 
Cancelled service instance [name=Service1, 
execId=e0264c92-3df3-49d8-bac7-d9b40f749161]

{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-10148) Add aws s3 and elb configs to benchmarks/config

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-10148:
-

 Summary: Add aws s3 and elb configs to benchmarks/config 
 Key: IGNITE-10148
 URL: https://issues.apache.org/jira/browse/IGNITE-10148
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov
Assignee: Ilya Suntsov


Add to yardstick:
 * S3 discovery config
 * ELB discovery config



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-9534) Wrong error message in bin/include/functions.sh

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-9534:


 Summary: Wrong error message in bin/include/functions.sh
 Key: IGNITE-9534
 URL: https://issues.apache.org/jira/browse/IGNITE-9534
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.6
Reporter: Ilya Suntsov


In the case when we don't have java installed on the host I see a message:

{noformat}

echo $0", ERROR:"

            echo "JAVA_HOME environment variable is not found."

            echo "Please point JAVA_HOME variable to location of JDK 1.7 or JDK 
1.8."

            echo "You can also download latest JDK at http://java.com/download;

{noformat}

Java versions should be changed to:

{noformat}

 JDK 1.8 or JDK 9

{noformat}

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: New PMC member: Dmitriy Pavlov

[Ilya Suntsov]

Dmitriy, congrats!
It is really great news!

On Fri, Aug 31, 2018, 02:30 Saikat Maitra  wrote:

> Dmitriy,
>
> Congratulations !!!
>
> My best wishes :)
>
> Regards,
> Saikat
>
>
>
> On Thu, Aug 30, 2018 at 1:20 PM, Pavel Kovalenko 
> wrote:
>
> > Dmitriy,
> >
> > Congratulations. This is very nice to see such valuable community member
> in
> > PMC role.
> >
> > чт, 30 авг. 2018 г. в 20:11, Dmitriy Govorukhin <
> > dmitriy.govoruk...@gmail.com>:
> >
> > > Dmitriy,
> > >
> > > My congratulations!
> > > Thank you for your work!
> > >
> > > On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov 
> > > wrote:
> > >
> > > > Dmitry,
> > > >
> > > > My congratulations!
> > > > Thank you for guiding and helping the community members and me, in
> > > > particular,
> > > > to follow the Apache Way principles and also for your contribution.
> > > >
> > > > On Wed, 29 Aug 2018 at 22:31 Denis Magda  wrote:
> > > >
> > > > > The Project Management Committee (PMC) for Apache Ignite
> > > > > has invited Dmitriy Pavlov to become a PMC member and we are
> pleased
> > > > > to announce that he has accepted.
> > > > >
> > > > > Being a PMC member enables assistance with the management
> > > > > and to guide the direction of the project.
> > > > >
> > > > > Congratulations Dmitriy! Keep contributing to Ignite success the
> way
> > > you
> > > > do
> > > > > ;)
> > > > >
> > > > > Denis
> > > > >
> > > > --
> > > > --
> > > > Maxim Muzafarov
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-9417) IgniteSqlInsertIndexedValueBenchamrks failed with more than one driver

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-9417:


 Summary: IgniteSqlInsertIndexedValueBenchamrks failed with more 
than one driver
 Key: IGNITE-9417
 URL: https://issues.apache.org/jira/browse/IGNITE-9417
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


I guess that we need to handle errors like bellow and continue to work OR each 
driver must insert it's own key range:

{noformat}

ERROR: Shutting down benchmark driver to unexpected exception.

Type '--help' for usage.

javax.cache.CacheException: Duplicate key during INSERT [key=52]

<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:676)

<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:615)

<-->at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:385)

<-->at 
org.apache.ignite.yardstick.cache.dml.IgniteSqlInsertIndexedValue1Benchmark.test(IgniteSqlInsertIndexedValue1Benchmark.java:38)

<-->at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178)

<-->at java.lang.Thread.run(Thread.java:748)

Caused by: class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Duplicate key 
during INSERT [key=52]

<-->at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:803)

<-->at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.processDmlSelectResult(DmlStatementsProcessor.java:581)

<-->at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:539)

<-->at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:171)

<-->at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsDistributed(DmlStatementsProcessor.java:345)

<-->at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1791)

<-->at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1755)

<-->at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2107)

<-->at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2102)

<-->at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)

<-->at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2650)

<-->at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2116)

<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:664)

<-->... 5 more

{noformat}

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Benchmarking

[Ilya Suntsov]

Anton,

I have experience with the yardstick and can help you sometimes.
My possibilities in this matter are limited and it is possible that your
request will be delayed.

Please, try to use the last version of the yardstick and then we can
discuss specific yardstick
issues that you couldn't solve.

Also, you can use dedicated AWS instances for benchmarking.
Pay attention to the fact that sometimes our benchmarks can show unstable
results in case of
non-dedicated instances.




2018-08-09 21:09 GMT+03:00 Vyacheslav Daradur :

> Huge +1, for a public benchmarking tool and the Docker based approach.
> On Thu, Aug 9, 2018 at 7:16 PM Pavel Kovalenko  wrote:
> >
> > Igniters,
> >
> > I would like to add that it would be very nice to have prepared scenarios
> > in packed docker images with docker-compose, to easily deploy and run it
> on
> > AWS environment. This will give the possibility to benchmark any changes
> > independently and fastly.
> >
> > 2018-08-09 18:51 GMT+03:00 Anton Vinogradov :
> >
> > > Igniters,
> > >
> > > All critical code changes should be covered by benchmarks.
> > > Currently, community have no dedicated benchmarking service.
> > >
> > > Everyone can run yandstick locally, but this seems to be useless.
> > > You have to run cluster on 4 clients and 4 servers, at least.
> > >
> > > Currently it is not possible for me to perform benchmarking using 8+
> real
> > > servers.
> > > Also, some automation requred to have reliable check of two branchs
> with
> > > one feature difference, since yardstick will provide you branch check,
> not
> > > a branches comparision.
> > >
> > > So, my question is:
> > > Is there anybody at community able to perform benchmarks on real
> hardware
> > > and already have automation to compare 2 branches?
> > >
>
>
>
> --
> Best Regards, Vyacheslav D.
>



-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: [BENCHMARK REQUEST] IGNITE-8446

[Ilya Suntsov]

Anton,

I've run benchmarks with the following parameters:

   - 4 servers, 8 clients
   - primary/full sync
   - in-memory

Benchmarks show approximately the same numbers.

Primary sync:
ignite-8446 ignite-8446-master delta
tx-optim-repRead-put-get 36119 36241 -0.34%
tx-pessim-repRead-put-get 16747 16886 -0.83%
tx-putAll 702 706 -0.57%

Full sync:
ignite-8446 ignite-8446-master delta
tx-optim-repRead-put-get 35967 36386 -1.16%
tx-pessim-repRead-put-get 14415 14513 -0.68%
tx-putAll 693 695 -0.29%

2018-08-03 15:53 GMT+03:00 Anton Vinogradov :

> - Benchmark should check how many tx can be completed in second (please
> use same as you use to  check the release)
> - in-memory
> - default
> - same you use at pre-release check.
>
> пт, 3 авг. 2018 г. в 15:38, Ilya Suntsov :
>
>> Anton,
>>
>> Please provide more details:
>>
>>- Benchmark class name
>>- PDS/in-memory
>>- sync mode
>>- cluster size
>>
>> ?
>>
>> 2018-08-03 13:52 GMT+03:00 Dmitriy Pavlov :
>>
>>> Hi Anton,
>>>
>>> Thank you for bringing this question here. Actually I'm not right person
>>> who can do it, but hopefully Ilya can assist.
>>>
>>> Hi Ilya,
>>>
>>> could you please run required benchmark?
>>>
>>> Sincerely,
>>> Dmitriy Pavlov
>>>
>>> пт, 3 авг. 2018 г. в 13:33, Anton Vinogradov :
>>>
>>>> Dmitry,
>>>>
>>>> AFAIK, you're able to perform benchmarking of critical code.
>>>> Could you please check https://issues.apache.
>>>> org/jira/browse/IGNITE-8446?
>>>>
>>>> We have to check
>>>> https://github.com/apache/ignite/tree/ignite-8446
>>>> vs
>>>> https://github.com/apache/ignite/tree/ignite-8446-master
>>>>
>>>> Only one benchmark is required: tx throughput
>>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Ilya Suntsov
>> email: isunt...@gridgain.com
>> *GridGain Systems*
>> www.gridgain.com
>>
>


-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: [BENCHMARK REQUEST] IGNITE-8446

[Ilya Suntsov]

Anton,

Please provide more details:

   - Benchmark class name
   - PDS/in-memory
   - sync mode
   - cluster size

?

2018-08-03 13:52 GMT+03:00 Dmitriy Pavlov :

> Hi Anton,
>
> Thank you for bringing this question here. Actually I'm not right person
> who can do it, but hopefully Ilya can assist.
>
> Hi Ilya,
>
> could you please run required benchmark?
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 3 авг. 2018 г. в 13:33, Anton Vinogradov :
>
>> Dmitry,
>>
>> AFAIK, you're able to perform benchmarking of critical code.
>> Could you please check https://issues.apache.org/jira/browse/IGNITE-8446?
>>
>> We have to check
>> https://github.com/apache/ignite/tree/ignite-8446
>> vs
>> https://github.com/apache/ignite/tree/ignite-8446-master
>>
>> Only one benchmark is required: tx throughput
>>
>


-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: iep-6 metrics ticket review

[Ilya Suntsov]

Dmitry G.,

I've run yardstick pds benchmarks against PR-3148 and master and can
confirm that fixes from PR don't affect performance.

2018-07-26 18:38 GMT+03:00 Dmitry Pavlov :

> Hi Ilya,
>
> We all agreed change is good, but we'd like to be absolutely sure there is
> no performance drop. Dmitriy G. was one from reviewer, so I hope he would
> provide any additional info about change.
>
> Could you please assist here?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 26 июл. 2018 г. в 18:25, Aleksey Kuznetsov :
>
>> Hi, Igniters!
>>
>> I have the ticket [1] reviewed, it introduce large changes to cache.
>>
>> How can I assure it causes no performance drop ?
>>
>> [1] : https://issues.apache.org/jira/browse/IGNITE-6846
>>
>> ср, 11 апр. 2018 г. в 3:32, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com>:
>>
>> > This is on my plate, will try to take a look this week.
>> >
>> > -Val
>> >
>> > On Mon, Apr 9, 2018 at 10:28 AM, Denis Magda  wrote:
>> >
>> > > Val,
>> > >
>> > > As an initial reviewer and reporter, could you have a look and sign
>> the
>> > > contribution off?
>> > >
>> > > --
>> > > Denis
>> > >
>> > > On Mon, Apr 9, 2018 at 12:56 AM, Aleksey Kuznetsov <
>> > > alkuznetsov...@gmail.com
>> > > > wrote:
>> > >
>> > > > Hi ,Igniters!
>> > > >
>> > > > Do we still need this ticket, about invoke metrics : [1] ?
>> > > >
>> > > > If yes, than could somebody review it ?
>> > > >
>> > > > If no, should we close this ticket ?
>> > > >
>> > > > [1] : https://issues.apache.org/jira/browse/IGNITE-6846
>> > > > --
>> > > >
>> > > > *Best Regards,*
>> > > >
>> > > > *Kuznetsov Aleksey*
>> > > >
>> > >
>> >
>>
>


-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: [VOTE] Apache Ignite 2.6.0 RC1

[Ilya Suntsov]

Anton,

Module spark-2.10 and optional lib ignite-spark_2.10 were removed during
the work on IGNITE-8534 <https://issues.apache.org/jira/browse/IGNITE-8534>

IGNITE-8768 <https://issues.apache.org/jira/browse/IGNITE-8768>:

+ 
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/EvictionContext.java

IGNITE-8804 <https://issues.apache.org/jira/browse/IGNITE-8804>:

+ config/wsl-default-config.xml

IGNITE-8685 <https://issues.apache.org/jira/browse/IGNITE-8685?src=confmacro>:

- 
modules/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java

- 
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java


Other changes are tests that were added.


2018-07-11 16:28 GMT+03:00 Anton Vinogradov :

> Ilya,
>
> Please confirm that all changes [1] expected
> [1]
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
>
> ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov :
>
> > Anton,
> >
> > Please take a look at:
> >
> > https://ci.ignite.apache.org/viewLog.html?buildId=1478134;
> tab=buildResultsDiv=ApacheIgniteReleaseJava8_
> IgniteRelease72CheckFileConsistency
> >
> > https://ci.ignite.apache.org/viewLog.html?buildId=1478557;
> tab=buildResultsDiv=ApacheIgniteReleaseJava8_
> PrepareVote4CheckRcLicensesChecksum
> >
> > Dmitry,
> >
> > These steps should be outside the chain.
> >
> > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov :
> >
> > > Automation possible, but it's hard to determine previous version
> > > automatically (especially when you have 2.x and 3.x releasing
> > concurrently)
> > > for API check [1],
> > > but RC check [1] can be chained.
> > >
> > > [1]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=
> > > buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > > [2]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=
> > > buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > >
> > > ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov :
> > >
> > > > No, I just wondering if it could be in chain. If manual run is
> > requires I
> > > > guess we could document it somewhere, so everyone in community will
> be
> > > > aware what should be done.
> > > >
> > > > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov :
> > > >
> > > > > Currently, I have no knowledge about this build types and theirs
> > > purpose.
> > > > >
> > > > > I guess release engineer has to run them manually with ignite-2.6
> > > branch
> > > > > or with 2.6.0-rc1 build result.
> > > > > Should I do it?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 11 Jul 2018, at 14:36, Dmitry Pavlov 
> > wrote:
> > > > >
> > > > > I thought these steps are to be run automatically within chain and
> no
> > > > > manual steps are required.
> > > > >
> > > > > Petr, please step in.
> > > > >
> > > > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov :
> > > > >
> > > > >> I do NOT see that API was checked [1] and automated check [2]
> > > performed
> > > > >>
> > > > >> [1]
> > > > >>
> > > > >>
> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=
> > > buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > > > >> [2]
> > > > >>
> > > > >>
> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=
> > > buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > > > >>
> > > > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <
> > akuznet...@apache.org
> > > >:
> > > > >>
> > > > >> > +1 (binding)
> > > > >> >
> > > > >> > Download sources:   OK
> > > > >> > Build from sources: OK
> > > > >> > Run ignite.bat: OK
> > > > >> >
> > > > >> > --
> > > > >> > Alexey Kuznetsov
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Ilya Suntsov
> > email: isunt...@gridgain.com
> > *GridGain Systems*
> > www.gridgain.com
> >
>



-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: [VOTE] Apache Ignite 2.6.0 RC1

[Ilya Suntsov]

Anton,

Please take a look at:
https://ci.ignite.apache.org/viewLog.html?buildId=1478134=buildResultsDiv=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency
https://ci.ignite.apache.org/viewLog.html?buildId=1478557=buildResultsDiv=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum

Dmitry,

These steps should be outside the chain.

2018-07-11 14:49 GMT+03:00 Anton Vinogradov :

> Automation possible, but it's hard to determine previous version
> automatically (especially when you have 2.x and 3.x releasing concurrently)
> for API check [1],
> but RC check [1] can be chained.
>
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=
> buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> [2]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=
> buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
>
> ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov :
>
> > No, I just wondering if it could be in chain. If manual run is requires I
> > guess we could document it somewhere, so everyone in community will be
> > aware what should be done.
> >
> > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov :
> >
> > > Currently, I have no knowledge about this build types and theirs
> purpose.
> > >
> > > I guess release engineer has to run them manually with ignite-2.6
> branch
> > > or with 2.6.0-rc1 build result.
> > > Should I do it?
> > >
> > >
> > >
> > >
> > > On 11 Jul 2018, at 14:36, Dmitry Pavlov  wrote:
> > >
> > > I thought these steps are to be run automatically within chain and no
> > > manual steps are required.
> > >
> > > Petr, please step in.
> > >
> > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov :
> > >
> > >> I do NOT see that API was checked [1] and automated check [2]
> performed
> > >>
> > >> [1]
> > >>
> > >>
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency=
> buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > >> [2]
> > >>
> > >>
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=
> buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__
> > >>
> > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov  >:
> > >>
> > >> > +1 (binding)
> > >> >
> > >> > Download sources:   OK
> > >> > Build from sources: OK
> > >> > Run ignite.bat: OK
> > >> >
> > >> > --
> > >> > Alexey Kuznetsov
> > >> >
> > >>
> > >
> > >
> >
>



-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: [VOTE] Apache Ignite 2.6.0 RC1

[Ilya Suntsov]

Dmitry,

I see 2.6 changes above 2.5:

Apache Ignite Release Notes
> ===
> Apache Ignite In-Memory Data Fabric 2.6
> ---
> Ignite:
> * Fixed incorrect calculation of client affinity assignment with baseline.
> * Fixed incorrect calculation of switch segment record in WAL.
> * Fixed JVM crush during in-progress eviction and cache group stop.
> REST:
> * Fixed serialization of BinaryObjects to JSON.
>


Apache Ignite In-Memory Data Fabric 2.5

---


2018-07-11 9:54 GMT+03:00 Dmitriy Setrakyan :

> Andrey, this is the link I have:
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
>
> This list does not look short. It looks like a copy of 2.5.
>
> D.
>
> On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura  wrote:
>
> > Sorry,
> >
> > You could check it using provided links.
> >
> >
> >
> > ср, 11 июл. 2018 г., 5:41 Andrey Gura :
> >
> > > Dmitry,
> > >
> > > It is emergency release so we have very short list of changes. You
> could
> > > check it using provided links.
> > >
> > >
> > > ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan :
> > >
> > >> Not sure if this is worth a down vote, but the release notes seem
> like a
> > >> copy of 2.5 release. I think 2.6 should have its own release notes.
> > >>
> > >> D.
> > >>
> > >> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura 
> wrote:
> > >>
> > >> > Igniters,
> > >> >
> > >> > We've uploaded a 2.6.0 release candidate to
> > >> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
> > >> >
> > >> > Git tag name is 2.6.0-rc1.
> > >> >
> > >> > This release includes the following changes:
> > >> >
> > >> > Ignite:
> > >> > * Fixed incorrect calculation of client affinity assignment with
> > >> baseline.
> > >> > * Fixed incorrect calculation of switch segment record in WAL.
> > >> > * Fixed JVM crush during in-progress eviction and cache group stop.
> > >> >
> > >> > REST:
> > >> > * Fixed serialization of BinaryObjects to JSON.
> > >> >
> > >> > Complete list of closed issues:
> > >> >
> > >> https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20IGNITE%20AND%
> > >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> > >> > 20closed%20or%20status%20%3D%20resolved)
> > >> >
> > >> > DEVNOTES
> > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> > >> >
> > >> > RELEASE NOTES
> > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> > >> >
> > >> > Please start voting.
> > >> >
> > >> > +1 - to accept Apache Ignite 2.6.0-RC1
> > >> > 0 - don't care either way
> > >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> > >> >
> > >> > This vote will go for 72 hours.
> > >> >
> > >>
> > >
> >
>



-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

[jira] [Created] (IGNITE-8864) sql-query-put x 5 performance drop

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-8864:


 Summary: sql-query-put x 5 performance drop
 Key: IGNITE-8864
 URL: https://issues.apache.org/jira/browse/IGNITE-8864
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Ilya Suntsov


Between commits, 631b659 and 303bd356 is a cause of x 5 performance drop on sql 
query put.

Configuration:
 * wal mode BACKGROUND
 * sync mode PRIMARY SYNC
 * 4 serv 8 clients

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8733) Add benchmarks for NodeJS thin client

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-8733:


 Summary: Add benchmarks for NodeJS thin client
 Key: IGNITE-8733
 URL: https://issues.apache.org/jira/browse/IGNITE-8733
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Ilya Suntsov


We have several benchmarks for Java thin client 
([PR|https://github.com/apache/ignite/pull/3942]). The same set should be 
implemented on NodeJS



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Apache ignite client for YCSB

[Ilya Suntsov]

Hi Brian,

I would like to add Apache Ignite (https://apacheignite.readme.io/docs)
client to YCSB repository.

Pull request passed all travis tests:
https://github.com/brianfrankcooper/YCSB/pull/1118

Could you please take a look at this PR?
-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

[Ilya Suntsov]

Dmitriy,

I've measured performance on the current master and haven't found any
problems with in-memory mode.

On Tue, Apr 10, 2018, 20:33 Dmitriy Setrakyan <dsetrak...@apache.org> wrote:

> I am not convinced that the performance degradation is only due to the new
> change that fixes the incorrect behavior. To my knowledge, there is also a
> drop in memory-only mode. Can someone explain why do we have such a drop?
>
> D.
>
> On Tue, Apr 10, 2018 at 9:08 AM, Vladimir Ozerov <voze...@gridgain.com>
> wrote:
>
> > 16% looks perfectly ok to me provided that we compare correct
> > implementation with incorrect one.
> >
> > вт, 10 апр. 2018 г. в 18:24, Dmitriy Setrakyan <d...@gridgain.com>:
> >
> > > Ilya, can we find out why pure in-memory scenario also had a
> performance
> > > drop and which commit caused it? It should not be affected by changes
> in
> > > persistence at all.
> > >
> > > D.
> > >
> > > On Tue, Apr 10, 2018 at 7:56 AM, Ilya Suntsov <isunt...@gridgain.com>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > Looks like commit:
> > > >
> > > > d0adb61ecd9af0d9907e480ec747ea1465f97cd7 is the first bad commit
> > > > > commit d0adb61ecd9af0d9907e480ec747ea1465f97cd7
> > > > > Author: Ivan Rakov <ivan.glu...@gmail.com>
> > > > > Date:   Tue Mar 27 20:11:52 2018 +0300
> > > > > IGNITE-7754 WAL in LOG_ONLY mode doesn't execute fsync on
> > > checkpoint
> > > > > begin - Fixes #3656.
> > > >
> > > >
> > > > was the cause of performance drop ( > 10% vs AI 2.4.0) on the
> following
> > > > benchmarks (LOG_ONLY):
> > > >
> > > >- atomic-put  (16 %)
> > > >- atomic-putAll (14 %)
> > > >- tx-putAll (11 %)
> > > >
> > > > As I understand it is greater than initial assessment.
> > > >
> > > > Thoughts?
> > > >
> > > > 2018-03-27 20:13 GMT+03:00 Dmitry Pavlov <dpavlov@gmail.com>:
> > > >
> > > > > Ivan, sure :)
> > > > >
> > > > > Thank you for this contribution, merged to master.
> > > > >
> > > > > вт, 27 мар. 2018 г. в 20:08, Ivan Rakov <ivan.glu...@gmail.com>:
> > > > >
> > > > > > Dmitry,
> > > > > >
> > > > > > Firstly PR contained dirty fix for performance measurement, but
> now
> > > it
> > > > > > contains good fix. :) Sorry for inconvenience.
> > > > > > I've renamed the PR.
> > > > > >
> > > > > > Best Regards,
> > > > > > Ivan Rakov
> > > > > >
> > > > > > On 27.03.2018 19:40, Dmitry Pavlov wrote:
> > > > > > > Hi Eduard, thank you for review.
> > > > > > >
> > > > > > > Hi Ivan,
> > > > > > >
> > > > > > > I'm confused on PR naming
> > > > > > > https://github.com/apache/ignite/pull/3656
> > > > > > >
> > > > > > > Could you rename?
> > > > > > >
> > > > > > > Sincerely,
> > > > > > > Dmitriy Pavlov
> > > > > > >
> > > > > > > вт, 27 мар. 2018 г. в 19:38, Eduard Shangareev <
> > > > > > eduard.shangar...@gmail.com
> > > > > > >> :
> > > > > > >> Ivan, I have reviewed your changes, looks good.
> > > > > > >>
> > > > > > >> On Tue, Mar 27, 2018 at 2:56 PM, Ivan Rakov <
> > > ivan.glu...@gmail.com>
> > > > > > wrote:
> > > > > > >>
> > > > > > >>> Igniters,
> > > > > > >>>
> > > > > > >>> I've completed development of https://issues.apache.org/jira
> > > > > > >>> /browse/IGNITE-7754. TeamCity state is ok. Please, review my
> > > > changes.
> > > > > > >>> Please note that it will be possible to track time of WAL
> fsync
> > > on
> > > > > > >>> checkpoint begin by *walCpRecordFsyncDuration *metric in
> > > > "Checkpoint
> > > > > > >>> started" message.
> > > > > > >>>
> >

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

[Ilya Suntsov]

t;>>>>>>>>>>>>> mode.
> > >>>>>>>>>> On Wed, Mar 21, 2018 at 6:11 PM, Dmitry Pavlov
> > >>>>>>>>>>>>>>>>> <dpavlov@gmail.com>
> > >>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Hi, I think option 1 is better. As Val said any mode
> that
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> allows
> > >>>>>>>>>>>>>>> corruption
> > >>>>>>>>>> does not make much sense.
> > >>>>>>>>>>>>>>>>>> What Ivan mentioned here as drop, in relation to old
> > mode
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> DEFAULT
> > >>>>>>>>>>>>>>>> (FSYNC
> > >>>>>>>>>>> now), is still significant perfromance boost.
> > >>>>>>>>>>>>>>>>> Sincerely,
> > >>>>>>>>>>>>>>>>>> Dmitriy Pavlov
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ср, 21 мар. 2018 г. в 17:56, Ivan Rakov <
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com
> > >>>>>>>>>>>>>>>> :
> > >>>>>>>>>> I've attached benchmark results to the JIRA ticket.
> > >>>>>>>>>>>> We observe ~7% drop in "fair" LOG_ONLY_SAFE mode,
> > >>>>>>>>>>>>>>>>>>> independent
> > >>>>>>>>>>>>>>>>> of
> > >>>>>>>>> WAL
> > >>>>>>>>>>> compaction enabled flag. It's pretty significant drop: WAL
> > >>>>>>>>>>>>>>>>> compaction
> > >>>>>>>>>>>>>>>>> itself gives only ~3% drop.
> > >>>>>>>>>>>>>>>>> I see two options here:
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> 1) Change LOG_ONLY behavior. That implies that we'll
> be
> > >>>>>>>>>>>>>>>>>>> ready
> > >>>>>>>>>>>>>>>>> to
> > >>>>>>>>> release
> > >>>>>>>>>>> AI 2.5 with 7% drop.
> > >>>>>>>>>>>>>>>>>> 2) Introduce LOG_ONLY_SAFE, make it default, add
> release
> > >>>>>>>>>>>>>>>>>>> note
> > >>>>>>>>>>>>>>>>> to AI
> > >>>>>>>>> 2.5
> > >>>>>>>>>>>>>>>>>> that we added power loss durability in default mode,
> but
> > >>>>>>>>>>>>>>>>> user
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> may
> > >>>>>>>>>>>>>>> fallback to previous LOG_ONLY in order to retain
> > >>>>>>>>>> performance.
> > >>>>>>>>>>>>>>>>> Thoughts?
> > >>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>>> Ivan Rakov
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> On 20.03.2018 16:00, Ivan Rakov wrote:
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> Val,
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> If a storage is in
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> corrupted state, does it mean that it needs to be
> > >>>>>>>>>>>>>>>>>>>>> completely
> > >>>>>>>>>>>>>>>>>>> removed
> > >>>>>>>>>> and
> > >>>>>>>>>>>>>>>>>> cluster needs to be restarted without data?
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> Yes, there's a chance that in LOG_ONLY all local data
> > >> will
> > >>>>>>>>>>>>>>>>>>>> be
> > >>>>>>>>>>>>>>>>>> lost,
> > >>>>>>>>>> but only in *power loss**/ OS crash* case.
> > >>>>>>>>>>>>>>>>> kill -9, JVM crash, death of critical system thread and
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> all
> > >>>>>>>>>>>>>>>>>> other
> > >>>>>>>>> cases that usually take place are variations of *process
> > >>>>>>>>>>>>>>>>>>>> crash*.
> > >>>>>>>>>>>>>>>>>> All
> > >>>>>>>>>>> WAL modes (except NONE, of course) ensure corruption-safety
> > >>>>>>>>>>>>>>>>> in
> > >>>>>>>>>>>>>>> case
> > >>>>>>>>> of
> > >>>>>>>>>>>>>>>>> process crash.
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> If so, I'm not sure any mode
> > >>>>>>>>>>>>>>>>>>>> that allows corruption makes much sense to me.
> > >>>>>>>>>>>>>>>>>>>>> It depends on performance impact of enforcing
> > >> power-loss
> > >>>>>>>>>>>>>>>>>>>> corruption
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> safety. Price of full protection from power loss is
> > high
> > >> -
> > >>>>>>>>>>>>>>>>> FSYNC
> > >>>>>>>>>>>>>> is
> > >>>>>>>>> way slower (2-10 times) than other WAL modes. The question is
> > >>>>>>>>>>>>>>>>> whether
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> ensuring weaker guarantees (corruption can't happen,
> but
> > >>>>>>>>>>>>>>>>>> loss
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> of
> > >>>>>>>>>>>>>>> last
> > >>>>>>>>>> updates can) will affect performance as badly as strong
> > >>>>>>>>>>>>>>>>>> guarantees.
> > >>>>>>>>>>>>>>>>>> I'll share benchmark results soon.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> Ivan Rakov
> > >>>>>>>>>>>>>>>>>>>> On 20.03.2018 5:09, Valentin Kulichenko wrote:
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> Guys,
> > >>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> What do we understand under "data corruption" here?
> > If
> > >> a
> > >>>>>>>>>>>>>>>>>>>>> storage
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> is
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> in
> > >>>>>>>>>>>>>>>>>> corrupted state, does it mean that it needs to be
> > >> completely
> > >>>>>>>>>>>>>>>>>> removed
> > >>>>>>>>>>>>>>>>>>> and
> > >>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> cluster needs to be restarted without data? If so, I'm
> > not
> > >>>>>>>>>>>>>>>>>> sure
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> any
> > >>>>>>>>>> mode
> > >>>>>>>>>>>>>>>>>> that allows corruption makes much sense to me. How am
> I
> > >>>>>>>>>>>>>>>>>> supposed
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> to
> > >>>>>>>>>>> use a
> > >>>>>>>>>>>>>>>>>> database, if virtually any failure can end with
> complete
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> loss of
> > >>>>>>>>>>>>>>>>>>>>> data?
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> In any case, this definitely should not be a default
> > >>>>>>>>>>>>>>>>>> behavior.
> > >>>>>>>>>>>>>>>> If
> > >>>>>>>>> user ever
> > >>>>>>>>>>>>>>>>>> switches to corruption-unsafe mode, there should be a
> > >>>>>>>>>>>>>>>>>> clear
> > >>>>>>>>>>>>>>>>>>> warning
> > >>>>>>>>> about
> > >>>>>>>>>>>>>>>>>> this.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> -Val
> > >>>>>>>>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 1:06 AM, Ivan Rakov <
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com>
> > >>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>> Ticket to track changes:
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-7754
> > >>>>>>>>>>>>>>>>>>>>>> Best Regards,
> > >>>>>>>>>>>>>>>>>>>>>> Ivan Rakov
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> On 16.03.2018 10:58, Dmitriy Setrakyan wrote:
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 12:55 AM, Ivan Rakov <
> > >>>>>>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>>> Vladimir,
> > >>>>>>>>>>>>>>>>>>>> Unlike BACKGROUND, LOG_ONLY provides strict write
> > >>>>>>>>>>>>>>>>>>>>>>> guarantees
> > >>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>> unless power
> > >>>>>>>>>>> loss has happened.
> > >>>>>>>>>>>>>>>>>>>>>>>> Seems like we need to measure performance
> > difference
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>> to
> > >>>>>>>>>>>>>>>>>>>>>> decide
> > >>>>>>>>> whether do
> > >>>>>>>>>>>>>>>>>>>>> we need separate WAL mode. If it will be invisible,
> > >>>>>>>>>>>>>>>>>> we'll
> > >>>>>>>>>>>>>>>>>>>>>> just
> > >>>>>>>>>> fix
> > >>>>>>>>>>>>>>>>>>>>> these
> > >>>>>>>>>>>>>>>>>> bugs without introducing new mode; if it will be
> > >>>>>>>>>>>>>>>>>>>> perceptible,
> > >>>>>>>>>>>>>>>>>>>>>>>> we'll
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>> continue the discussion about introducing
> > >>>>>>>>>>>>>>>>>>>>>> LOG_ONLY_SAFE.
> > >>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>> Makes sense?
> > >>>>>>>>>>>>>>>>>>>> Yes, this sounds like the right approach.
> > >>>>>>>>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>>>>>>>
> >
> >
>



-- 
Best Regards,
Ilya Suntsov
email: isunt...@gridgain.com
*GridGain Systems*
www.gridgain.com

[jira] [Created] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7768:


 Summary: No description for 
org.apache.ignite.ml.nn.trainers.distributed
 Key: IGNITE-7768
 URL: https://issues.apache.org/jira/browse/IGNITE-7768
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.4
Reporter: Ilya Suntsov
Assignee: Artem Malykh


We need to add description for package 
org.apache.ignite.ml.nn.trainers.distributed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7410) IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7410:


 Summary: IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs 
 Key: IGNITE-7410
 URL: https://issues.apache.org/jira/browse/IGNITE-7410
 Project: Ignite
  Issue Type: Bug
  Components: yardstick
Affects Versions: 2.4
Reporter: Ilya Suntsov
 Attachments: logs_sparse-distributed-matrix-mul.zip

I tried to run the benchmarks bellow on 2 servers and 3 clients:
 * IgniteSparseDistributedMatrixMulBenchmark

 * IgniteSparseDistributedMatrixMul2Benchmark

They hang.

I've attached logs and configs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7245) Missing description in javadoc for ignite-dev-utils

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7245:


 Summary: Missing description in javadoc for ignite-dev-utils
 Key: IGNITE-7245
 URL: https://issues.apache.org/jira/browse/IGNITE-7245
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov
Priority: Minor


Need add description in java doc



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7244) Missing README.txt for ignite-dev-utils module

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7244:


 Summary: Missing README.txt for ignite-dev-utils module
 Key: IGNITE-7244
 URL: https://issues.apache.org/jira/browse/IGNITE-7244
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


We need to add some information about this module in README.txt




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7241) Create shell (bat) script for run IgniteWalConverter

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7241:


 Summary: Create shell (bat) script for run IgniteWalConverter
 Key: IGNITE-7241
 URL: https://issues.apache.org/jira/browse/IGNITE-7241
 Project: Ignite
  Issue Type: Improvement
  Components: build
Affects Versions: 2.3
Reporter: Ilya Suntsov


IgniteWalConverter allow us to parse WAL.
I guess we should add to {{bin}} directory script that will start this 
converter with parameters.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7240) Upload ignite-dev-utils module in maven

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7240:


 Summary: Upload ignite-dev-utils module in maven
 Key: IGNITE-7240
 URL: https://issues.apache.org/jira/browse/IGNITE-7240
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 2.1
Reporter: Ilya Suntsov


Module  ignite-dev-utils allow us to parse WAL.
We should upload it to maven.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7212) Load stoped after server node kill

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7212:


 Summary: Load stoped after server node kill
 Key: IGNITE-7212
 URL: https://issues.apache.org/jira/browse/IGNITE-7212
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.4
Reporter: Ilya Suntsov
Priority: Critical


Scenario:
* Start 4 servers
* Start load tasks on 5 clients
* Kill 1 server
* Waiting for rebalancing
* Kill 1 server
Result:
After the kill of second servers node load stoped.
In servers logs I see messages like this:
{noformat}
[2017-12-15 11:23:50][DEBUG][grid-nio-worker-tcp-comm-0-#41] Remote client 
closed connection: GridSelectorNioSessionImpl [worker=DirectNioClientWorker 
[super=AbstractNioClientWorker [idx=0, bytesRcvd=130952565, 
bytesSent=131203245, bytesRcvd0=3069200, bytesSent0=3068083, select=true, 
super=GridWorker [name=grid-nio-worker-tcp-comm-0, igniteInstanceName=null, 
finished=false, hashCode=1748650517, interrupted=false, 
runner=grid-nio-worker-tcp-comm-0-#41]]], 
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
readBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
inRecovery=GridNioRecoveryDescriptor [acked=1024, resendCnt=0, rcvCnt=1026, 
sentCnt=1029, reserved=true, lastAck=1024, nodeLeft=false, 
node=TcpDiscoveryNode [id=b7cfaa4e-b3b7-4485-a421-c731d9ed869d, 
addrs=[127.0.0.1, 172.31.20.3], 
sockAddrs=[ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3:47500, 
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1513335739604, loc=false, ver=2.4.0#20171214-sha1:da782958, 
isClient=false], connected=false, connectCnt=1, queueLimit=4096, reserveCnt=1, 
pairedConnections=false], outRecovery=GridNioRecoveryDescriptor [acked=1024, 
resendCnt=0, rcvCnt=1026, sentCnt=1029, reserved=true, lastAck=1024, 
nodeLeft=false, node=TcpDiscoveryNode [id=b7cfaa4e-b3b7-4485-a421-c731d9ed869d, 
addrs=[127.0.0.1, 172.31.20.3], 
sockAddrs=[ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3:47500, 
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1513335739604, loc=false, ver=2.4.0#20171214-sha1:da782958, 
isClient=false], connected=false, connectCnt=1, queueLimit=4096, reserveCnt=1, 
pairedConnections=false], super=GridNioSessionImpl 
[locAddr=/172.31.23.220:41732, 
rmtAddr=ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3:47100, 
createTime=1513335774008, closeTime=0, bytesSent=131203245, 
bytesRcvd=130952565, bytesSent0=3068083, bytesRcvd0=3069200, 
sndSchedTime=1513335774008, lastSndTime=1513337029027, 
lastRcvTime=1513337029027, readsPaused=false, 
filterChain=FilterChain[filters=[GridNioCodecFilter 
[parser=org.apache.ignite.internal.util.nio.GridDirectParser@11ae7d3b, 
directMode=true], GridConnectionBytesVerifyFilter], accepted=false]]
[2017-12-15 11:23:50][WARN ][tcp-disco-msg-worker-#2] Failed to send message to 
next node [msg=TcpDiscoveryConnectionCheckMessage 
[super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
id=6c7f6d95061-c3cf9fe4-ab13-4d95-ace3-84a54cd73e08, verifierNodeId=null, 
topVer=0, pendingIdx=0, failedNodes=null, isClient=false]], 
next=TcpDiscoveryNode [id=b7cfaa4e-b3b7-4485-a421-c731d9ed869d, 
addrs=[127.0.0.1, 172.31.20.3], 
sockAddrs=[ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3:47500, 
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1513335739604, loc=false, ver=2.4.0#20171214-sha1:da782958, 
isClient=false], errMsg=Failed to send message to next node 
[msg=TcpDiscoveryConnectionCheckMessage [super=TcpDiscoveryAbstractMessage 
[sndNodeId=null, id=6c7f6d95061-c3cf9fe4-ab13-4d95-ace3-84a54cd73e08, 
verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, 
isClient=false]], next=ClusterNode [id=b7cfaa4e-b3b7-4485-a421-c731d9ed869d, 
order=1, addr=[127.0.0.1, 172.31.20.3], daemon=false]]]
[2017-12-15 11:23:50][DEBUG][grid-nio-worker-tcp-comm-0-#41] Session was closed 
but there are unacknowledged messages, will try to reconnect 
[rmtNode=b7cfaa4e-b3b7-4485-a421-c731d9ed869d]
[2017-12-15 11:23:50][DEBUG][tcp-comm-worker-#1] Recovery reconnect 
[rmtNode=b7cfaa4e-b3b7-4485-a421-c731d9ed869d]
[2017-12-15 11:23:50][DEBUG][tcp-comm-worker-#1] Creating NIO client to node: 
TcpDiscoveryNode [id=b7cfaa4e-b3b7-4485-a421-c731d9ed869d, addrs=[127.0.0.1, 
172.31.20.3], 
sockAddrs=[ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3:47500, 
/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
lastExchangeTime=1513335739604, loc=false, ver=2.4.0#20171214-sha1:da782958, 
isClient=false]
[2017-12-15 11:23:50][DEBUG][tcp-comm-worker-#1] Addresses resolved from 
attributes [rmtNode=b7cfaa4e-b3b7-4485-a421-c731d9ed869d, 
addrs=[ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3:47100, 
/127.0.0.1:47100], isRmtAddrsExist=true]
[2017-12-15 11:23:50][DEBUG][tcp-comm-worker-#1] Client creation failed 
[addr=ip-172-31-20-3.us-east-2.compute.internal/172.31.20.3

Re: Adding sqlline tool to Apache Ignite project

[Ilya Suntsov]

Guys,

I've created the ticket for 2.4 release:
https://issues.apache.org/jira/browse/IGNITE-6561

2017-08-30 22:21 GMT+03:00 Julian Hyde <jh...@apache.org>:

> Denis,
>
> I’m glad you’re thinking of using SQLLine. Under the BSD license, you
> don’t need my permission to distribute, but I grant that permission.
>
> Drill, Phoenix and Calcite already distribute SQLLine, so Ignite is in
> good company.
>
> If you need extensions, please discuss on the dev list, or open a GitHub
> case or pull request. SQLLine operates in the usual way for a GitHub
> project. It’s unlikely that you’ll need Ignite-specific extensions —
> SQLLine just exposes what comes through the JDBC driver — but we can
> discuss if the need arises. The Hive project forked SQLLine into its own
> Beeline module and I’d like to avoid a repeat of that.
>
> Julian
>
> > On Aug 29, 2017, at 6:35 PM, Denis Magda <dma...@apache.org> wrote:
> >
> > Igniters,
> >
> > Let me introduce Julian Hyde [1], creator of SQLLine tool and our Apache
> mate,
> >
> > Julian,
> >
> > Please grant that Apache Ignite community a permission to include
> SQLLine [2] it in every Ignite deliverable (source, binary). It’s planned
> to suggest the tool as a default command line SQL utility for Ignite
> clusters. SQLLite and Ignite usage will also be documented on Ignite’s
> technical documentation.
> >
> > [1] https://people.apache.org/~jhyde/ <https://people.apache.org/~jhyde/
> >
> > [2] https://github.com/julianhyde/sqlline <https://github.com/
> julianhyde/sqlline>
> >
> > —
> > Denis
> >
> >> On Aug 25, 2017, at 9:17 AM, Denis Magda <dma...@apache.org  dma...@apache.org>> wrote:
> >>
> >> Hi Ilya,
> >>
> >> Thanks for the clarification! Referring to the page shared by you [1]
> if we need to get author’s consent in a written form:
> >>
> >> A permissive license similar to the BSD 2-Clause License, but with a
> 3rd clause that prohibits others from using the name of the project or its
> contributors to promote derived products without written consent.
> >>
> >> [1] https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE> <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE>>
> >>
> >> I’ll reach out the author requesting the permit.
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 25, 2017, at 9:12 AM, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com <mailto:ilya.kasnach...@gmail.com>> wrote:
> >>>
> >>> Hi Denis,
> >>>
> >>> There are two kinds of BSD license, 3-clause and 4-clause. The
> difference
> >>> between them is advertising clause:
> >>>
> >>> "3. All advertising materials mentioning features or use of this
> software
> >>> must display the following acknowledgement: This product includes
> software
> >>> developed by the University of California, Berkeley and its
> contributors."
> >>>
> >>> which is causing problems with other licenses and which sqlline's
> license
> >>> doesn't contain:
> >>> https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE>
> >>> So it should be all good for inclusion.
> >>>
> >>> --
> >>> Ilya Kasnacheev.
> >>>
> >>> 2017-08-25 18:48 GMT+03:00 Denis Magda <dma...@apache.org>:
> >>>
> >>>> Hi Ilya,
> >>>>
> >>>> It will be a useful addition to Ignite. I would include the tool in
> one of
> >>>> the nearest releases. It’s license is BSD-3 which is compatible with
> ours.
> >>>> However, there is a note on ASF side saying that BSD licenses can be
> >>>> included without advertising clause [1]. What does it mean for us?
> Can we
> >>>> document the tool and mention on our site?
> >>>>
> >>>> [1] https://www.apache.org/legal/resolved.html#category-a <
> >>>> https://www.apache.org/legal/resolved.html#category-a>
> >>>>
> >>>> —
> >>>> Denis
> >>>>
> >>>>> On Aug 25, 2017, at 8:32 AM, Ilya Suntsov <isunt...@gridgain.com>
> wrote:
> >>>>>
> >>>>> Hi Igniters,
> >>>>>
> >>>>> I've found one command line tool that can be used for execute queries
> >>>>> (DDL/DML) with data from Apache Ignite grid via
> >>>>> *org.apache.ignite.IgniteJdbcThinDriver*.
> >>>>>
> >>>>> Here you can find overview of internal commands of this tool:
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/
> Overview+sqlline+tool
> >>>>>
> >>>>> The most problems with sqlline relate with some issues from our side
> or
> >>>>> some unsupported features.
> >>>>>
> >>>>> Would be nice to add tool like this (sqlline or something else) in
> our
> >>>>> project.
> >>>>>
> >>>>> Have you any objections or other thoughts?
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Ilya Suntsov
> >>>>
> >>>>
> >>
> >
>
>


-- 
Ilya Suntsov

Re: Adding sqlline tool to Apache Ignite project

[Ilya Suntsov]

Guys,

I've created ticket [1] for version 2.4.
https://issues.apache.org/jira/browse/IGNITE-6561

2017-08-30 22:21 GMT+03:00 Julian Hyde <jh...@apache.org>:

> Denis,
>
> I’m glad you’re thinking of using SQLLine. Under the BSD license, you
> don’t need my permission to distribute, but I grant that permission.
>
> Drill, Phoenix and Calcite already distribute SQLLine, so Ignite is in
> good company.
>
> If you need extensions, please discuss on the dev list, or open a GitHub
> case or pull request. SQLLine operates in the usual way for a GitHub
> project. It’s unlikely that you’ll need Ignite-specific extensions —
> SQLLine just exposes what comes through the JDBC driver — but we can
> discuss if the need arises. The Hive project forked SQLLine into its own
> Beeline module and I’d like to avoid a repeat of that.
>
> Julian
>
> > On Aug 29, 2017, at 6:35 PM, Denis Magda <dma...@apache.org> wrote:
> >
> > Igniters,
> >
> > Let me introduce Julian Hyde [1], creator of SQLLine tool and our Apache
> mate,
> >
> > Julian,
> >
> > Please grant that Apache Ignite community a permission to include
> SQLLine [2] it in every Ignite deliverable (source, binary). It’s planned
> to suggest the tool as a default command line SQL utility for Ignite
> clusters. SQLLite and Ignite usage will also be documented on Ignite’s
> technical documentation.
> >
> > [1] https://people.apache.org/~jhyde/ <https://people.apache.org/~jhyde/
> >
> > [2] https://github.com/julianhyde/sqlline <https://github.com/
> julianhyde/sqlline>
> >
> > —
> > Denis
> >
> >> On Aug 25, 2017, at 9:17 AM, Denis Magda <dma...@apache.org  dma...@apache.org>> wrote:
> >>
> >> Hi Ilya,
> >>
> >> Thanks for the clarification! Referring to the page shared by you [1]
> if we need to get author’s consent in a written form:
> >>
> >> A permissive license similar to the BSD 2-Clause License, but with a
> 3rd clause that prohibits others from using the name of the project or its
> contributors to promote derived products without written consent.
> >>
> >> [1] https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE> <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE>>
> >>
> >> I’ll reach out the author requesting the permit.
> >>
> >> —
> >> Denis
> >>
> >>> On Aug 25, 2017, at 9:12 AM, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com <mailto:ilya.kasnach...@gmail.com>> wrote:
> >>>
> >>> Hi Denis,
> >>>
> >>> There are two kinds of BSD license, 3-clause and 4-clause. The
> difference
> >>> between them is advertising clause:
> >>>
> >>> "3. All advertising materials mentioning features or use of this
> software
> >>> must display the following acknowledgement: This product includes
> software
> >>> developed by the University of California, Berkeley and its
> contributors."
> >>>
> >>> which is causing problems with other licenses and which sqlline's
> license
> >>> doesn't contain:
> >>> https://github.com/julianhyde/sqlline/blob/master/LICENSE <
> https://github.com/julianhyde/sqlline/blob/master/LICENSE>
> >>> So it should be all good for inclusion.
> >>>
> >>> --
> >>> Ilya Kasnacheev.
> >>>
> >>> 2017-08-25 18:48 GMT+03:00 Denis Magda <dma...@apache.org>:
> >>>
> >>>> Hi Ilya,
> >>>>
> >>>> It will be a useful addition to Ignite. I would include the tool in
> one of
> >>>> the nearest releases. It’s license is BSD-3 which is compatible with
> ours.
> >>>> However, there is a note on ASF side saying that BSD licenses can be
> >>>> included without advertising clause [1]. What does it mean for us?
> Can we
> >>>> document the tool and mention on our site?
> >>>>
> >>>> [1] https://www.apache.org/legal/resolved.html#category-a <
> >>>> https://www.apache.org/legal/resolved.html#category-a>
> >>>>
> >>>> —
> >>>> Denis
> >>>>
> >>>>> On Aug 25, 2017, at 8:32 AM, Ilya Suntsov <isunt...@gridgain.com>
> wrote:
> >>>>>
> >>>>> Hi Igniters,
> >>>>>
> >>>>> I've found one command line tool that can be used for execute queries
> >>>>> (DDL/DML) with data from Apache Ignite grid via
> >>>>> *org.apache.ignite.IgniteJdbcThinDriver*.
> >>>>>
> >>>>> Here you can find overview of internal commands of this tool:
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/
> Overview+sqlline+tool
> >>>>>
> >>>>> The most problems with sqlline relate with some issues from our side
> or
> >>>>> some unsupported features.
> >>>>>
> >>>>> Would be nice to add tool like this (sqlline or something else) in
> our
> >>>>> project.
> >>>>>
> >>>>> Have you any objections or other thoughts?
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Ilya Suntsov
> >>>>
> >>>>
> >>
> >
>
>


-- 
Ilya Suntsov

[jira] [Created] (IGNITE-6561) Include sqlline in Apache Ignite

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6561:


 Summary: Include sqlline in Apache Ignite
 Key: IGNITE-6561
 URL: https://issues.apache.org/jira/browse/IGNITE-6561
 Project: Ignite
  Issue Type: Improvement
  Components: build
Affects Versions: 2.3
Reporter: Ilya Suntsov
 Fix For: 2.4


I guess we need to include [sqlline|https://github.com/julianhyde/sqlline] in 
our project.
Here is overview of internal sqlline commands:
https://cwiki.apache.org/confluence/display/IGNITE/Overview+sqlline+tool



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6478) IndexOutOfBoundsException jdbc2

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6478:


 Summary: IndexOutOfBoundsException jdbc2
 Key: IGNITE-6478
 URL: https://issues.apache.org/jira/browse/IGNITE-6478
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.3


I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true 
--verbose=true --showWarnings=true --showNestedErrs=true -u 
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
 when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at 
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6479) IndexOutOfBoundsException jdbc2

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6479:


 Summary: IndexOutOfBoundsException jdbc2
 Key: IGNITE-6479
 URL: https://issues.apache.org/jira/browse/IGNITE-6479
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.3


I've connected to grid via jdbc2 (https://github.com/julianhyde/sqlline) :
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcDriver --color=true 
--verbose=true --showWarnings=true --showNestedErrs=true -u 
jdbc:ignite:cfg://cache=cache123:transactionsAllowed=true@/path_to_config/ignite-jdbc-config.xml
{noformat}
 when I tried to get list of tables I got exception:
{noformat}
0: jdbc:ignite:cfg://cache=cache123:transacti> !tables
java.lang.IndexOutOfBoundsException: Index: 0
at java.util.Collections$EmptyList.get(Collections.java:4454)
at 
org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata.getTableName(JdbcResultSetMetadata.java:120)
at sqlline.Rows.isPrimaryKey(Rows.java:68)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:106)
at sqlline.TableOutputFormat.getOutputString(TableOutputFormat.java:91)
at sqlline.TableOutputFormat.print(TableOutputFormat.java:35)
at sqlline.SqlLine.print(SqlLine.java:1648)
at sqlline.Commands.metadata(Commands.java:199)
at sqlline.Commands.tables(Commands.java:332)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
at sqlline.SqlLine.dispatch(SqlLine.java:791)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6457) Incorrect exception when used schema name in lower case

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6457:


 Summary: Incorrect exception when used schema name in lower case 
 Key: IGNITE-6457
 URL: https://issues.apache.org/jira/browse/IGNITE-6457
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.1
 Environment: Cache configuration:
{noformat}











{noformat}
Reporter: Ilya Suntsov
 Fix For: 2.3


Scenario:
1. Start 1 node
2. connect to node via sqlline (https://github.com/julianhyde/sqlline)
{noformat} ./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true 
--verbose=true --showWarnings=true --showNestedErrs=true -u 
jdbc:ignite:thin://127.0.0.1:10800/test{noformat}
3. Create table:
{noformat}CREATE TABLE city1 (id LONG PRIMARY KEY, name VARCHAR);{noformat}
Result:
{noformat}
[16:35:27,506][SEVERE][client-connector-#40%null%][JdbcRequestHandler] Failed 
to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=test, 
pageSize=1024, maxRows=0, sqlQry=CREATE TABLE city1 (id LONG PRIMARY KEY, name 
VARCHAR), args=[], stmtType=ANY_STATEMENT_TYPE]]
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
set schema for DB connection for thread [schema=test]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:439)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:356)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1287)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.h2.jdbc.JdbcSQLException: Schema "test" not found; SQL statement:
SET SCHEMA "test" [90079-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.engine.Database.getSchema(Database.java:1755)
at org.h2.command.dml.Set.update(Set.java:408)
at org.h2.command.CommandContainer.update(CommandContainer.java:101)
at org.h2.command.Command.executeUpdate(Command.java:260)
at 
org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:137)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:122)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:431)
... 19 more
{noformat}

So we have incorrect exception.

Correct one appears if used the following jdbc url: 
{{jdbc:ignite:thin://127.0.0.1:10800/TEST}}







--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6448) Select * doesn't return new field name after concurrent ALTER TABLE

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6448:


 Summary: Select * doesn't return new field name after concurrent 
ALTER TABLE 
 Key: IGNITE-6448
 URL: https://issues.apache.org/jira/browse/IGNITE-6448
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.1
Reporter: Ilya Suntsov
Priority: Blocker
 Fix For: 2.3


Steps for reproduce:
1. Start 3 nodes
2. Execute 
{noformat}CREATE TABLE person (id LONG, name VARCHAR, city_id LONG, PRIMARY KEY 
(id, city_id)) {noformat}
to create table Person
3. Connect to grid via sqlline (https://github.com/julianhyde/sqlline)
{noformat}./sqlline -d org.apache.ignite.IgniteJdbcThinDriver --color=true 
--verbose=true --showWarnings=true --showNestedErrs=true -u 
jdbc:ignite:thin://127.0.0.1/{noformat}
4. Create one more connection {noformat}!connect jdbc:ignite:thin://127.0.0.1/ 
{noformat}
5. Execute ALTER TABLE for both connections {noformat} !all alter table person 
add field1 varchar;{noformat}
Result:
1. Got exception on coordinator:
{noformat}[10:59:15,805][SEVERE][client-connector-#55%null%][JdbcRequestHandler]
 Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest 
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=alter table person add 
field1 varchar, args=[], stmtType=ANY_STATEMENT_TYPE]]
class org.apache.ignite.internal.processors.query.IgniteSQLException: Column 
already exists: FIELD1
at 
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:329)
at 
org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:273)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1383)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1918)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1914)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2396)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1922)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:286)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:149)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:141)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:40)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
2. When I try to get all data from Person:
{noformat}select * from person;{noformat}
I get the table without new field but if try to get only this field from table 
it works.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Apache Ignite 2.2.0 RC2

[Ilya Suntsov]

+1
Checked md5, sha512
Build from sources
Build examples

2017-09-16 10:45 GMT+03:00 Andrey Gura <ag...@apache.org>:

> +1
>
> 15 сент. 2017 г. 5:48 PM пользователь "Anton Vinogradov" <a...@apache.org>
> написал:
>
> > Igniters,
> >
> > We have uploaded a 2.2.0 release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.2.0-rc2/
> >
> > Git tag name is
> > 2.2.0-rc2
> >
> > This release includes the following changes:
> >
> > Ignite:
> > * Checkpointing algorithm optimized
> > * Default max memory size changed from 80% to 20%
> >
> > Complete list of closed issues:
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > 20fixVersion%20%3D%202.2%20AND%20(status%20%3D%
> > 20closed%20or%20status%20%3D%20resolved)
> >
> > DEVNOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=DEVNOTES.txt;hb=refs/tags/2.2.0-rc2
> >
> > RELEASE NOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.2.0-rc2
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 2.2.0-RC2
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 2.2.0-RC2 (explain why)
> >
> > This vote will go for 72 hours.
> >
>



-- 
Ilya Suntsov

[jira] [Created] (IGNITE-6315) Exception during DistributedRegressionExample (ML)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6315:


 Summary: Exception during DistributedRegressionExample (ML)
 Key: IGNITE-6315
 URL: https://issues.apache.org/jira/browse/IGNITE-6315
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.3


When I tried to start 
{noformat}examples/src/main/ml/org/apache/ignite/examples/ml/math/regression/DistributedRegressionExample.java{noformat}
I got exception:
{noformat}
>>> Ignite grid started.
>>> Create new SparseDistributedMatrix inside IgniteThread.
>>> Create new linear regression object
Exception in thread "SparseDistributedMatrixExample-#36%null%" class 
org.apache.ignite.ml.math.exceptions.UnsupportedOperationException: Unsupported 
operation.
at 
org.apache.ignite.ml.math.impls.matrix.SparseDistributedMatrix.likeVector(SparseDistributedMatrix.java:146)
at 
org.apache.ignite.ml.math.util.MatrixUtil.likeVector(MatrixUtil.java:87)
at 
org.apache.ignite.ml.regressions.AbstractMultipleLinearRegression.newSampleData(AbstractMultipleLinearRegression.java:126)
at 
org.apache.ignite.ml.regressions.OLSMultipleLinearRegression.newSampleData(OLSMultipleLinearRegression.java:96)
at 
org.apache.ignite.examples.ml.math.regression.DistributedRegressionExample.lambda$main$0(DistributedRegressionExample.java:115)
at 
org.apache.ignite.examples.ml.math.regression.DistributedRegressionExample$$Lambda$1/600958416.run(Unknown
 Source)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: New API docs look for Ignite.NET

[Ilya Suntsov]

Pavel, thanks!
It is the great news!
Looks like DocFX will save 30-40 min.

2017-09-05 11:16 GMT+03:00 Pavel Tupitsyn <ptupit...@apache.org>:

> Igniters and users,
>
> Historically we've been using Doxygen [1] to generate .NET API
> documentation [2].
>
> Recently it became very slow on our code base (more than 30 minutes to
> generate), and I could not find any solution or tweak to fix that. Other
> issues include outdated looks and limited customization possibilities.
>
> I propose to replace it with DocFX [3] [4]:
> - Popular .NET Foundation project
> - Good looks and usability out of the box
> - Easy to set up
>
> Our docs will look like this: [5]
> Let me know if you have any objections or suggestions.
>
> Pavel
>
>
> [1] http://www.stack.nl/~dimitri/doxygen/
> [2] https://ignite.apache.org/releases/latest/dotnetdoc/index.html
> [3] https://dotnet.github.io/docfx/
> [4] https://issues.apache.org/jira/browse/IGNITE-6253
> [5] https://ptupitsyn.github.io/docfx-test/api/index.html
>



-- 
Ilya Suntsov

[jira] [Created] (IGNITE-6226) Review docs for integration with Apache Zeppelin

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6226:


 Summary: Review docs for integration with Apache Zeppelin
 Key: IGNITE-6226
 URL: https://issues.apache.org/jira/browse/IGNITE-6226
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.1
Reporter: Ilya Suntsov
Assignee: Ilya Suntsov
 Fix For: 2.3


Now we have non actual documentation for Apache Zeppelin integration: 
https://apacheignite.readme.io/v1.1/docs/data-analysis-with-apache-zeppelin?edits=true



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Adding sqlline tool to Apache Ignite project

[Ilya Suntsov]

Hi Igniters,

I've found one command line tool that can be used for execute queries
(DDL/DML) with data from Apache Ignite grid via
*org.apache.ignite.IgniteJdbcThinDriver*.

Here you can find overview of internal commands of this tool:
https://cwiki.apache.org/confluence/display/IGNITE/Overview+sqlline+tool

The most problems with sqlline relate with some issues from our side or
some unsupported features.

Would be nice to add tool like this (sqlline or something else) in our
project.

Have you any objections or other thoughts?


-- 
Ilya Suntsov

[jira] [Created] (IGNITE-6177) Update docs for integration with Apache Zeppelin

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6177:


 Summary: Update docs for integration with Apache Zeppelin
 Key: IGNITE-6177
 URL: https://issues.apache.org/jira/browse/IGNITE-6177
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.2


Since release AI 1.1 we haven't updated the following documentation section:
https://apacheignite.readme.io/v1.1/docs/data-analysis-with-apache-zeppelin



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6152) Wrong response from grid via jdbc driver

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6152:


 Summary: Wrong response from grid via jdbc driver
 Key: IGNITE-6152
 URL: https://issues.apache.org/jira/browse/IGNITE-6152
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.1
 Environment: OS X 10.10.5
java version "1.8.0_91"
Reporter: Ilya Suntsov
 Fix For: 2.2


Now I'm testing command line tool - *sqlline* ([link to 
github|https://github.com/julianhyde/sqlline]) for execute sql queries to AI 
grid via thin jdbc driver.

When I was trying to get column list from AI grid and H2 database I got 2 
different responses from the same table.
Ignite:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> !columns person
++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |
++++
|| PUBLIC | PERSON  
   |
|| PUBLIC | PERSON  
   |
|| PUBLIC | PERSON  
   |
++++
{noformat}  

H2:
{noformat}
+---+-++-+-+---+-+---+++-+-++---+--+---+
| TABLE_CAT | TABLE_SCHEM | TABLE_NAME | COLUMN_NAME |  DATA_TYPE  | TYPE_NAME 
| COLUMN_SIZE | BUFFER_LENGTH | DECIMAL_DIGITS | NUM_PREC_RADIX |  NULLABLE   | 
REMARKS | COLUMN_DEF | SQL_DATA_TYPE | SQL_DATETIME_SUB | CHAR_OCTE |
+---+-++-+-+---+-+---+++-+-++---+--+---+
| TEST" | PUBLIC  | PERSON | ID  | -5  | BIGINT
| 19  | 19| 0  | 10 | 0   | 
|| -5| 0| 19|
| TEST" | PUBLIC  | PERSON | NAME| 12  | VARCHAR   
| 2147483647  | 2147483647| 0  | 10 | 1   | 
|| 12| 0| 214748364 |
| TEST" | PUBLIC  | PERSON | CITY_ID | -5  | BIGINT
| 19  | 19| 0  | 10 | 0   | 
|| -5| 0| 19|
+---+-++-+-+---+-+---+++-+-++---+--+---+
{noformat}






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6126) Compilation error (yardstick repo)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-6126:


 Summary: Compilation error (yardstick repo)
 Key: IGNITE-6126
 URL: https://issues.apache.org/jira/browse/IGNITE-6126
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


Steps for reproduce:
1. Clone 
{noformat}https://github.com/apacheignite/yardstick-ignite.git{noformat}
2. Change version of apache ignite from 1.9.0 to 2.1.0
3.{noformat}mvn clean package{noformat}
Result:
{noformat}
[WARNING] COMPILATION WARNING : 
[INFO] -
[WARNING] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/failover/IgniteFailoverAbstractBenchmark.java:
 Some input files use or override a deprecated API.
[WARNING] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/failover/IgniteFailoverAbstractBenchmark.java:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/CacheEntryEventProbe.java:
 Some input files use unchecked or unsafe operations.
[WARNING] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/CacheEntryEventProbe.java:
 Recompile with -Xlint:unchecked for details.
[INFO] 4 warnings 
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/IgniteNode.java:[45,38]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/IgniteNode.java:[45,1]
 static import only from classes and interfaces
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/IgniteBenchmarkArguments.java:[21,31]
 cannot find symbol
  symbol:   class CacheAtomicWriteOrderMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/IgniteBenchmarkArguments.java:[69,13]
 cannot find symbol
  symbol:   class CacheAtomicWriteOrderMode
  location: class org.apache.ignite.yardstick.IgniteBenchmarkArguments
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/IgniteBenchmarkArguments.java:[243,12]
 cannot find symbol
  symbol:   class CacheAtomicWriteOrderMode
  location: class org.apache.ignite.yardstick.IgniteBenchmarkArguments
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgnitePutTxOffHeapBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/failover/IgniteFailoverAbstractBenchmark.java:[41,77]
 cannot find symbol
  symbol:   class GridDhtPartitionMap2
  location: package 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgniteSqlQueryJoinOffHeapBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgnitePutGetTxOffHeapValuesBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgnitePutOffHeapValuesBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgniteGetOffHeapValuesBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgnitePutGetOffHeapBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgniteSqlQueryOffHeapBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR] 
/Users/gridgain/TRASH/yardstick-ignite/src/main/java/org/apache/ignite/yardstick/cache/IgnitePutOffHeapBenchmark.java:[21,31]
 cannot find symbol
  symbol:   class CacheMemoryMode
  location: package org.apache.ignite.cache
[ERROR

Re: [VOTE] Apache Ignite 2.1.0 RC1

[Ilya Suntsov]

Lgpl binaries should not to be in svn. This build will be removed.

15 июля 2017 г. 1:52 PM пользователь "Sergey Kozlov" 
написал:

> Igniters
>
> Could someone explain why we include LGPL binary fabric [1] in the release?
> Either it was a mistake or we should upload also SHA1/MD5/ASC checksums as
> well
>
>
> [1]
> https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
> apache-ignite-fabric-lgpl-2.1.0-bin.zip
>
> On Fri, Jul 14, 2017 at 8:45 PM, Vladimir Ozerov 
> wrote:
>
> > gniters!
> >
> > We have uploaded a 2.1.0 release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc1/
> >
> > Git tag name is
> > 2.1.0-rc1
> >
> > This release includes the following changes:
> >
> > Ignite:
> > * Persistent cache store
> > * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync() mehtods
> > * Deprecated IgniteConfiguration.marshaller
> > * Updated Lucene dependency to version 5.5.2
> > * Machine learning: implemented K-means clusterization algorithm
> optimized
> > for distributed storages
> > * SQL: CREATE TABLE and DROP TABLE commands support
> > * SQL: New thin JDBC driver
> > * SQL: Improved performance of certain queries, when affinity node can be
> > calculated in advance
> > * SQL: Fixed return type of AVG() function
> > * SQL: BLOB type support added to thick JDBC driver
> > * SQL: Improved LocalDate, LocalTime and LocalDateTime support for Java 8
> > * SQL: Added FieldsQueryCursor interface to get fields metadata for
> > SqlFieldsQuery
> > * ODBC: Implemented DML statement batching
> > * Massive performance and stability improvements
> >
> > Ignite.NET:
> > * Automatic remote assembly loading
> > * NuGet-based standalone node deployment
> > * Added conditional data removeal via LINQ DeleteAll
> > * Added TimestampAttribute to control DateTime serialization mode
> > * Added local collections joins support to LINQ.
> >
> > Ignite CPP:
> > * Added Compute::Call and Compute::Broadcast methods
> >
> > Web Console:
> > * Implemented support for UNIQUE indexes for key fields on import model
> > from RDBMS
> > * Added option to show full stack trace on Queries screen
> > * Added PK alias generation on Models screen.
> >
> > Complete list of closed issues:
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > 20fixVersion%20%3D%202.1%20AND%20(status%20%3D%
> > 20closed%20or%20status%20%3D%20resolved)
> >
> > DEVNOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=DEVNOTES.txt;hb=refs/tags/2.1.0-rc1
> >
> > RELEASE NOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc1
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 2.1.0-rc1
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 2.1.0-rc1 (explain why)
> >
> > This vote will go for 72 hours.
> >
> > Vladimir.
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

[jira] [Created] (IGNITE-5735) NPE during populated data (CacheQueryDdlExample)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5735:


 Summary: NPE during populated data (CacheQueryDdlExample)
 Key: IGNITE-5735
 URL: https://issues.apache.org/jira/browse/IGNITE-5735
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1
Reporter: Ilya Suntsov
 Fix For: 2.1


Steps for reproduce:
1. Start 2 nodes with *examples/config/example-ignite.xml*
2. Start *CacheQueryDdlExample*
Result:
Om example node:
{noformat}
[10:19:17]__   
[10:19:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
[10:19:17]  _/ // (7 7// /  / / / _/   
[10:19:17] /___/\___/_/|_/___/ /_/ /___/  
[10:19:17] 
[10:19:17] ver. 2.1.2#20170711-sha1:2a2c8030
[10:19:17] 2017 Copyright(C) Apache Software Foundation
[10:19:17] 
[10:19:17] Ignite documentation: http://ignite.apache.org
[10:19:17] 
[10:19:17] Quiet mode.
[10:19:17]   ^-- Logging to file 
'/Users/gridgain/Downloads/gridgain-enterprise-fabric-8.1.2/work/log/ignite-9ef688f8.log'
[10:19:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[10:19:17] 
[10:19:17] OS: Mac OS X 10.10.5 x86_64
[10:19:17] VM information: Java(TM) SE Runtime Environment 1.8.0_45-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.45-b02
[10:19:17] Initial heap size is 256MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[10:19:17] Configured plugins:
[10:19:17]   ^-- GridGain 8.1.2#20170711-sha1:ff30520a
[10:19:17]   ^-- 2017 Copyright(C) GridGain Systems
[10:19:17] 
[10:19:17] Message queue limit is set to 0 which may lead to potential OOMEs 
when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
message queues growth on sender and receiver sides.
[10:19:17] Security status [authentication=off, tls/ssl=off]
[10:19:18] Rolling updates are disabled. GridGain version update will require 
full cluster restart. Consider changing 
'GridGainConfiguration.rollingUpdatesEnabled' configuration property.
[2017-07-12 10:19:20,162][ERROR][main][GridEntLicenseProcessor] License 
violation detected:
  ^-- Maximum number of nodes (3/2) is exceeded.
[2017-07-12 10:19:20,162][ERROR][main][GridEntLicenseProcessor] Contact 
sa...@gridgain.com for further assistance. Make sure to include your license 
ID: 9D50E008-472D-430F-8B2D-CFB8A3894C0D
[2017-07-12 10:19:20,163][ERROR][main][GridEntLicenseProcessor] License 
grace/burst period - left 1 hour.
[10:19:20] Performance suggestions for grid  (fix if possible)
[10:19:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[10:19:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[10:19:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[10:19:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
JVM options)
[10:19:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
[10:19:20]   ^-- Disable processing of calls to System.gc() (add 
'-XX:+DisableExplicitGC' to JVM options)
[10:19:20] Refer to this page for more performance suggestions: 
https://apacheignite.readme.io/docs/jvm-and-system-tuning
[10:19:20] 
[10:19:20] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[10:19:20] 
[10:19:20] Ignite node started OK (id=9ef688f8)
[10:19:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=8, heap=5.6GB]

>>> Cache query DDL example started.

>>> Created database objects.

>>> Populated data.
{noformat}

On remote nodes;
{noformat}
SEVERE: Failed to read message [msg=GridIoMessage [plc=0, topic=null, 
topicOrd=-1, ordered=false, timeout=0, skipOnTimeout=false, msg=null], 
buf=java.nio.DirectByteBuffer[pos=4 lim=10001 cap=32768], 
reader=DirectMessageReader [state=DirectMessageState [pos=0, stack=[StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140343292566528, arrOff=-1, 
tmpArrOff=0, tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, 
arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, 
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], 
state=0], null, null, null, null, null, null, null, null, null]], 
lastRead=false], ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker 
[super=AbstractNioClientWorker [idx=2, bytesRcvd=117764, bytesSent=5240, 
bytesRcvd0=20086, bytesSent0=56, select=true, super=GridWorker 
[name=grid-nio-worker-tcp-comm-2, igniteInstanceName=null, finished=false, 
hashCode=158461243, interrupted=false, 
runner=grid-nio-worker-tcp-comm-2-#19%null%]]], 
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
readBuf=java.nio.DirectByteBuffer[pos=4 lim=10001 cap=32768], 
inRecovery=GridNioRecoveryDescriptor [acked=10, resendCnt=0, rcvCnt=10, 
sentCnt=10, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode 
[id=9e

[jira] [Created] (IGNITE-5538) NPE (PersistentStoreExample)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5538:


 Summary: NPE (PersistentStoreExample)
 Key: IGNITE-5538
 URL: https://issues.apache.org/jira/browse/IGNITE-5538
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Ilya Suntsov
 Fix For: 2.1


Steps to reproduce:
1. Start *PersistentStoreExampleNodeStartup*
2. Start *PersistentStoreExample* (UPLOAD=true)
Result:
1. Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
2. Started preloading
3. On ExampleNode got exception:
{noformat}
[2017-06-19 13:11:28,545][WARN 
][grid-nio-worker-tcp-comm-3-#20%null%][TcpCommunicationSpi] Failed to process 
selector key (will close): GridSelectorNioSessionImpl 
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=3, 
bytesRcvd=2052, bytesSent=252, bytesRcvd0=228, bytesSent0=28, select=true, 
super=GridWorker [name=grid-nio-worker-tcp-comm-3, igniteInstanceName=null, 
finished=false, hashCode=1279096191, interrupted=false, 
runner=grid-nio-worker-tcp-comm-3-#20%null%]]], 
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
readBuf=java.nio.DirectByteBuffer[pos=4 lim=186 cap=32768], 
inRecovery=GridNioRecoveryDescriptor [acked=103, resendCnt=0, rcvCnt=104, 
sentCnt=103, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
[id=be66eae2-3986-4772-b02b-bf2813370a15, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
172.25.4.115, 172.25.4.116, 2001:db8:85a3:0:0:8a2e:370:7334], 
sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.25.4.115:0, /172.25.4.116:0, 
/2001:db8:85a3:0:0:8a2e:370:7334:0], discPort=0, order=2, intOrder=2, 
lastExchangeTime=1497867042970, loc=false, ver=2.1.1#20170618-sha1:09ce29e0, 
isClient=true], connected=true, connectCnt=1, queueLimit=4096, reserveCnt=35, 
pairedConnections=false], outRecovery=GridNioRecoveryDescriptor [acked=103, 
resendCnt=0, rcvCnt=104, sentCnt=103, reserved=true, lastAck=96, 
nodeLeft=false, node=TcpDiscoveryNode [id=be66eae2-3986-4772-b02b-bf2813370a15, 
addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 172.25.4.115, 172.25.4.116, 
2001:db8:85a3:0:0:8a2e:370:7334], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
/172.25.4.115:0, /172.25.4.116:0, /2001:db8:85a3:0:0:8a2e:370:7334:0], 
discPort=0, order=2, intOrder=2, lastExchangeTime=1497867042970, loc=false, 
ver=2.1.1#20170618-sha1:09ce29e0, isClient=true], connected=true, connectCnt=1, 
queueLimit=4096, reserveCnt=35, pairedConnections=false], 
super=GridNioSessionImpl [locAddr=/0:0:0:0:0:0:0:1:47100, 
rmtAddr=/0:0:0:0:0:0:0:1:60813, createTime=1497867087529, closeTime=0, 
bytesSent=28, bytesRcvd=228, bytesSent0=28, bytesRcvd0=228, 
sndSchedTime=1497867087529, lastSndTime=1497867087529, 
lastRcvTime=1497867087541, readsPaused=false, 
filterChain=FilterChain[filters=[GridNioCodecFilter 
[parser=o.a.i.i.util.nio.GridDirectParser@7a94a8f6, directMode=true], 
GridConnectionBytesVerifyFilter], accepted=true]]
[2017-06-19 
13:11:28,545][ERROR][grid-nio-worker-tcp-comm-3-#20%null%][TcpCommunicationSpi] 
Closing NIO session because of unhandled exception.
class org.apache.ignite.internal.util.nio.GridNioException: null
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
org.apache.ignite.internal.managers.communication.GridIoMessageFactory.create(GridIoMessageFactory.java:879)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$9.create(TcpCommunicationSpi.java:2134)
at 
org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1154)
at 
org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
at 
org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:261)
at 
org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
at 
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109

[jira] [Created] (IGNITE-5537) bin/control.sh add validation of input parameters

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5537:


 Summary: bin/control.sh add validation of input parameters
 Key: IGNITE-5537
 URL: https://issues.apache.org/jira/browse/IGNITE-5537
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Ilya Suntsov
 Fix For: 2.1


I've tried to run *bin/control.sh* without parameters, with parameter 
*help*,*-h*. Utility in these cases tried to connect to grid but should just 
prints help. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5098) Missed ignite-rocketmq/licenses/ignite-2.0.txt

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5098:


 Summary: Missed ignite-rocketmq/licenses/ignite-2.0.txt
 Key: IGNITE-5098
 URL: https://issues.apache.org/jira/browse/IGNITE-5098
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


Need to add $IGNITE_HOME/libs/optional/ignite-rocketmq/licenses/ignite-2.0.txt



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

[jira] [Created] (IGNITE-5096) Too many files with unapproved license

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5096:


 Summary: Too many files with unapproved license
 Key: IGNITE-5096
 URL: https://issues.apache.org/jira/browse/IGNITE-5096
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov
Priority: Critical


Steps to reproduce:
mvn clean validate -DskipTests=true -P check-licenses

Result:

{noformat}
[INFO] apache-ignite .. FAILURE [  1.429 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 54.186 s
[INFO] Finished at: 2017-04-27T09:36:47+03:00
[INFO] Final Memory: 62M/479M
[INFO] 
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check 
(default) on project apache-ignite: Too many files with unapproved license: 3 
See RAT report
{noformat}

RAT report attached to this ticket.



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

[jira] [Created] (IGNITE-5022) Duplicates of JVM OPTS [yardstick]

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-5022:


 Summary: Duplicates of JVM OPTS [yardstick]
 Key: IGNITE-5022
 URL: https://issues.apache.org/jira/browse/IGNITE-5022
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.9
Reporter: Ilya Suntsov
 Fix For: 2.1


I've set in properties file these jvm options:
{noformat}
JVM_OPTS=${JVM_OPTS}" \
-Xms6g \
-Xmx6g \
-Xloggc:./gc${now0}.log \
-XX:+PrintGCDetails \
-verbose:gc \
-XX:+UseParNewGC \
-XX:+UseConcMarkSweepGC \
{noformat}

But in nodes logs I see the following:
{noformat}
-Xms2g, -Xmx2g, -Djava.net.preferIPv4Stack=true, 
-DIGNITE_QUIET=false,
 -Xms6g,
 -Xmx6g,
 -Xloggc:./gc205724.log,
 -XX:+PrintGCDetails,
 -verbose:gc,
 -XX:+UseParNewGC,
 -XX:+UseConcMarkSweepGC,
 
-Xloggc:/home/ubuntu/date-1804-205649-s-4-c-8-ver-2.0.0-SNAPSHOT-3565e4ee/yardstick/bin/../output/logs-20170418-205720/logs_drivers/gc-205724-driver-id0-172.31.46.6-2.0.0-SNAPSHOT-3565e4ee-atomic-put-1-backup.log,
 -Dyardstick.driver0, 
-Xloggc:/home/ubuntu/date-1804-205649-s-4-c-8-ver-2.0.0-SNAPSHOT-3565e4ee/yardstick/bin/../output/logs-20170418-205720/logs_drivers/gc-205724-driver-id1-172.31.37.52-2.0.0-SNAPSHOT-3565e4ee-atomic-put-1-backup.log,
 -Dyardstick.driver1,
 
-Xloggc:/home/ubuntu/date-1804-205649-s-4-c-8-ver-2.0.0-SNAPSHOT-3565e4ee/yardstick/bin/../output/logs-20170418-205720/logs_drivers/gc-205724-driver-id2-172.31.35.222-2.0.0-SNAPSHOT-3565e4ee-atomic-put-1-backup.log,
 -Dyardstick.driver2
{noformat}

The problem is duplicates of logs files in the end. It was log of yardstick 
driver with id equals 2 but here we can see also info about gc log driver with 
id 0 and id 1.
Also we need to add if condition in bootstrap script where we set 
{noformat}-Xms2g, -Xmx2g, -Djava.net.preferIPv4Stack=true,  {noformat}



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

[jira] [Created] (IGNITE-4913) Update yardstick properties files

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4913:


 Summary: Update yardstick properties files
 Key: IGNITE-4913
 URL: https://issues.apache.org/jira/browse/IGNITE-4913
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.9
Reporter: Ilya Suntsov
 Fix For: 2.0


Need to add *ver* parameter in all properties files from yardstick/config.
Example:
{noformat}
#Ignite version
ver="RELEASE-"

CONFIGS="\
-cfg ${SCRIPT_DIR}/../config/ignite-multicast-config.xml -nn ${nodesNum} -b 
${b} -w ${w} -d ${d} -t ${t} -sm ${sm} -dn IgnitePutBenchmark -sn IgniteNode 
-ds ${ver}atomic-put-${b}-backup,\
...
{noformat}



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

[jira] [Created] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4787:


 Summary: Performance drop sql-merge-all 1.9 vs 1.8
 Key: IGNITE-4787
 URL: https://issues.apache.org/jira/browse/IGNITE-4787
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.9
 Environment: AWS EC2 Instances (r4.2xlarge)
1 client/ 4 servers
primary sync
64 threads
1 backup

Reporter: Ilya Suntsov
Priority: Critical
 Fix For: 2.0


We have performance drop on sql-merge-all benchmark in 1.9 against 1.8.
Below are numbers of 5 runs of this benchmark:
1.9..1.8..delta
4911.89...4400.63...-11.62%
4922.16...4414.56...-11.50%
4899.16...4397.73...-11.40%
4875.75...4389.8.-11.07%
4906.68...4418.05...-11.06%

Logs and configs are in attachment.



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

[jira] [Created] (IGNITE-4743) Set AUTO_COPY to false when it wasn't define in properties file

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4743:


 Summary: Set AUTO_COPY to false when it wasn't define in 
properties file
 Key: IGNITE-4743
 URL: https://issues.apache.org/jira/browse/IGNITE-4743
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


In case when in properties file there isn't variable AUTO_COPY we automatically 
set it to true. It's wrong. 
We should add condition if AUTO_COPY doesn't exist in property file then set it 
to false.



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

[jira] [Created] (IGNITE-4512) Doesnt work sql-delete benchmark

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4512:


 Summary: Doesnt work sql-delete benchmark
 Key: IGNITE-4512
 URL: https://issues.apache.org/jira/browse/IGNITE-4512
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
 Environment: Benchmark class: IgniteSqlDeleteBenchmark
Yardsitck configuration: 1 client, 4 servers, 64 threads, 1 backup, primary sync
Reporter: Ilya Suntsov
 Fix For: 2.0


I got the following exception when tried to run sql-delete benchmark:
{noformat}
<13:18:49> DELETE setUp: have successfully put 0 items
<13:18:50> DELETE setUp: have successfully put 10 
items
<13:18:51> DELETE setUp: have successfully put 20 
items
<13:18:52> Probe writer is not configured (using default CSV 
writer)
<13:18:52> ThroughputLatencyProbe is started.
<13:18:52> DStatProbe is started. Command: 'dstat -m --all 
--noheaders --noupdate 1'
<13:18:52> PercentileProbe is started.
[13:18:53,373][INFO ][grid-timeout-worker-#23%null%][IgniteKernal].
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=84f60fbc, name=null, uptime=00:00:05:000]
^-- H/N/C [hosts=5, nodes=5, CPUs=80]
^-- CPU [cur=0%, avg=0%, GC=0%]
^-- Heap [used=56MB, free=97.26%, comm=2047MB]
^-- Non heap [used=56MB, free=-1%, comm=57MB]
^-- Public thread pool [active=0, idle=6, qSize=0]
^-- System thread pool [active=0, idle=16, qSize=0]
^-- Outbound messages queue [size=7]
Finishing main test [ts=1483006734702, date=Thu Dec 29 13:18:54 MSK 2016]
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
java.util.NoSuchElementException
<-->at java.util.AbstractQueue.remove(AbstractQueue.java:117)
<-->at 
org.apache.ignite.yardstick.cache.dml.IgniteSqlDeleteBenchmark.test(IgniteSqlDeleteBenchmark.java:73)
<-->at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
<-->at java.lang.Thread.run(Thread.java:745)
[13:18:54,740][INFO ][Thread-72][GridCacheProcesso
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Ilya Suntsov]

Denis,

I think we can remove all configs except:

benchmark-multicast.properties

benchmark.properties

ignite-base-config.xml

ignite-localhost-config.xml

ignite-multicast-config.xml

2016-12-28 2:49 GMT+03:00 Denis Magda <dma...@apache.org>:

> I would have only those configs that are useful. Ilya Suntsov, basing on
> your experience, please suggest which configs makes sense to include into
> every Ignite release.
>
> Oleg, also please note that community decided to include not only the
> benchmarking binaries but the sources as well into every Apache Ignite
> release. I’ve update the ticket before. Hope you followed the discussion ;)
> https://issues.apache.org/jira/browse/IGNITE-4212?
> focusedCommentId=15765151=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-15765151
>
> —
> Denis
>
> > On Dec 27, 2016, at 5:35 AM, Oleg Ostanin <oosta...@gridgain.com> wrote:
> >
> > I mean removing those configs from binary assembly, not from repository.
> >
> > On Tue, Dec 27, 2016 at 4:28 PM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
> >
> >> Hello Igniters.
> >> I think it would be better to remove some configuration files from
> >> benchmarks/config:
> >>
> >> ignite-base-load-config.xml
> >> ignite-cache-load-config.xml
> >> ignite-failover-base-config.xml
> >> ignite-failover-localhost-config.xml
> >> benchmark-cache-load.properties
> >> benchmark-cache-load-win.properties
> >> benchmark-failover.properties
> >>
> >> because those configs do not relate to any of performance tests.
> >>
> >> On Tue, Dec 20, 2016 at 11:24 PM, Denis Magda <dma...@apache.org>
> wrote:
> >>
> >>> Summarized the discussion updating the ticket
> >>> https://issues.apache.org/jira/browse/IGNITE-4212# <
> >>> https://issues.apache.org/jira/browse/IGNITE-4212#>
> >>>
> >>> —
> >>> Denis
> >>>
> >>>> On Dec 19, 2016, at 12:26 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> >>> wrote:
> >>>>
> >>>> Sergey,
> >>>>
> >>>> I am not sure I like "extras". I am voting for "benchmarks" folder
> right
> >>>> under the root folder.
> >>>>
> >>>> D.
> >>>>
> >>>> On Mon, Dec 19, 2016 at 12:07 PM, Sergey Kozlov <skoz...@gridgain.com
> >
> >>>> wrote:
> >>>>
> >>>>> Formatting has cut lines:
> >>>>>
> >>>>> — apache_ignite_root_folder
> >>>>> — bin
> >>>>> — examples
> >>>>> — extras
> >>>>>  — benchmarks
> >>>>>— bin
> >>>>>— src (benchmarks sources with pom.xml)
> >>>>>— config
> >>>>>— libs (compiled benchmarks)
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Mon, Dec 19, 2016 at 11:04 PM, Sergey Kozlov <
> skoz...@gridgain.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Denis,
> >>>>>>
> >>>>>> Mostly yes. But I look ahead and think that we may include more
> >>> things in
> >>>>>> future than yardstick only. It's why I suggest something like that:
> >>>>>> — apache_ignite_root_folder
> >>>>>>   — bin
> >>>>>>   — examples
> >>>>>>   — extras
> >>>>>>   — benchmarks
> >>>>>>   — bin
> >>>>>>   — src (benchmarks sources with pom.xml)
> >>>>>>   — config
> >>>>>>   — libs (compiled benchmarks)
> >>>>>>
> >>>>>> On Mon, Dec 19, 2016 at 10:15 PM, Denis Magda <dma...@apache.org>
> >>> wrote:
> >>>>>>
> >>>>>>> Well, if to refer to Dmitriy suggestion we can have the following
> >>>>>>> structure
> >>>>>>>
> >>>>>>> — apache_ignite_root_folder
> >>>>>>>   — examples
> >>>>>>>   — bin
> >>>>>>>   — benchmarks
> >>>>>>>   — bin
> >>>>>>>   — src (benchmarks sources with pom.xml)
> >>>>>>>   — config
> >>

[jira] [Created] (IGNITE-4373) Performance drop tx-putAll 1.8.0 vs 1.7.0

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4373:


 Summary: Performance drop tx-putAll 1.8.0 vs 1.7.0
 Key: IGNITE-4373
 URL: https://issues.apache.org/jira/browse/IGNITE-4373
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
 Environment: CentOS 
jdk 1.7
Reporter: Ilya Suntsov
Priority: Critical
 Fix For: 1.9


I've run benchmarks AI 1.8.0 vs 1.7.0 and got the following results for 
tx-putAll:
{noformat}
1,608.23 1,767.34 -9.89%
1521.18  1757.26 -15.52%
1531.49 1740.15 -13.62%
{noformat}

Configuration:
 - 1 client 4 servers
 - 64 threads
- 1 backup
 - primary sync



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4282) Javadoc broken

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4282:


 Summary: Javadoc broken 
 Key: IGNITE-4282
 URL: https://issues.apache.org/jira/browse/IGNITE-4282
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.8
Reporter: Ilya Suntsov
 Fix For: 1.8


Broken javadoc here:
{noformat}incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/rest/handlers/redis/server/GridRedisDbSizeCommandHandler.java{noformat}

Warning text:
{noformat}Tag @inheritDoc cannot be used in constructor documentation.  It can 
only be used in the following types of documentation: method, inline 
text.{noformat}

Log you can find in attachment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3814) Unstable results of compute benchmarks

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3814:


 Summary: Unstable results of compute benchmarks
 Key: IGNITE-3814
 URL: https://issues.apache.org/jira/browse/IGNITE-3814
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
 Environment: Ubuntu 14.04
jdk 1.7, jdk 1.8
Reporter: Ilya Suntsov


I've run the following compute benchmarks:
* exec-compute
* run-compute
* broad-compute
* apply-compute
and got huge difference between the best and worst results e.g. for 
exec-compute we have the following numbers:
1   1222.38
2   1220.63
3   1044.53
4   1342.39
5   1393.57
5   1064.66

delta between 3-rd and 4-th runs is 28%.
I think we should re-work these benchmarks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3387) NPE deploy ignite with mesos

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3387:


 Summary: NPE deploy ignite with mesos
 Key: IGNITE-3387
 URL: https://issues.apache.org/jira/browse/IGNITE-3387
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Ilya Suntsov
 Fix For: 1.7


I tried to use marathon to deploy ignite with mesos:
{noformat}
curl -X POST -H "Content-type: application/json" --data-binary @marathon.json 
http://192.168.2.106:8080/v2/apps/
{noformat}

where marathon.json contains:
{noformat}
  "id": "ignition",
  "instances": 1,
  "cpus": 1,
  "mem": 512,
  "ports": [0],
  "uris": [
"https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
  ],
  "env": {
"IGNITE_NODE_COUNT": "4",
"MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
"IGNITE_RUN_CPU_PER_NODE": "2",
"IGNITE_MEMORY_PER_NODE": "2048",
"IGNITE_VERSION":"6.6.6"
  },
  "cmd": "java -jar ignite-mesos-1.6.0.jar"
{noformat} 

and got the following exception caused by wrong ignite version from 
marathon.json:
{noformat}
Exception in thread "Thread-11" java.lang.NullPointerException
at 
org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
at 
org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
at 
org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)

{noformat}

I think we should return another exception/error to be clear what happened.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3176:


 Summary: Need to create gc log for each client separately [ 
yardstick-ignite ]
 Key: IGNITE-3176
 URL: https://issues.apache.org/jira/browse/IGNITE-3176
 Project: Ignite
  Issue Type: Bug
  Components: clients, general
Affects Versions: 1.6
Reporter: Ilya Suntsov
Priority: Critical
 Fix For: 1.7


In case when started more than one client/server on one host yardstick re-write 
GC logs.

GC options contain in *.properties files:
{noformat}
now0=`date +'%H%M%S'`
# JVM options.
JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
# Uncomment to enable concurrent garbage collection (GC) if you encounter long 
GC pauses.
JVM_OPTS=${JVM_OPTS}" \
-Xloggc:./gc${now0}.log \
-XX:+PrintGCDetails \
-verbose:gc \
-XX:+UseParNewGC \
-XX:+UseConcMarkSweepGC \
-XX:+UseTLAB \
-XX:NewSize=128m \
-XX:MaxNewSize=128m \
-XX:MaxTenuringThreshold=0 \
-XX:SurvivorRatio=1024 \
-XX:+UseCMSInitiatingOccupancyOnly \
-XX:CMSInitiatingOccupancyFraction=60 \
{noformat}

As you can see here will be created 1 log file and if you start another 
driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3106) Yardstick can't parse /config/queries.txt with license header

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3106:


 Summary: Yardstick can't parse /config/queries.txt with license 
header
 Key: IGNITE-3106
 URL: https://issues.apache.org/jira/browse/IGNITE-3106
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.6
Reporter: Ilya Suntsov
Priority: Blocker
 Fix For: 1.6


File yardstick/config/queries.txt contains queries that used for load tests. 
Yardstick can't parse this file with this license header:
{noformat}
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#  http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
{noformat}

Yardstick reads line in upper case and tried to execute it as query:
{noformat}
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
javax.cache.CacheException: class org.apache.ignite.IgniteException: Failed to 
parse query: # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:674)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doSqlQuery(IgniteCacheRandomOperationBenchmark.java:858)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:553)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:495)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:158)
<-->at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
<-->at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Failed to parse query: # 
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
<-->at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:665)
<-->... 6 more
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3103) No description in javadoc (kafka module)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3103:


 Summary: No description in javadoc (kafka module)
 Key: IGNITE-3103
 URL: https://issues.apache.org/jira/browse/IGNITE-3103
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.6
Reporter: Ilya Suntsov
Priority: Minor
 Fix For: 1.6


No description in javadoc for classes:
* org.apache.ignite.stream.kafka.connect
 * org.apache.ignite.stream.kafka.connect.serialization



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3070) Failed to fetch data from node at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3070:


 Summary:  Failed to fetch data from node at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor
 Key: IGNITE-3070
 URL: https://issues.apache.org/jira/browse/IGNITE-3070
 Project: Ignite
  Issue Type: Bug
  Components: cache, general
 Environment: 1 host: Cent OS 5, jdk 1.7
1 yardstick driver, 3 yardstick servers
Reporter: Ilya Suntsov
Priority: Critical
 Attachments: logs-bug-load.zip

I ran a load test with the following parameters:
 - 1 backup
 - key range equal 1 000 000
 - warmup 60 sec
 - duration 300 sec
 - preloading amount  500 000
 - 64 threads
 - primary sync mode 
Additional parameters:
{noformat}
--allow-operation PUT --allow-operation PUT_ALL --allow-operation GET 
--allow-operation GET_ALL --allow-operation INVOKE --allow-operation INVOKE_ALL 
--allow-operation REMOVE \
--allow-operation REMOVE_ALL --allow-operation PUT_IF_ABSENT --allow-operation 
REPLACE --allow-operation SCAN_QUERY --allow-operation SQL_QUERY 
--allow-operation CONTINUOUS_QUERY {noformat}

Queries file:
{noformat}
SELECT Person.firstName  FROM "query".Person, "orgCache".Organization WHERE 
Person.orgId = Organization.id AND lower(Organization.name) = 
lower('Organization 55')
SELECT Organization.name  FROM "orgCache".Organization WHERE 
lower(Organization.name) LIKE lower('%55%')
{noformat}

Another parameters and caches configurations you can find in attachment.

I got the following exception on yardstick driver:
{noformat}
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
javax.cache.CacheException: Failed to fetch data from node: 
25328521-72be-4d42-8ba1-98a408558900
<-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$3.fetchNextPage(GridReduceQueryExecutor.java:290)
<-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex.fetchNextPage(GridMergeIndex.java:229)
<-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndexUnsorted$1.hasNext(GridMergeIndexUnsorted.java:106)
<-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$IteratorCursor.next(GridMergeIndex.java:351)
<-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMergeIndex$FetchingCursor.next(GridMergeIndex.java:382)
<-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:614)
<-->at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:956)
<-->at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doSqlQuery(IgniteCacheRandomOperationBenchmark.java:835)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:553)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:496)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:152)
<-->at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
<-->at java.lang.Thread.run(Thread.java:745)
<-->Suppressed: javax.cache.CacheException: Failed to execute map query on 
the node: b0e43304-0a86-43cf-b14c-20a3753a85a6, class 
javax.cache.CacheException:No query result found for request: 
GridQueryNextPageRequest [qryReqId=108, qry=0, pageSize=1024]
<--><-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:257)
<--><-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:247)
<--><-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:228)
<--><-->at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:176)
<--><-->at 
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2039)
<--><-->at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
<--><-->at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
<--><--

[jira] [Created] (IGNITE-2932) IgniteFutureTimeoutException during the run of load test (cache-tx-invoke)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2932:


 Summary: IgniteFutureTimeoutException during the run of load test 
(cache-tx-invoke)
 Key: IGNITE-2932
 URL: https://issues.apache.org/jira/browse/IGNITE-2932
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
 Environment: 
Environment:
vCPU 8
RAM 15GiB
OS Ubuntu 14.04
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Yardstick configuration:
client mode (15 servers, 5 clients)
PRIMARY SYNC
128 threads
1 backup
Reporter: Ilya Suntsov
Assignee: Artem Shutak
Priority: Critical
 Fix For: 1.6


I got the following exception during the run of load test with 2 backups (+ sql 
caches and sql benchmarks) :
{noformat}
<16:39:52> Got exception: class 
org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached before 
computation completed.
<16:39:52> Full thread dump of the current node 
below.class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was 
reached before computation completed.
at 
org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
at 
org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
at 
org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
at java.lang.Thread.run(Thread.java:745)
Caused by: class 
org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was 
reached before computation completed.
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
... 2 more

[16:39:52] (wrn) No deadlocked threads detected.
Finishing main test [ts=1459442392910, date=Thu Mar 31 16:39:52 UTC 2016]
{noformat}

Logs and configs you can find in attachment.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2896) IgniteFutureTimeoutException during load test (yardstick)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2896:


 Summary: IgniteFutureTimeoutException during load test (yardstick)
 Key: IGNITE-2896
 URL: https://issues.apache.org/jira/browse/IGNITE-2896
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.6
 Environment: Environment:
 - vCPU 8
 - RAM 15GiB
 - OS Ubuntu 14.04
 - Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Yardstick configuration:
 - client mode (15 servers, 5 clients)
 - PRIMARY SYNC
 - 128 threads
 - 1 backup
Reporter: Ilya Suntsov
Assignee: Artem Shutak
Priority: Critical
 Fix For: 1.6


I got the following exception during the run of load test with 1 baskup (+ sql 
caches and sql benchmarks) :
{noformat}
 Got exception: class 
org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached before 
computation completed.
class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached 
before computation completed.
at 
org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
at 
org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
at 
org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
at java.lang.Thread.run(Thread.java:745)
Caused by: class 
org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was 
reached before computation completed.
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
at 
org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
... 2 more
{noformat}

Logs and configs you can find in attachment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2867) IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2867:


 Summary: IgniteConsistencyException during running load test 
(cache-atomic-invoke-retry-validator)
 Key: IGNITE-2867
 URL: https://issues.apache.org/jira/browse/IGNITE-2867
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.6
 Environment: Yardstick driver's host: Ubuntu 14.04.3 LTS
Yardstick server's hosts: Ubuntu 14.04.3 LTS and CentOS release 6.7 (Final)

Yardstick configuration: 2 clients, 3 servers, PRIMARY_SYNC, 1 and 2 backups
Reporter: Ilya Suntsov
Assignee: Artem Shutak
Priority: Critical
 Fix For: 1.6
 Attachments: logs_configs_2103.zip

I've add one more client and run load test with 2 clients and 3 servers (all on 
different hosts).
Test runs for ~ 3 min and stops with exception:
{noformat}
 Got exception: 
org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
and local map are in inconsistent state.
{noformat}

Logs and configs you can find in attachment. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2638) "Connection to Ignite Web Agent is not established" form not in focus

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2638:


 Summary: "Connection to Ignite Web Agent is not established" form 
not in focus
 Key: IGNITE-2638
 URL: https://issues.apache.org/jira/browse/IGNITE-2638
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: 1.6
 Environment: OS X 10.10.5
Safari 9.0.2 (10601.3.9)
Reporter: Ilya Suntsov
Assignee: Alexey Kuznetsov
Priority: Minor
 Fix For: 1.6


Steps for reproduce:
1. Stop  ignite-web-agent 
2. Go to https://console.gridgain.com/sql/demo
3. Click on 'Show security token'
Result:
Text in form became blurry. Please look in attachment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2327) No error message when visorui connects to sequre grid without permissions

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2327:


 Summary: No error message when visorui connects to sequre grid 
without permissions
 Key: IGNITE-2327
 URL: https://issues.apache.org/jira/browse/IGNITE-2327
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
 Environment: jdk 1.7
ubuntu 14.04
Reporter: Ilya Suntsov
Assignee: Alexey Kuznetsov
 Fix For: 1.5


Steps for reproduce:
1. Start 
examples/src/main/java/org/gridgain/examples/auth/GridAclExampleServerNodeStartup.java
 with server-auth.xml (in attachment)
2. Start  visorui with  client-config.xml (in attachment)
Result:
Client haven't permission to use visor for grid monitoring (ADMIN_VIEW, 
ADMIN_QUERY, ADMIN_CACHE) but visorui doesn't show message about it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Mandatory requirement to run ExampleNodeStartup only for a several examples

[Ilya Suntsov]

Guys,
I've re-checked these examples. Most of the benchmarks corresponding to the
description that was provided by Yakov above but the following examples
don't work with remote nodes started with server classpath :

   - org.apache.ignite.examples.datagrid.CacheQueryExample
   - org.apache.ignite.examples.streaming.StreamVisitorExample
   - org.apache.ignite.examples.java8.streaming.StreamTransformerExample
   - org.apache.ignite.examples.java8.streaming.StreamVisitorExample


2015-12-14 17:53 GMT+03:00 Yakov Zhdanov <yzhda...@apache.org>:

> Guys,
>
> There is currently a limitation - we cannot effectively deploy class
> definitions over discovery protocol. This is possible to fix, but needs
> some more investigation.
>
> As far as current situation with examples, I think that the following
> examples should work with remote nodes started with server classpath
> (yes/no). Sergey, can you please check if my vision is correct and let us
> know:
>
> Java
> Y: org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample
> Y: org.apache.ignite.examples.datagrid.starschema.CacheStarSchemaExample
> N: org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample
> N: org.apache.ignite.examples.datagrid.store.dummy.CacheDummyStoreExample
> N: org.apache.ignite.examples.datagrid.store.jdbc.CacheJdbcStoreExample
> N: org.apache.ignite.examples.datagrid.store.spring.CacheSpringStoreExample
> Y: org.apache.ignite.examples.datagrid.CacheQueryExample
> N: org.apache.ignite.examples.servicegrid.ServicesExample - service cannot
> be peer deployed now
> Y: org.apache.ignite.examples.streaming.StreamTransformerExample
> Y: org.apache.ignite.examples.streaming.StreamVisitorExample
> Y: org.apache.ignite.examples.streaming.org.apache.ignite.
> examples.streaming.wordcount.QueryWords
> Y: org.apache.ignite.examples.streaming.org.apache.ignite.
> examples.streaming.wordcount.StreamWords
>
> Scala
> Y: org.apache.ignite.scalar.examples.ScalarCacheQueryExample
> Y: org.apache.ignite.scalar.examples.ScalarSnowflakeSchemaExample
>
> Java8
> Y: org.apache.ignite.examples.java8.streaming.StreamTransformerExample
> Y: org.apache.ignite.examples.java8.streaming.StreamVisitorExample
>
> LGPL:
> N: org.apache.ignite.examples.datagrid.store.hibernate.
> CacheHibernateStoreExample
> --Yakov
>
> 2015-12-12 5:23 GMT+03:00 Alexey Kuznetsov <akuznet...@gridgain.com>:
>
> > Dmitriy,
> >
> > As far as I know P2P works mainly for Compute
> > See: https://apacheignite.readme.io/v1.5/docs/zero-deployment
> >
> > On Sat, Dec 12, 2015 at 4:47 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Why are we not allowing to deploy factory classes over P2P deployment?
> > >
> > > On Fri, Dec 11, 2015 at 7:29 AM, Alexey Kuznetsov <
> > akuznet...@gridgain.com
> > > >
> > > wrote:
> > >
> > > > I can confirm examples developed/changed by me.
> > > >
> > > > >>
> org.apache.ignite.examples.datagrid.store.auto.CacheAutoStoreExample
> > > > DO NOT ALLOW to start remote nodes via ignite.sh out of the box, but
> if
> > > > user put example cache store factory class into \libs folder example
> > will
> > > > run.
> > > >
> > > > >>
> > > >
> > > >
> > >
> >
> org.apache.ignite.examples.binary.datagrid.store.auto.CacheBinaryAutoStoreExample
> > > > This example ALLOW to start remote nodes via ignite.sh.
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>



-- 
Ilya Suntsov

[jira] [Created] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2175:


 Summary: Not valid exceptions in case when example can't works 
with remote node started with server classpath (Java 7)
 Key: IGNITE-2175
 URL: https://issues.apache.org/jira/browse/IGNITE-2175
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
 Environment: jdk 1.7
OS X 10.10.2
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


Steps for reproduce:
1. Start one node form IDEA and one more from terminal
2. Run StreamVisitorExample.
Got exception:
{noformat}
16:41:23,807][SEVERE][pub-#13%null%][DataStreamProcessor] Failed to finish 
update job.
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1634)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:870)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:83)
at 
org.apache.ignite.examples.streaming.StreamVisitorExample$1.apply(StreamVisitorExample.java:77)
at org.apache.ignite.stream.StreamVisitor.receive(StreamVisitor.java:38)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:298)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4522)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1378)
at 
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:299)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:863)
... 13 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.streaming.StreamVisitorExample$Instrument
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:274)
at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1443)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:537)
at 
org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:116)
at 
org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinary(CacheObjectContext.java:280

[jira] [Created] (IGNITE-2158) Null values in examples output

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2158:


 Summary: Null values in examples output
 Key: IGNITE-2158
 URL: https://issues.apache.org/jira/browse/IGNITE-2158
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
 Environment: OS X 10.10.2
jdk 1.7
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
 Fix For: 1.5


In output of the following examples there are fields that have 'null' or zero 
values (salary, orgId, resume ):
1.CacheDummyStoreExample
{noformat}
[16:48:47] Ignite node started OK (id=64a079ad)
[16:48:47] Topology snapshot [ver=9, servers=3, clients=0, CPUs=8, heap=8.0GB]

>>> Cache store example started.
>>> Store loadCache for entry count: 10
>>> Loaded 10 keys with backups in 971ms.
Read value: null
Overwrote old value: null
Read value: Person [id=7754401276845136764, orgId=null, lastName=Newton, 
firstName=Isaac, salary=0.0, resume=null]
>>> Store put [key=7754401276845136764, val=Person [id=7754401276845136764, 
>>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null], 
>>> xid=ab2b0c0a151-03aba62c--0009--0151a0c0307a]
Read value after commit: Person [id=7754401276845136764, orgId=null, 
lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
[16:48:48] Ignite node stopped OK [uptime=00:00:01:38]
{noformat}

2. CacheJdbcStoreExample
{noformat}
[16:49:36] Ignite node started OK (id=f662db78)
[16:49:36] Topology snapshot [ver=11, servers=3, clients=0, CPUs=8, heap=8.0GB]

>>> Cache store example started.
>>> Loaded 0 values into cache.
>>> Loaded 1 keys with backups in 26ms.
>>> Store load [key=8980561285181288706]
Read value: null
Overwrote old value: null
Read value: Person [id=8980561285181288706, orgId=null, lastName=Newton, 
firstName=Isaac, salary=0.0, resume=null]
>>> Store write [key=8980561285181288706, val=Person [id=8980561285181288706, 
>>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null]]
Read value after commit: Person [id=8980561285181288706, orgId=null, 
lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
[16:49:36] Ignite node stopped OK [uptime=00:00:00:182]
{noformat}

3. CacheSpringStoreExample
{noformat}
[16:50:16] Ignite node started OK (id=670dd40a)
[16:50:16] Topology snapshot [ver=13, servers=3, clients=0, CPUs=8, heap=8.0GB]

>>> Cache store example started.
>>> Loaded 0 values into cache.
>>> Loaded 0 keys with backups in 33ms.
Read value: null
Overwrote old value: null
Read value: Person [id=8312945083421167351, orgId=null, lastName=Newton, 
firstName=Isaac, salary=0.0, resume=null]
>>> Store write [key=8312945083421167351, val=Person [id=8312945083421167351, 
>>> orgId=null, lastName=Newton, firstName=Isaac, salary=0.0, resume=null]]
Read value after commit: Person [id=8312945083421167351, orgId=null, 
lastName=Newton, firstName=Isaac, salary=0.0, resume=null]
[16:50:16] Ignite node stopped OK [uptime=00:00:00:469]
{noformat}





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2128) Incorrect output in CacheClientBinaryQueryExample

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2128:


 Summary: Incorrect output in CacheClientBinaryQueryExample
 Key: IGNITE-2128
 URL: https://issues.apache.org/jira/browse/IGNITE-2128
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5
 Environment: OS X 10.10.2
jdk 1.7
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


Steps to reproduce:
1. Start 1 node in IDEA
2. Start 
org/apache/ignite/examples/binary/datagrid/CacheClientBinaryQueryExample.java
Result:
{noformat}
[17:41:30]__   
[17:41:30]   /  _/ ___/ |/ /  _/_  __/ __/ 
[17:41:30]  _/ // (7 7// /  / / / _/   
[17:41:30] /___/\___/_/|_/___/ /_/ /___/  
[17:41:30] 
[17:41:30] ver. 1.5.0-b2#20151210-sha1:d2008c53
[17:41:30] 2015 Copyright(C) Apache Software Foundation
[17:41:30] 
[17:41:30] Ignite documentation: http://ignite.apache.org
[17:41:30] 
[17:41:30] Quiet mode.
[17:41:30]   ^-- Logging to file 
'/Users/gridgain/Downloads/apache-ignite-fabric-1.5-2.0-b2-bin/work/log/ignite-c96bd940.log'
[17:41:30]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[17:41:30] 
[17:41:30] OS: Mac OS X 10.10.3 x86_64
[17:41:30] VM information: Java(TM) SE Runtime Environment 1.7.0_79-b15 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 24.79-b02
[17:41:30] Initial heap size is 192MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[17:41:30] Configured plugins:
[17:41:30]   ^-- None
[17:41:30] 
[17:41:30] Security status [authentication=off, tls/ssl=off]
[17:41:32] Attempting to start more nodes than physical RAM available on 
current host (this can cause significant slowdown)
[17:41:33] Performance suggestions for grid  (fix if possible)
[17:41:33] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[17:41:33]   ^-- Disable peer class loading (set 'peerClassLoadingEnabled' to 
false)
[17:41:33]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[17:41:33] 
[17:41:33] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[17:41:33] 
[17:41:33] Ignite node started OK (id=c96bd940)
[17:41:33] Topology snapshot [ver=7, servers=5, clients=0, CPUs=8, heap=13.0GB]

>>> Binary objects cache query example started.

>>> Employees with zip 94109:

>>> Employees working for GridGain:
>>> Employee [idHash=1570448684, hash=1704762760, departments=BinaryObject 
>>> [idHash=1957010358, hash=-1143237694, typeId=179563853], addr=Address 
>>> [idHash=613549454, hash=220889046, street=1096 Eddy Street, San Francisco, 
>>> CA, zip=94109], name=James Wilson, salary=12500]
>>> Employee [idHash=1856684131, hash=1443330375, departments=BinaryObject 
>>> [idHash=205315160, hash=1785031702, typeId=179563853], addr=Address 
>>> [idHash=1873157038, hash=78336113, street=184 Fidler Drive, San Antonio, 
>>> TX, zip=78130], name=Daniel Adams, salary=11000]
>>> Employee [idHash=40072646, hash=1100837732, departments=BinaryObject 
>>> [idHash=1338579811, hash=290257426, typeId=179563853], addr=Address 
>>> [idHash=472197505, hash=1208142819, street=667 Jerry Dove Drive, Florence, 
>>> SC, zip=29501], name=Cristian Moss, salary=12500]

>>> Employee names and their salaries:
>>> [Name=James Wilson, salary=12500]
>>> [Name=Daniel Adams, salary=11000]
>>> [Name=Cristian Moss, salary=12500]
>>> [Name=Allison Mathis, salary=25300]
>>> [Name=Breana Robbin, salary=6500]
>>> [Name=Philip Horsley, salary=19800]
>>> [Name=Brian Peters, salary=10600]

>>> Employees living in Texas:
{noformat}

as you can see in output no employees with zip code "94109" and no employees 
from Texas but in code were created 2 employees with zip  "94109":
{noformat}
 employeeCache.put(new EmployeeKey(1, 1), new Employee(
"James Wilson",
12500,
new Address("1096 Eddy Street, San Francisco, CA", 94109),
Arrays.asList("Human Resources", "Customer Service")
));

employeeCache.put(new EmployeeKey(4, 2), new Employee(
"Allison Mathis",
25300,
new Address("2702 Freedom Lane, San Francisco, CA", 94109),
Arrays.asList("Development")
));
{noformat}
 and two employees from TX:
{noformat}
 employeeCache.put(new EmployeeKey(2, 1), new Employee(
"Daniel Adams",
11000,
new Address("184 Fidler Drive, San Antonio, TX", 78130),
Arrays.asList("Development", "QA")
));
 employeeCache.put(new EmployeeKey(5, 2), new Employee(
"Breana Robbin",
6500,
new Address("3960 Sundown Lane, Austin, TX", 78130),
Arrays.asList("Sales")
));
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2078) Need to clean cache after query in CacheQueryExample

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2078:


 Summary: Need to clean cache after query in CacheQueryExample
 Key: IGNITE-2078
 URL: https://issues.apache.org/jira/browse/IGNITE-2078
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5
 Environment: OS X 10.10.2
jdk 1.7
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
 Fix For: 1.5


Steps to reproduce:
1. Build examples 
2. Start several nodes: org/apache/ignite/examples/ExampleNodeStartup.java
3. Run org/apache/ignite/examples/datagrid/CacheQueryExample.java
Example output:
{noformat}
>>> Cache query example started.

>>> People with salaries between 0 and 1000 (queried with SCAN query): 
>>> Entry [key=AffinityKey [key=1717604734904449, 
>>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe, 
>>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has 
>>> Bachelor Degree., salary=1000.0]]
>>> Entry [key=AffinityKey [key=-591199628496362239, 
>>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
>>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
>>> Bachelor Degree., salary=1000.0]]

>>> People with salaries between 0 and 1000 (queried with SQL query): 
>>> Entry [key=AffinityKey [key=1717604734904449, 
>>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe, 
>>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has 
>>> Bachelor Degree., salary=1000.0]]
>>> Entry [key=AffinityKey [key=-591199628496362239, 
>>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
>>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
>>> Bachelor Degree., salary=1000.0]]

>>> People with salaries between 1000 and 2000 (queried with SQL query): 
>>> Entry [key=AffinityKey [key=6165286975353599015, 
>>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith, 
>>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has 
>>> Master Degree., salary=2000.0]]
>>> Entry [key=AffinityKey [key=-3732623193094597924, 
>>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe, 
>>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has 
>>> Master Degree., salary=2000.0]]

>>> Following people are 'ApacheIgnite' employees: 

>>> Following people are 'Other' employees: 
>>> Entry [key=AffinityKey [key=-591199628496362239, 
>>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
>>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
>>> Bachelor Degree., salary=1000.0]]

>>> Following people have 'Master Degree' in their resumes: 
>>> Entry [key=AffinityKey [key=6165286975353599015, 
>>> affKey=-7983468300595888028], val=Person [firstName=Jane, lastName=Smith, 
>>> id=6165286975353599015, orgId=-7983468300595888028, resume=Jane Smith has 
>>> Master Degree., salary=2000.0]]
>>> Entry [key=AffinityKey [key=-3732623193094597924, 
>>> affKey=-6908357575301716955], val=Person [firstName=John, lastName=Doe, 
>>> id=-3732623193094597924, orgId=-6908357575301716955, resume=John Doe has 
>>> Master Degree., salary=2000.0]]

>>> Following people have 'Bachelor Degree' in their resumes: 
>>> Entry [key=AffinityKey [key=1717604734904449, 
>>> affKey=-6908357575301716955], val=Person [firstName=Jane, lastName=Doe, 
>>> id=1717604734904449, orgId=-6908357575301716955, resume=Jane Doe has 
>>> Bachelor Degree., salary=1000.0]]
>>> Entry [key=AffinityKey [key=-591199628496362239, 
>>> affKey=-7983468300595888028], val=Person [firstName=John, lastName=Smith, 
>>> id=-591199628496362239, orgId=-7983468300595888028, resume=John Smith has 
>>> Bachelor Degree., salary=1000.0]]

>>> Average salary for 'ApacheIgnite' employees: 
>>> [null]

>>> Names of all employees:
>>> [Jane Smith]
>>> [Jane Doe]
>>> [John Doe]
>>> [John Smith]

>>> Names of all employees and organizations they belong to:
>>> [John Smith, Other]

>>> Cache query example finished.
[13:01:23] Ignite node stopped OK [uptime=00:00:01:297]
{noformat}
4. Start example second time (don't stop nodes).
Example output:
{noformat}
>>> Cache query example started.

[jira] [Created] (IGNITE-2041) CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2041:


 Summary: CacheAutoStoreExample: Failed to find class with given 
class loader for unmarshalling
 Key: IGNITE-2041
 URL: https://issues.apache.org/jira/browse/IGNITE-2041
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.5
Reporter: Ilya Suntsov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 1.5


Steps for reproduce:
1. Start
examples/src/main/java/org/apache/ignite/examples/datagrid/store/auto/DbH2ServerStartup.java
2. Start 1 node from IDEA and 1 from terminal (with 
examples/config/example-ignite.xml)
3. Run CacheAutoStoreExample
Result:
Node in terminal:
{noformat}
mpb:bin gridgain$ ./ignite.sh ../examples/config/example-ignite.xml -v
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
support was removed in 8.0
Ignite Command Line Startup, ver. 1.5.1-EA#20151130-sha1:4f1d55cc
2015 Copyright(C) Apache Software Foundation

[15:26:14,676][INFO][main][IgniteKernal] 

>>>__    
>>>   /  _/ ___/ |/ /  _/_  __/ __/  
>>>  _/ // (7 7// /  / / / _/
>>> /___/\___/_/|_/___/ /_/ /___/   
>>> 
>>> ver. 1.5.1-EA#20151130-sha1:4f1d55cc
>>> 2015 Copyright(C) Apache Software Foundation
>>> 
>>> Ignite documentation: http://ignite.apache.org

[15:26:14,677][INFO][main][IgniteKernal] Config URL: 
file:/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/bin/../examples/config/example-ignite.xml
[15:26:14,677][INFO][main][IgniteKernal] Daemon mode: off
[15:26:14,677][INFO][main][IgniteKernal] OS: Mac OS X 10.10.3 x86_64
[15:26:14,677][INFO][main][IgniteKernal] OS user: gridgain
[15:26:14,677][INFO][main][IgniteKernal] Language runtime: Java Platform API 
Specification ver. 1.8
[15:26:14,678][INFO][main][IgniteKernal] VM information: Java(TM) SE Runtime 
Environment 1.8.0_45-b14 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 
25.45-b02
[15:26:14,679][INFO][main][IgniteKernal] VM total memory: 0.96GB
[15:26:14,679][INFO][main][IgniteKernal] Remote Management [restart: on, REST: 
on, JMX (remote: on, port: 49113, auth: off, ssl: off)]
[15:26:14,679][INFO][main][IgniteKernal] 
IGNITE_HOME=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA
[15:26:14,680][INFO][main][IgniteKernal] VM arguments: [-Xms1g, -Xmx1g, 
-XX:+AggressiveOpts, -XX:MaxPermSize=256m, -DIGNITE_QUIET=false, 
-DIGNITE_SUCCESS_FILE=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/work/ignite_success_6cde77f0-d8a7-44f7-8e33-ad553102eb52,
 -Dcom.sun.management.jmxremote, -Dcom.sun.management.jmxremote.port=49113, 
-Dcom.sun.management.jmxremote.authenticate=false, 
-Dcom.sun.management.jmxremote.ssl=false, 
-DIGNITE_HOME=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA, 
-DIGNITE_PROG_NAME=./ignite.sh]
[15:26:14,680][INFO][main][IgniteKernal] Configured caches 
['ignite-marshaller-sys-cache', 'ignite-sys-cache', 'ignite-atomics-sys-cache']
[15:26:14,680][WARNING][main][IgniteKernal] Peer class loading is enabled 
(disable it in production for performance and deployment consistency reasons)
[15:26:14,683][INFO][main][IgniteKernal] 3-rd party licenses can be found at: 
/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/libs/licenses
[15:26:14,741][INFO][main][IgniteKernal] Non-loopback local IPs: 192.168.1.113, 
fe80:0:0:0:3e07:54ff:fe6b:6c35%en0
[15:26:14,741][INFO][main][IgniteKernal] Enabled local MACs: 3C07546B6C35
[15:26:14,752][INFO][main][IgnitePluginProcessor] Configured plugins:
[15:26:14,752][INFO][main][IgnitePluginProcessor]   ^-- GridGain 
7.5.1-EA#20151130-sha1:7528584b
[15:26:14,752][INFO][main][IgnitePluginProcessor]   ^-- 2015 Copyright(C) 
GridGain Systems
[15:26:14,753][INFO][main][IgnitePluginProcessor] 
[15:26:14,815][INFO][main][TcpCommunicationSpi] IPC shared memory server 
endpoint started [port=48101, 
tokDir=/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1-EA/work/ipc/shmem/358d6354-ed8f-4806-8da3-3d19971fa90b-703]
[15:26:14,815][INFO][main][TcpCommunicationSpi] Successfully bound shared 
memory communication to TCP port [port=48101, locHost=0.0.0.0/0.0.0.0]
[15:26:14,841][INFO][main][TcpCommunicationSpi] Successfully bound to TCP port 
[port=47101, locHost=0.0.0.0/0.0.0.0]
[15:26:14,861][WARNING][main][NoopCheckpointSpi] Checkpoints are disabled (to 
enable configure any GridCheckpointSpi implementation)
[15:26:14,884][WARNING][main][GridCollisionManager] Collision resolution is 
disabled (all jobs will be activated upon arrival).
[15:26:14,927][WARNING][main][NoopSwapSpaceSpi] Swap space is disabled. To 
enable use FileSwapSpaceSpi.
[15:26:14,929][INFO][main][IgniteKernal] Security status [authentication=off, 
tls/ssl=off]
[15:26:15,133][INFO][main][GridTcpRestProtocol] Command protocol succes

[jira] [Created] (IGNITE-2034) Need to print information about marshaller in log (for yardstick-ignite)

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2034:


 Summary: Need to print information about marshaller in log (for 
yardstick-ignite)
 Key: IGNITE-2034
 URL: https://issues.apache.org/jira/browse/IGNITE-2034
 Project: Ignite
  Issue Type: Task
  Components: cache
Affects Versions: 1.5
Reporter: Ilya Suntsov
Assignee: Artem Shutak
 Fix For: 1.6


In yardstick's driver and yardstick's servers logs need to print information 
about marshaller that is used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2035) Misprint in javadoc

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2035:


 Summary: Misprint in javadoc
 Key: IGNITE-2035
 URL: https://issues.apache.org/jira/browse/IGNITE-2035
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 1.5
 Environment: OS X 10.10.2
jdk 1.8.45
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov
Priority: Minor
 Fix For: 1.5


ComputeClientBinaryTaskExecutionExample:
{noformat}
* 
 * Remote nodes should always be started with special configuration file which
 * enables the binary marshaller: {@code 'ignite.{sh|bat} 
examples/config/binary/example-ignite-binary.xml'}.
 * 
{noformat}

There isn't examples/config/binary/example-ignite-binary.xml in build



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2024) CacheAutoStoreExample: Failed to execute compound future reducer

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2024:


 Summary: CacheAutoStoreExample: Failed to execute compound future 
reducer
 Key: IGNITE-2024
 URL: https://issues.apache.org/jira/browse/IGNITE-2024
 Project: Ignite
  Issue Type: Bug
 Environment: OS X 10.10.2
jdk-1.8.45
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov


Steps for reproduce:
1. Build examples with profiles java8 and lgpl
2. Run DbH2ServerStartup
3. Start 2 nodes using ExampleNodeStartup
4. Run CacheAutoStoreExample
Result:
Got exceptions:
CacheAutoStoreExample:
{noformat}
[23:54:21]__   
[23:54:21]   /  _/ ___/ |/ /  _/_  __/ __/ 
[23:54:21]  _/ // (7 7// /  / / / _/   
[23:54:21] /___/\___/_/|_/___/ /_/ /___/  
[23:54:21] 
[23:54:21] ver. 1.5.1#20151128-sha1:4c014a47
[23:54:21] 2015 Copyright(C) Apache Software Foundation
[23:54:21] 
[23:54:21] Ignite documentation: http://ignite.apache.org
[23:54:21] 
[23:54:21] Quiet mode.
[23:54:21]   ^-- Logging to file 
'/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1/work/log/ignite-25bd3c3d.log'
[23:54:21]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[23:54:21] 
[23:54:21] OS: Mac OS X 10.10.3 x86_64
[23:54:21] VM information: Java(TM) SE Runtime Environment 1.8.0_45-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.45-b02
[23:54:21] Initial heap size is 192MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[23:54:22] Configured plugins:
[23:54:22]   ^-- GridGain 7.5.1#20151128-sha1:c8fb3cdd
[23:54:22]   ^-- 2015 Copyright(C) GridGain Systems
[23:54:22] 
[23:54:22] Security status [authentication=off, tls/ssl=off]
[23:54:22] Rolling updates are disabled. GridGain version update will require 
full cluster restart. Consider changing 
'GridGainConfiguration.rollingUpdatesEnabled' configuration property.
[23:54:23,737][ERROR][main][GridEntLicenseProcessor] License violation detected:
  ^-- Maximum number of nodes (3/2) is exceeded.
[23:54:23,737][ERROR][main][GridEntLicenseProcessor] Contact sa...@gridgain.com 
for further assistance. Make sure to include your license ID: 
14177F1A-5B5A-4F9C-BC55-F7335715F311
[23:54:23,737][ERROR][main][GridEntLicenseProcessor] License grace/burst period 
- left 1 hour.
[23:54:23] Performance suggestions for grid  (fix if possible)
[23:54:23] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[23:54:23]   ^-- Disable peer class loading (set 'peerClassLoadingEnabled' to 
false)
[23:54:23]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[23:54:23]   ^-- Use default binary marshaller (do not set 'marshaller' 
explicitly)
[23:54:23] 
[23:54:23] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[23:54:23] 
[23:54:23] Ignite node started OK (id=25bd3c3d)
[23:54:23] Topology snapshot [ver=3, servers=3, clients=0, CPUs=8, heap=8.0GB]

>>> Cache auto store example started.
[23:54:24] (err) Failed to execute compound future reducer: Compound future 
listener []class org.apache.ignite.IgniteCheckedException: 
javax.cache.CacheException: Failed to find getter in POJO class 
[class=org.apache.ignite.examples.model.Person, prop=id]
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:309)
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:265)
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAllFromStore(GridCacheStoreManagerAdapter.java:398)
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAll(GridCacheStoreManagerAdapter.java:364)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.loadMissingFromStore(GridDhtLockFuture.java:1016)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:745)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onDone(GridDhtLockFuture.java:724)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onDone(GridDhtLockFuture.java:79)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:323)
at 
org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:301)
at 
org.apache.ignite.internal.util.future.GridCompoundFuture.markInitialized(GridCompoundFuture.java:292)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.map(GridDhtLockFuture.java:958)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onOwnerChanged(Gri