[jira] [Commented] (IGNITE-1395) REST HTTP module prints out unnecessary message
[
https://issues.apache.org/jira/browse/IGNITE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747090#comment-14747090
]
Roman Shtykh commented on IGNITE-1395:
--
I will have a look at this issue. Can you please assign me?
> REST HTTP module prints out unnecessary message
> ---
>
> Key: IGNITE-1395
> URL: https://issues.apache.org/jira/browse/IGNITE-1395
> Project: Ignite
> Issue Type: Bug
> Components: newbie
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Priority: Minor
> Labels: newbie
> Fix For: ignite-1.5
>
>
> 1. Copy directory libs/optional/ignite-rest-http in libs/
> 2. Start node in quiet mode.
> 3. The output is following:
> {noformat}
> ...
> [17:49:42] Quiet mode.
> ...
> [17:49:50] Security status [authentication=off, communication encryption=off]
> 2015-09-09 17:49:50.789:INFO::main: Logging initialized @9841ms
> [17:49:52] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [17:49:52]
> [17:49:52] Ignite node started OK (id=54eee2db)
> [17:49:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=1.0GB]
> ...
> {noformat}
> The message after security status is generated by REST HTTP module.
> 1. It has wrong format
> 2. It should not be printed in quiet mode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1495) Cache SQL query metadata index's fields have wrong register.
Vasiliy Sisko created IGNITE-1495: - Summary: Cache SQL query metadata index's fields have wrong register. Key: IGNITE-1495 URL: https://issues.apache.org/jira/browse/IGNITE-1495 Project: Ignite Issue Type: Bug Components: SQL Affects Versions: ignite-1.5 Reporter: Vasiliy Sisko Assignee: Vasiliy Sisko Fix For: ignite-1.5 Index's fields should have register how in table fields (In upper case). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[
https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747218#comment-14747218
]
Pavel Konstantinov commented on IGNITE-851:
---
I've opened Caches page and clicked New button during loading information about
caches
{code}
prepareNewItem@http://webconsole.gridgain.com/caches-controller.js:375:21
$scope.createItem@http://webconsole.gridgain.com/caches-controller.js:393:46
anonymous/fn@http://ajax.googleapis.com/ajax/libs/angularjs/1.4.5/angular.min.js
line 212 > Function:2:218
Ic[c]http://ajax.googleapis.com/ajax/libs/angularjs/1.4.5/angular.min.js:252:74
{code}
> Implement caches screen
> ---
>
> Key: IGNITE-851
> URL: https://issues.apache.org/jira/browse/IGNITE-851
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
> Fix For: ignite-1.5
>
> Attachments: Caches.pdf, caches-page-advanced-2.png
>
>
> See screenshot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1495) Cache SQL query metadata index's fields have wrong register.
[ https://issues.apache.org/jira/browse/IGNITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-1495: -- Attachment: #_IGNITE-1495_Test_for_index_s_fields.patch > Cache SQL query metadata index's fields have wrong register. > > > Key: IGNITE-1495 > URL: https://issues.apache.org/jira/browse/IGNITE-1495 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: ignite-1.5 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > Attachments: #_IGNITE-1495_Test_for_index_s_fields.patch > > > Index's fields should have register how in table fields (In upper case). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1495) Cache SQL query metadata index's fields have wrong register.
[ https://issues.apache.org/jira/browse/IGNITE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747223#comment-14747223 ] tc_commenter commented on IGNITE-1495: -- There was triggered next test builds for last attached patch-file: 01. http://204.14.53.153/viewQueued.html?itemId=106243 - Ignite AOP 02. http://204.14.53.153/viewQueued.html?itemId=106244 - Ignite Basic 03. http://204.14.53.153/viewQueued.html?itemId=106245 - Ignite Cache 04. http://204.14.53.153/viewQueued.html?itemId=106246 - Ignite Cache 2 05. http://204.14.53.153/viewQueued.html?itemId=106247 - Ignite Cache 3 06. http://204.14.53.153/viewQueued.html?itemId=106248 - Ignite Cache 4 07. http://204.14.53.153/viewQueued.html?itemId=106249 - Ignite Cache Expiry Policy 08. http://204.14.53.153/viewQueued.html?itemId=106250 - Ignite Cache Failover 09. http://204.14.53.153/viewQueued.html?itemId=106251 - Ignite Cache Failover Multi JVM 10. http://204.14.53.153/viewQueued.html?itemId=106252 - Ignite Cache Failover2 11. http://204.14.53.153/viewQueued.html?itemId=106253 - Ignite Cache Full API 12. http://204.14.53.153/viewQueued.html?itemId=106254 - Ignite Cache Full API Multi JVM 13. http://204.14.53.153/viewQueued.html?itemId=106255 - Ignite Cache Full API Portable 14. http://204.14.53.153/viewQueued.html?itemId=106256 - Ignite Cache Portable 15. http://204.14.53.153/viewQueued.html?itemId=106257 - Ignite Cache Query Portable 16. http://204.14.53.153/viewQueued.html?itemId=106258 - Ignite Cache Restarts 17. http://204.14.53.153/viewQueued.html?itemId=106259 - Ignite Cache Tx Recovery 18. http://204.14.53.153/viewQueued.html?itemId=106260 - Ignite Cloud 19. http://204.14.53.153/viewQueued.html?itemId=106261 - Ignite Compute Grid 20. http://204.14.53.153/viewQueued.html?itemId=106262 - Ignite Data Strucutures 21. http://204.14.53.153/viewQueued.html?itemId=106263 - Ignite Examples 22. http://204.14.53.153/viewQueued.html?itemId=106264 - Ignite GCE 23. http://204.14.53.153/viewQueued.html?itemId=106265 - Ignite Geospacial Indexing 24. http://204.14.53.153/viewQueued.html?itemId=106266 - Ignite H2 Indexing 25. http://204.14.53.153/viewQueued.html?itemId=106267 - Ignite Hadoop 26. http://204.14.53.153/viewQueued.html?itemId=106268 - Ignite Hibernate 27. http://204.14.53.153/viewQueued.html?itemId=106269 - Ignite IGFS 28. http://204.14.53.153/viewQueued.html?itemId=106270 - Ignite IGFS Examples 29. http://204.14.53.153/viewQueued.html?itemId=106271 - Ignite IGFS Linux and MacOS 30. http://204.14.53.153/viewQueued.html?itemId=106272 - Ignite Java Client 31. http://204.14.53.153/viewQueued.html?itemId=106273 - Ignite JDBC Driver 32. http://204.14.53.153/viewQueued.html?itemId=106274 - Ignite JTA 33. http://204.14.53.153/viewQueued.html?itemId=106275 - Ignite Logging 34. http://204.14.53.153/viewQueued.html?itemId=106276 - Ignite Portables Basic 35. http://204.14.53.153/viewQueued.html?itemId=106277 - Ignite Queries 36. http://204.14.53.153/viewQueued.html?itemId=106278 - Ignite Scalar Examples 37. http://204.14.53.153/viewQueued.html?itemId=106279 - Ignite SPI 38. http://204.14.53.153/viewQueued.html?itemId=106280 - Ignite Spring 39. http://204.14.53.153/viewQueued.html?itemId=106281 - Ignite Start Nodes 40. http://204.14.53.153/viewQueued.html?itemId=106282 - Ignite URI Deploy SPI 41. http://204.14.53.153/viewQueued.html?itemId=106283 - Ignite Visor Console 42. http://204.14.53.153/viewQueued.html?itemId=106284 - Ignite WebSessions 43. http://204.14.53.153/viewQueued.html?itemId=106285 - JCache TCK > Cache SQL query metadata index's fields have wrong register. > > > Key: IGNITE-1495 > URL: https://issues.apache.org/jira/browse/IGNITE-1495 > Project: Ignite > Issue Type: Bug > Components: SQL >Affects Versions: ignite-1.5 >Reporter: Vasiliy Sisko >Assignee: Sergi Vladykin > Fix For: ignite-1.5 > > Attachments: #_IGNITE-1495_Test_for_index_s_fields.patch > > > Index's fields should have register how in table fields (In upper case). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1493) Fatal exception is thrown during queue instantiation when using Ignite with an HP-UX machine.
[
https://issues.apache.org/jira/browse/IGNITE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747230#comment-14747230
]
Vladimir Ozerov commented on IGNITE-1493:
-
1) Analysis of a similar problem in another Java project:
https://github.com/dain/snappy/issues/24
2) Reference to OpenJDK docs:
https://github.com/openjdk-mirror/jdk7u-jdk/blob/master/src/share/classes/sun/misc/Unsafe.java
{code}The object referred to by o is an array, and the offset is
an integer of the form B+N*S, where N is valid index
into the array, and B and S are values obtained by
{@link #arrayBaseOffset} and {@link #arrayIndexScale} (respectively) from the
array's class.{code}
3) GridUnsafeDataOutput do not consult to arrayIndexScale().
> Fatal exception is thrown during queue instantiation when using Ignite with
> an HP-UX machine.
> -
>
> Key: IGNITE-1493
> URL: https://issues.apache.org/jira/browse/IGNITE-1493
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Environment: * HP-UX B.11.31 IA64W machine
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
>Reporter: Nicholas Dzwill
>Priority: Blocker
> Attachments: ErrorLog.txt, server.log
>
>
> A fatal exception is thrown during queue instantiation when using an HP-UX
> B.11.31 IA64W machine.
> The environment is as follows:
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
> The error logged is as follows:
> * Current thread (01ab2800): JavaThread "main" [_thread_in_vm, id=23,
> lwp_id=3525570, stack(4e501000,4e601000)]
> * siginfo:si_signo=SIGBUS: si_errno=0, si_code=1 (BUS_ADRALN),
> si_addr=5e038d15
>
> The exception above means there is an "invalid address alignment" (writing to
> an odd memory location) when calling the following method:
> * Class: org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream
> * Method:
> {code:borderStyle=solid}
>/** {@inheritDoc} */
> @Override public void writeInt(int v) throws IOException {
> requestFreeSize(4);
> UNSAFE.putInt(bytes, byteArrOff + off, v); // byteArrOff + off =
> 17 when this exception is thrown
> onWrite(4);
> }
> {code}
>
> Basic setup - Ignite is configured with spring and pushed to the constructor
> of a class. That class uses this instance of Ignite to instantiate an
> IgniteQueue as follows:
> {code:borderStyle=solid}
> CollectionConfiguration configuration = new CollectionConfiguration();
> configuration.setCollocated(true);
> IgniteQueue queue = ignite.queue("queue", 0, configuration);
> {code}
>
> Partial stack:
> * Instantiating the queue calls:
> **
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.compatibleConfiguration()
>
> * Which in turn calls:
> ** org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke()
> * Leading to the fatal error when calling:
> **
> org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeInt()
> The error log has been attached with the stack trace of the error. The
> server log is also attached. We are running Ignite in a variety of
> environments and this issue only appears to exist in this specific
> environment and is consistently hit in the same place with no apparent
> work-around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1147. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) I added logic that disable "Save" button on profile page when nothing to save. > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747285#comment-14747285 ] Alexey Kuznetsov commented on IGNITE-851: - Fixed page loading algorithm: load data first, then load page descriptor. Will add spinner later. > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1395) REST HTTP module prints out unnecessary message
[
https://issues.apache.org/jira/browse/IGNITE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747343#comment-14747343
]
Roman Shtykh commented on IGNITE-1395:
--
"Logging initialized ..." line is printed out because
org.eclipse.jetty.util.log.Slf4jLog requires org.slf4j.Logger, fails to find it
and initializes StdErrLog with INFO level. The attached patch is a simple fix
for the issue.
> REST HTTP module prints out unnecessary message
> ---
>
> Key: IGNITE-1395
> URL: https://issues.apache.org/jira/browse/IGNITE-1395
> Project: Ignite
> Issue Type: Bug
> Components: newbie
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Priority: Minor
> Labels: newbie
> Fix For: ignite-1.5
>
>
> 1. Copy directory libs/optional/ignite-rest-http in libs/
> 2. Start node in quiet mode.
> 3. The output is following:
> {noformat}
> ...
> [17:49:42] Quiet mode.
> ...
> [17:49:50] Security status [authentication=off, communication encryption=off]
> 2015-09-09 17:49:50.789:INFO::main: Logging initialized @9841ms
> [17:49:52] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [17:49:52]
> [17:49:52] Ignite node started OK (id=54eee2db)
> [17:49:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=1.0GB]
> ...
> {noformat}
> The message after security status is generated by REST HTTP module.
> 1. It has wrong format
> 2. It should not be printed in quiet mode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1395) REST HTTP module prints out unnecessary message
[
https://issues.apache.org/jira/browse/IGNITE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-1395:
-
Attachment: ignite-1395.patch
> REST HTTP module prints out unnecessary message
> ---
>
> Key: IGNITE-1395
> URL: https://issues.apache.org/jira/browse/IGNITE-1395
> Project: Ignite
> Issue Type: Bug
> Components: newbie
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Priority: Minor
> Labels: newbie
> Fix For: ignite-1.5
>
> Attachments: ignite-1395.patch
>
>
> 1. Copy directory libs/optional/ignite-rest-http in libs/
> 2. Start node in quiet mode.
> 3. The output is following:
> {noformat}
> ...
> [17:49:42] Quiet mode.
> ...
> [17:49:50] Security status [authentication=off, communication encryption=off]
> 2015-09-09 17:49:50.789:INFO::main: Logging initialized @9841ms
> [17:49:52] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [17:49:52]
> [17:49:52] Ignite node started OK (id=54eee2db)
> [17:49:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=1.0GB]
> ...
> {noformat}
> The message after security status is generated by REST HTTP module.
> 1. It has wrong format
> 2. It should not be printed in quiet mode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1136) NPE when cache starts
[
https://issues.apache.org/jira/browse/IGNITE-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747362#comment-14747362
]
Vladimir Ozerov commented on IGNITE-1136:
-
Cannot reproduce.
> NPE when cache starts
> -
>
> Key: IGNITE-1136
> URL: https://issues.apache.org/jira/browse/IGNITE-1136
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: ignite-1.4
>
>
> During working on IGNITE-1079 ticket the following problem was found:
> {noformat}
> Got exception while starting (will rollback startup routine).
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.onKernalStart(GridDhtCacheAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1144)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:843)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:830)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at
> io.vertx.spi.cluster.ignite.IgniteClusterManager.lambda$join$5(IgniteClusterManager.java:194)
> at
> io.vertx.spi.cluster.ignite.IgniteClusterManager$$Lambda$19/1900164709.handle(Unknown
> Source)
> at
> io.vertx.core.impl.ContextImpl.lambda$executeBlocking$18(ContextImpl.java:279)
> at io.vertx.core.impl.ContextImpl$$Lambda$20/1445157774.run(Unknown
> Source)
> at
> io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor.lambda$new$101(OrderedExecutorFactory.java:91)
> at
> io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor$$Lambda$16/1061804750.run(Unknown
> Source)
> 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}
> The problem reproduces not always. In order to reproduce this need to start
> IgniteComplexHATest (see https://github.com/agura/vertx-ignite) and run tests
> several times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1136) NPE when cache starts
[
https://issues.apache.org/jira/browse/IGNITE-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura resolved IGNITE-1136.
-
Resolution: Cannot Reproduce
I can't reproduce it also. So I close this ticket.
> NPE when cache starts
> -
>
> Key: IGNITE-1136
> URL: https://issues.apache.org/jira/browse/IGNITE-1136
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: ignite-1.4
>
>
> During working on IGNITE-1079 ticket the following problem was found:
> {noformat}
> Got exception while starting (will rollback startup routine).
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.onKernalStart(GridDhtCacheAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1144)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:843)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:830)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at
> io.vertx.spi.cluster.ignite.IgniteClusterManager.lambda$join$5(IgniteClusterManager.java:194)
> at
> io.vertx.spi.cluster.ignite.IgniteClusterManager$$Lambda$19/1900164709.handle(Unknown
> Source)
> at
> io.vertx.core.impl.ContextImpl.lambda$executeBlocking$18(ContextImpl.java:279)
> at io.vertx.core.impl.ContextImpl$$Lambda$20/1445157774.run(Unknown
> Source)
> at
> io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor.lambda$new$101(OrderedExecutorFactory.java:91)
> at
> io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor$$Lambda$16/1061804750.run(Unknown
> Source)
> 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}
> The problem reproduces not always. In order to reproduce this need to start
> IgniteComplexHATest (see https://github.com/agura/vertx-ignite) and run tests
> several times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1136) NPE when cache starts
[
https://issues.apache.org/jira/browse/IGNITE-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura closed IGNITE-1136.
---
> NPE when cache starts
> -
>
> Key: IGNITE-1136
> URL: https://issues.apache.org/jira/browse/IGNITE-1136
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: ignite-1.4
>
>
> During working on IGNITE-1079 ticket the following problem was found:
> {noformat}
> Got exception while starting (will rollback startup routine).
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.onKernalStart(GridDhtCacheAdapter.java:152)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:1144)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:843)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:830)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1538)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1405)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:931)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:477)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:458)
> at org.apache.ignite.Ignition.start(Ignition.java:321)
> at
> io.vertx.spi.cluster.ignite.IgniteClusterManager.lambda$join$5(IgniteClusterManager.java:194)
> at
> io.vertx.spi.cluster.ignite.IgniteClusterManager$$Lambda$19/1900164709.handle(Unknown
> Source)
> at
> io.vertx.core.impl.ContextImpl.lambda$executeBlocking$18(ContextImpl.java:279)
> at io.vertx.core.impl.ContextImpl$$Lambda$20/1445157774.run(Unknown
> Source)
> at
> io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor.lambda$new$101(OrderedExecutorFactory.java:91)
> at
> io.vertx.core.impl.OrderedExecutorFactory$OrderedExecutor$$Lambda$16/1061804750.run(Unknown
> Source)
> 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}
> The problem reproduces not always. In order to reproduce this need to start
> IgniteComplexHATest (see https://github.com/agura/vertx-ignite) and run tests
> several times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1492) Platform .Net: Set up FxCop project, fix/suppress warnings
[ https://issues.apache.org/jira/browse/IGNITE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768830#comment-14768830 ] ASF GitHub Bot commented on IGNITE-1492: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/95 IGNITE-1492 Platform .Net: Set up FxCop project, fix/suppress warnings You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1492 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/95.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #95 commit 7cc621c7b46539599411faaf091ba756ea13a7c0 Author: ptupitsyn Date: 2015-09-16T09:13:08Z wip commit b01a5284d3dedb0f8abbdcd7f655b41423697cb1 Author: ptupitsyn Date: 2015-09-16T09:14:33Z wip commit 2f0c98bb731421d9bad17f64aa10518bff9d623d Author: ptupitsyn Date: 2015-09-16T09:17:39Z Add global suppressions commit 52383ed07e18b3696f4b1bb91f97d64407f0667d Author: ptupitsyn Date: 2015-09-16T09:19:34Z wip commit 2f6edd12386e46216bc3900bfcdce7427e77 Author: ptupitsyn Date: 2015-09-16T09:28:13Z wip commit c35e342ea129644a64c61eb3e2c046ad04050ede Author: ptupitsyn Date: 2015-09-16T09:35:50Z wip commit 03b666fade29c20b2d95fbb64242d1f5d833 Author: ptupitsyn Date: 2015-09-16T09:51:20Z wip commit 1b2a5466d26d91d10df31a4ac8a723f1cfb03b6a Author: ptupitsyn Date: 2015-09-16T09:55:41Z fix EventType commit cc58b106b1c738b74cf3246cf5bba08d4ffa3602 Author: ptupitsyn Date: 2015-09-16T09:56:36Z wip commit 1c8b2338f86a8b013bbf1b8ade428eb40a2cfaae Author: ptupitsyn Date: 2015-09-16T10:01:18Z Fix JvmContext init commit 8a3153e65b3c7ce663ed5300a9476be595117c8c Author: ptupitsyn Date: 2015-09-16T10:03:31Z wip commit 0d5decfbe52b2e1509fe29219a3f5da7180a76a3 Author: ptupitsyn Date: 2015-09-16T10:04:41Z wip commit 386f11a0fbebc9f11e59730f7523a22140d3b2c0 Author: ptupitsyn Date: 2015-09-16T10:06:47Z wip commit ffb3d2b78061771b979e040289dae93fb246d9b8 Author: ptupitsyn Date: 2015-09-16T10:07:42Z wip commit bcecd28384f9aa67a1514e18e37238ba15aefaf1 Author: ptupitsyn Date: 2015-09-16T10:08:37Z wip commit f1724c52b29b01b6350091d41cf27fe7990ef6ce Author: ptupitsyn Date: 2015-09-16T10:09:57Z wip commit a7914ca0899626ee66ab7c114b17a6a3d96b6d07 Author: ptupitsyn Date: 2015-09-16T10:10:53Z wip commit d83fa6af5e93a77c43a57cc63433c5d669492b3b Author: ptupitsyn Date: 2015-09-16T10:14:46Z wip commit 7d0b850e765cc194ba63b1adb962afaa15a5ccfd Author: ptupitsyn Date: 2015-09-16T10:17:33Z wip commit 5cf1e7b25cdfd2041d7ccde715dc4fba6220e4e8 Author: ptupitsyn Date: 2015-09-16T10:18:48Z wip commit e558179e484f26f51d00d277dcb81ad7033165c7 Author: ptupitsyn Date: 2015-09-16T10:21:27Z wip commit dd0b62ed96c208253a26c0eb728df0d5bb64db28 Author: ptupitsyn Date: 2015-09-16T10:22:35Z wip commit 343cd851232b08f2d3989e9f6064111220d56d80 Author: ptupitsyn Date: 2015-09-16T10:23:51Z wip commit b77b50cde0a29d99f60f7bfa69ea8500bc4cabe1 Author: ptupitsyn Date: 2015-09-16T10:24:57Z wip commit f7cf5a8f65b3f9f15391857386bf98a946cdfbbf Author: ptupitsyn Date: 2015-09-16T10:26:20Z wip commit a9bf502709b7521112566f316849208e0a6636b0 Author: ptupitsyn Date: 2015-09-16T10:33:00Z wip commit 80c5ed4d22722acaee293acfc7fe8d3eccfb10ee Author: ptupitsyn Date: 2015-09-16T10:36:35Z wip commit 696365f6db977003f6d7a9e5f851e297dd1dea05 Author: ptupitsyn Date: 2015-09-16T10:41:45Z wip commit eccefd2309678a00c9b396d8848e08d6ff0f65f8 Author: ptupitsyn Date: 2015-09-16T10:47:21Z wip commit ad626f1c3c186debf7c9d86a17b1959258ddf8eb Author: ptupitsyn Date: 2015-09-16T10:49:58Z wip > Platform .Net: Set up FxCop project, fix/suppress warnings > -- > > Key: IGNITE-1492 > URL: https://issues.apache.org/jira/browse/IGNITE-1492 > Project: Ignite > Issue Type: Sub-task >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768918#comment-14768918
]
Chandresh Pancholi commented on IGNITE-429:
---
Gian,
I am facing some issue. i have pushed my changes
(https://github.com/chandresh-pancholi/ignite). can you please check and let me
know so that i can modify the code.
module - storm
> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm
> and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1492) Platform .Net: Set up FxCop project, fix/suppress warnings
[ https://issues.apache.org/jira/browse/IGNITE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14768931#comment-14768931 ] Pavel Tupitsyn commented on IGNITE-1492: - All errors and warnings fixed or suppressed, FxCop step enabled on TC. > Platform .Net: Set up FxCop project, fix/suppress warnings > -- > > Key: IGNITE-1492 > URL: https://issues.apache.org/jira/browse/IGNITE-1492 > Project: Ignite > Issue Type: Sub-task >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1496) Platform .Net: Add .Net examples
Pavel Tupitsyn created IGNITE-1496: --- Summary: Platform .Net: Add .Net examples Key: IGNITE-1496 URL: https://issues.apache.org/jira/browse/IGNITE-1496 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: ignite-1.5 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: ignite-1.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1221) Proper GridCacheContext cleanup
[
https://issues.apache.org/jira/browse/IGNITE-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov reassigned IGNITE-1221:
-
Assignee: Andrey Gura
> Proper GridCacheContext cleanup
> ---
>
> Key: IGNITE-1221
> URL: https://issues.apache.org/jira/browse/IGNITE-1221
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Sometimes when a cache is stopped and its corresponding {{GridCacheContext}}
> is cleaned up there are some threads exist that keep executing cache related
> operations.
> This may lead to deadlocks, hangs and other unpredictable results.
> Initial discussion on the dev list:
> http://mail-archives.apache.org/mod_mbox/incubator-ignite-dev/201508.mbox/browser
> Look for discussion "Fixed deadlock in GridDhtAtomicCache (Alex G. your
> review is needed)"
> As an example, the bug described and fixed as IGNITE-1189 was caused by
> already invalidated {{GridCacheContext}}.
> Moreover, Andrey Gura reports that he observes hangs in cache's read
> operations probably caused by the same reason.
> To reproduce try to do the following.
> Temporary comment out the following catch block in
> {{GridDhtAtomicCache.updateAllAsyncInternal0}}:
> {noformat}
> catch (Exception e) {
> // At least RuntimeException can be thrown by the code above when
> GridCacheContext is cleaned and there is
> // an attempt to use cleaned resources.
> U.error(log, "Unexpected exception during cache update", e);
> res.addFailedKeys(keys, e);
> completionCb.apply(req, res);
> return;
> }
> {noformat}
> Run {{IgniteCacheAtomicNodeRestartTest.testRestartWithPutTenNodesTwoBackups}}
> in a loop using TeamCity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1494) putAll after put doesn't update values
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov closed IGNITE-1494.
-
> putAll after put doesn't update values
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
> Attachments: CacheEvictExample.java, example-evict.xml
>
>
> 1. Copy example-evict.xml in examples/config directory
> 2. Copy CacheEvictExample in org.apache.ignite.examples.datagrid package
> 3. Start node bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheEvictExample (it makes 100 single key-value puts and
> then putAll with 100 keys/values)
> 5. The output if following:
> {noformat}
> C:\Java\jdk1.8.0_31\bin\java -Didea.launcher.port=7544
> "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
> Community Edition 13.1.4\bin" -Dfile.encoding=UTF-8 -classpath
> "C:\Java\jdk1.8.0_31\jre\lib\charsets.jar;C:\Java\jdk1.8.0_31\jre\lib\deploy.jar;C:\Java\jdk1.8.0_31\jre\lib\javaws.jar;C:\Java\jdk1.8.0_31\jre\lib\jce.jar;C:\Java\jdk1.8.0_31\jre\lib\jfr.jar;C:\Java\jdk1.8.0_31\jre\lib\jfxswt.jar;C:\Java\jdk1.8.0_31\jre\lib\jsse.jar;C:\Java\jdk1.8.0_31\jre\lib\management-agent.jar;C:\Java\jdk1.8.0_31\jre\lib\plugin.jar;C:\Java\jdk1.8.0_31\jre\lib\resources.jar;C:\Java\jdk1.8.0_31\jre\lib\rt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\access-bridge-64.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\cldrdata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\dnsns.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jaccess.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jfxrt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\localedata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\nashorn.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunec.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunjce_provider.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunmscapi.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunpkcs11.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\zipfs.jar;D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\examples\target\classes;D:\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-core\1.4.0-QASVK150901\ignite-core-1.4.0-QASVK150901.jar;D:\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-hibernate\1.4.0-QASVK150901\ignite-hibernate-1.4.0-QASVK150901.jar;D:\.m2\repository\org\hibernate\hibernate-core\4.2.6.Final\hibernate-core-4.2.6.Final.jar;D:\.m2\repository\antlr\antlr\2.7.7\antlr-2.7.7.jar;D:\.m2\repository\org\jboss\logging\jboss-logging\3.1.0.GA\jboss-logging-3.1.0.GA.jar;D:\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\.m2\repository\org\jboss\spec\javax\transaction\jboss-transaction-api_1.1_spec\1.0.1.Final\jboss-transaction-api_1.1_spec-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\javax\persistence\hibernate-jpa-2.0-api\1.0.1.Final\hibernate-jpa-2.0-api-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\common\hibernate-commons-annotations\4.0.2.Final\hibernate-commons-annotations-4.0.2.Final.jar;D:\.m2\repository\org\javassist\javassist\3.15.0-GA\javassist-3.15.0-GA.jar;D:\.m2\repository\org\apache\ignite\ignite-spring\1.4.0-QASVK150901\ignite-spring-1.4.0-QASVK150901.jar;D:\.m2\repository\org\springframework\spring-core\4.1.0.RELEASE\spring-core-4.1.0.RELEASE.jar;D:\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\.m2\repository\org\springframework\spring-aop\4.1.0.RELEASE\spring-aop-4.1.0.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar;D:\.m2\repository\org\springframework\spring-beans\4.1.0.RELEASE\spring-beans-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-context\4.1.0.RELEASE\spring-context-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-expression\4.1.0.RELEASE\spring-expression-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-tx\4.1.0.RELEASE\spring-tx-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-jdbc\4.1.0.RELEASE\spring-jdbc-4.1.0.RELEASE.jar;D:\.m2\repository\org\apache\ignite\ignite-log4j\1.4.0-QASVK150901\ignite-log4j-1.4.0-QASVK150901.jar;D:\.m2\repository\log4j\log4j\1.2.17\log4j-1.2.17.jar;D:\.m2\repository\org\apache\ignite\ignite-indexing\1.4.0-QASVK150901\ignite-indexing-1.4.0-QASVK150901.jar;D:\.m2\repository\commons-codec\commons-codec\1.6\commons-codec-1.6.jar;D:\.m2\repository\org\apache\lucene\lucene-core\3.5.0\lucene-core-3.5.0.jar;D:\.m2\repository\com\h2database\h2\1.3.175\h2-1.3.175.jar;D:\.m2\repository\org\apache\ignite\ignite-schedule\1.4.0-QASVK150901\ignite-schedule-1.4.0-QASVK150901.jar;D:\.m2\repository\it\sauronsoftware\cron4j\cron4j\2.2.5\cron4j-2.2.5.jar;D:\.m2\repository\com\google\
[jira] [Resolved] (IGNITE-1494) putAll after put doesn't update values
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov resolved IGNITE-1494.
---
Resolution: Not A Problem
It's related to logic of PRIMARY_SYNC and near cache: getall after putall can
return results before update comes on client
> putAll after put doesn't update values
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
> Attachments: CacheEvictExample.java, example-evict.xml
>
>
> 1. Copy example-evict.xml in examples/config directory
> 2. Copy CacheEvictExample in org.apache.ignite.examples.datagrid package
> 3. Start node bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheEvictExample (it makes 100 single key-value puts and
> then putAll with 100 keys/values)
> 5. The output if following:
> {noformat}
> C:\Java\jdk1.8.0_31\bin\java -Didea.launcher.port=7544
> "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
> Community Edition 13.1.4\bin" -Dfile.encoding=UTF-8 -classpath
> "C:\Java\jdk1.8.0_31\jre\lib\charsets.jar;C:\Java\jdk1.8.0_31\jre\lib\deploy.jar;C:\Java\jdk1.8.0_31\jre\lib\javaws.jar;C:\Java\jdk1.8.0_31\jre\lib\jce.jar;C:\Java\jdk1.8.0_31\jre\lib\jfr.jar;C:\Java\jdk1.8.0_31\jre\lib\jfxswt.jar;C:\Java\jdk1.8.0_31\jre\lib\jsse.jar;C:\Java\jdk1.8.0_31\jre\lib\management-agent.jar;C:\Java\jdk1.8.0_31\jre\lib\plugin.jar;C:\Java\jdk1.8.0_31\jre\lib\resources.jar;C:\Java\jdk1.8.0_31\jre\lib\rt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\access-bridge-64.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\cldrdata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\dnsns.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jaccess.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jfxrt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\localedata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\nashorn.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunec.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunjce_provider.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunmscapi.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunpkcs11.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\zipfs.jar;D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\examples\target\classes;D:\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-core\1.4.0-QASVK150901\ignite-core-1.4.0-QASVK150901.jar;D:\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-hibernate\1.4.0-QASVK150901\ignite-hibernate-1.4.0-QASVK150901.jar;D:\.m2\repository\org\hibernate\hibernate-core\4.2.6.Final\hibernate-core-4.2.6.Final.jar;D:\.m2\repository\antlr\antlr\2.7.7\antlr-2.7.7.jar;D:\.m2\repository\org\jboss\logging\jboss-logging\3.1.0.GA\jboss-logging-3.1.0.GA.jar;D:\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\.m2\repository\org\jboss\spec\javax\transaction\jboss-transaction-api_1.1_spec\1.0.1.Final\jboss-transaction-api_1.1_spec-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\javax\persistence\hibernate-jpa-2.0-api\1.0.1.Final\hibernate-jpa-2.0-api-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\common\hibernate-commons-annotations\4.0.2.Final\hibernate-commons-annotations-4.0.2.Final.jar;D:\.m2\repository\org\javassist\javassist\3.15.0-GA\javassist-3.15.0-GA.jar;D:\.m2\repository\org\apache\ignite\ignite-spring\1.4.0-QASVK150901\ignite-spring-1.4.0-QASVK150901.jar;D:\.m2\repository\org\springframework\spring-core\4.1.0.RELEASE\spring-core-4.1.0.RELEASE.jar;D:\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\.m2\repository\org\springframework\spring-aop\4.1.0.RELEASE\spring-aop-4.1.0.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar;D:\.m2\repository\org\springframework\spring-beans\4.1.0.RELEASE\spring-beans-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-context\4.1.0.RELEASE\spring-context-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-expression\4.1.0.RELEASE\spring-expression-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-tx\4.1.0.RELEASE\spring-tx-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-jdbc\4.1.0.RELEASE\spring-jdbc-4.1.0.RELEASE.jar;D:\.m2\repository\org\apache\ignite\ignite-log4j\1.4.0-QASVK150901\ignite-log4j-1.4.0-QASVK150901.jar;D:\.m2\repository\log4j\log4j\1.2.17\log4j-1.2.17.jar;D:\.m2\repository\org\apache\ignite\ignite-indexing\1.4.0-QASVK150901\ignite-indexing-1.4.0-QASVK150901.jar;D:\.m2\repository\commons-codec\commons-codec\1.6\commons-codec-1.6.jar;D:\.m2\repository\org\apache\lucene\lucene-core\3.5.0\lucene-core-3.5.0.jar;D:\.m2\repository\com\h2database\h2\1.3.175\h2-1.3.175.jar;D:\.m2\repository\org\apache\ignite\ignite-schedule
[jira] [Updated] (IGNITE-1496) Platform .Net: Add .Net examples
[ https://issues.apache.org/jira/browse/IGNITE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1496: Description: Include example tests > Platform .Net: Add .Net examples > > > Key: IGNITE-1496 > URL: https://issues.apache.org/jira/browse/IGNITE-1496 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > > Include example tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1496) Platform .Net: Add .Net examples
[ https://issues.apache.org/jira/browse/IGNITE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1496: Description: * Create separate Examples solution (with 2 projects - main and dll) * Add these projects to main Ignite solution * Include example tests into Apache.Ignite.Core.Tests * Fix config files and documentation, make sure GridGain in not mentioned anywhere was:Include example tests > Platform .Net: Add .Net examples > > > Key: IGNITE-1496 > URL: https://issues.apache.org/jira/browse/IGNITE-1496 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > > * Create separate Examples solution (with 2 projects - main and dll) > * Add these projects to main Ignite solution > * Include example tests into Apache.Ignite.Core.Tests > * Fix config files and documentation, make sure GridGain in not mentioned > anywhere -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1239) Cache partition iterator throws exception when concurrent rebalancing is running
[
https://issues.apache.org/jira/browse/IGNITE-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov resolved IGNITE-1239.
--
Assignee: (was: Alexey Goncharuk)
> Cache partition iterator throws exception when concurrent rebalancing is
> running
>
>
> Key: IGNITE-1239
> URL: https://issues.apache.org/jira/browse/IGNITE-1239
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Alexey Goncharuk
> Fix For: ignite-1.4
>
> Attachments: ignite-1239-2.patch, ignite-1239.patch, ignite-1239.patch
>
>
> I observed this exception when IgniteRDD was iterating over partition and two
> new nodes have joined:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN,
> clsName=null, clause=null,
> filter=org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1@6490c94c,
> part=138, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=10,
> maxTime=10, avgTime=10.0, execs=1, fails=1, executed=true], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null,
> keepPortable=false, subjId=9cdc9751-c6ec-43eb-968a-e941f2a1a8cd, taskHash=0],
> rdc=null, trans=null]
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:245)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:303)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:156)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter
> [type=SCAN, clsName=null, clause=null,
> filter=org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1@6490c94c,
> part=138, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0,
> maxTime=0, avgTime=0.0, execs=0, fails=0, executed=false], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null,
> keepPortable=false, subjId=9cdc9751-c6ec-43eb-968a-e941f2a1a8cd, taskHash=0],
> rdc=null, trans=null], nodeId=963d0e35-7805-4b6d-8d64-22cce84e35f2]
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:370)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:377)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:44)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:74)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:72)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:534)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1026)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2256)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:946)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:60)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:915)
> ... 3 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Partition can't be
> reserved
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6808)
> {code}
> The issue is that query request was sent on a backup node and by the time
> request has arrived, the partition was already evicted, which resulted in
> "Partition cannot be reserved" exception. We should automatically retry if
> this exception is encountered.
> I believe we have logic that retries, but it looks like there is a bug in
> that logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1239) Cache partition iterator throws exception when concurrent rebalancing is running
[
https://issues.apache.org/jira/browse/IGNITE-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790522#comment-14790522
]
Semen Boikov commented on IGNITE-1239:
--
I reverted change in IgniteCache#localPeek since it caused a lot of tests
failures, instead I use peekEx in scan iterator code. Also I removed internal
future listener in CacheQueryFallbackFuture since this listener and
'retryIfPossible' method retried the same query twice (now
CacheQueryFallbackFuture itself is not completed its 'get' method is never
called).
Merged to 1.4.
> Cache partition iterator throws exception when concurrent rebalancing is
> running
>
>
> Key: IGNITE-1239
> URL: https://issues.apache.org/jira/browse/IGNITE-1239
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: ignite-1.4
>
> Attachments: ignite-1239-2.patch, ignite-1239.patch, ignite-1239.patch
>
>
> I observed this exception when IgniteRDD was iterating over partition and two
> new nodes have joined:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN,
> clsName=null, clause=null,
> filter=org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1@6490c94c,
> part=138, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=10,
> maxTime=10, avgTime=10.0, execs=1, fails=1, executed=true], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null,
> keepPortable=false, subjId=9cdc9751-c6ec-43eb-968a-e941f2a1a8cd, taskHash=0],
> rdc=null, trans=null]
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:245)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:303)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:156)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter
> [type=SCAN, clsName=null, clause=null,
> filter=org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1@6490c94c,
> part=138, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0,
> maxTime=0, avgTime=0.0, execs=0, fails=0, executed=false], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null,
> keepPortable=false, subjId=9cdc9751-c6ec-43eb-968a-e941f2a1a8cd, taskHash=0],
> rdc=null, trans=null], nodeId=963d0e35-7805-4b6d-8d64-22cce84e35f2]
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:370)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:377)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:44)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:74)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:72)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:534)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1026)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2256)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:946)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:60)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:915)
> ... 3 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Partition can't be
> reserved
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6808)
> {code}
> The issue is that query request was sent on a backup node and by the time
[jira] [Closed] (IGNITE-1239) Cache partition iterator throws exception when concurrent rebalancing is running
[
https://issues.apache.org/jira/browse/IGNITE-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov closed IGNITE-1239.
> Cache partition iterator throws exception when concurrent rebalancing is
> running
>
>
> Key: IGNITE-1239
> URL: https://issues.apache.org/jira/browse/IGNITE-1239
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Alexey Goncharuk
> Fix For: ignite-1.4
>
> Attachments: ignite-1239-2.patch, ignite-1239.patch, ignite-1239.patch
>
>
> I observed this exception when IgniteRDD was iterating over partition and two
> new nodes have joined:
> {code}
> Caused by: class org.apache.ignite.IgniteCheckedException: Query execution
> failed: GridCacheQueryBean [qry=GridCacheQueryAdapter [type=SCAN,
> clsName=null, clause=null,
> filter=org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1@6490c94c,
> part=138, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=10,
> maxTime=10, avgTime=10.0, execs=1, fails=1, executed=true], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null,
> keepPortable=false, subjId=9cdc9751-c6ec-43eb-968a-e941f2a1a8cd, taskHash=0],
> rdc=null, trans=null]
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.checkError(GridCacheQueryFutureAdapter.java:245)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.internalIterator(GridCacheQueryFutureAdapter.java:303)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:156)
> ... 17 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to execute
> query on node [query=GridCacheQueryBean [qry=GridCacheQueryAdapter
> [type=SCAN, clsName=null, clause=null,
> filter=org.apache.ignite.internal.processors.cache.IgniteCacheProxy$1@6490c94c,
> part=138, incMeta=false, metrics=GridCacheQueryMetricsAdapter [minTime=0,
> maxTime=0, avgTime=0.0, execs=0, fails=0, executed=false], pageSize=1024,
> timeout=0, keepAll=true, incBackups=false, dedup=false, prj=null,
> keepPortable=false, subjId=9cdc9751-c6ec-43eb-968a-e941f2a1a8cd, taskHash=0],
> rdc=null, trans=null], nodeId=963d0e35-7805-4b6d-8d64-22cce84e35f2]
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.onPage(GridCacheQueryFutureAdapter.java:370)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryResponse(GridCacheDistributedQueryManager.java:377)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.access$000(GridCacheDistributedQueryManager.java:44)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:74)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$1.apply(GridCacheDistributedQueryManager.java:72)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:534)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:240)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1026)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2256)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:946)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:60)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:915)
> ... 3 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Partition can't be
> reserved
> at
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6808)
> {code}
> The issue is that query request was sent on a backup node and by the time
> request has arrived, the partition was already evicted, which resulted in
> "Partition cannot be reserved" exception. We should automatically retry if
> this exception is encountered.
> I believe we have logic that retries, but it looks like there is a bug in
> that logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1452) OptimizedMarshaller.unmarshal hangs in IgniteCacheQueryNodeRestartSelfTest2
[
https://issues.apache.org/jira/browse/IGNITE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov updated IGNITE-1452:
--
Fix Version/s: (was: ignite-1.5)
ignite-1.4
> OptimizedMarshaller.unmarshal hangs in IgniteCacheQueryNodeRestartSelfTest2
> ---
>
> Key: IGNITE-1452
> URL: https://issues.apache.org/jira/browse/IGNITE-1452
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Blocker
> Fix For: ignite-1.4
>
> Attachments: Ignite_Tests_Ignite_Queries_3147.log.zip
>
>
> Observed on TC hang in IgniteCacheQueryNodeRestartSelfTest2, one thread hangs
> inside 'unmarshal' (full log is attached):
> {noformat}
> [01:36:54]W: [org.apache.ignite:ignite-indexing] Thread
> [name="ignite-#58451%sys-near.IgniteCacheQueryNodeRestartSelfTest25%",
> id=70744, state=WAITING, blockCnt=0, waitCnt=4]
> [01:36:54]W: [org.apache.ignite:ignite-indexing] Lock
> [object=o.a.i.i.processors.cache.distributed.dht.GridPartitionedGetFuture@5829204d,
> ownerName=null, ownerId=-1]
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> sun.misc.Unsafe.park(Native Method)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCacheAdapter.getTopologySafe(GridCacheAdapter.java:1345)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.MarshallerContextImpl.className(MarshallerContextImpl.java:151)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:256)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:309)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> java.io.ObjectInputStream.readObject(ObjectInputStream.java:364)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller.java:240)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cacheobject.IgniteCacheObjectProcessorImpl.unmarshal(IgniteCacheObjectProcessorImpl.java:101)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.portable.CacheObjectPortableProcessorImpl.unmarshal(CacheObjectPortableProcessorImpl.java:730)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.CacheObjectImpl.finishUnmarshal(CacheObjectImpl.java:104)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCacheEntryInfo.unmarshal(GridCacheEntryInfo.java:411)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplyMessage.finishUnmarshal(GridDhtPartitionSupplyMessage.java:262)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1021)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:262)
> [01:36:54]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
> [01:36:54
[jira] [Updated] (IGNITE-1497) Support CPU architectures different from x86/x64
[
https://issues.apache.org/jira/browse/IGNITE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1497:
Affects Version/s: ignite-1.4
> Support CPU architectures different from x86/x64
>
>
> Key: IGNITE-1497
> URL: https://issues.apache.org/jira/browse/IGNITE-1497
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>
> Ignite widely uses {{Unsafe}} instance throughout the code and the usage is
> mostly based on the fact that the platform will be running on a little-endian
> x86/x64 machine.
> As an example the following classes work with short, int, long and other type
> values bigger than 1 byte in size without taking CPU endiannes into account:
> - {{DirectByteBufferStream}};
> - {{PortableObjectOffheapImpl}};
> - {{GridUnsafeDataOutput}};
> - etc.
> This leads to VM crashes on different CPU architectures:
> - IGNITE-1493;
> -
> http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
> All the classes that use {{Unsafe}} in Ignite have to be revisited and
> modified in a way to support different CPU architectures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1497) Support CPU architectures different from x86/x64
Denis Magda created IGNITE-1497:
---
Summary: Support CPU architectures different from x86/x64
Key: IGNITE-1497
URL: https://issues.apache.org/jira/browse/IGNITE-1497
Project: Ignite
Issue Type: Improvement
Components: general
Reporter: Denis Magda
Ignite widely uses {{Unsafe}} instance throughout the code and the usage is
mostly based on the fact that the platform will be running on a little-endian
x86/x64 machine.
As an example the following classes work with short, int, long and other type
values bigger than 1 byte in size without taking CPU endiannes into account:
- {{DirectByteBufferStream}};
- {{PortableObjectOffheapImpl}};
- {{GridUnsafeDataOutput}};
- etc.
This leads to VM crashes on different CPU architectures:
- IGNITE-1493;
-
http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
All the classes that use {{Unsafe}} in Ignite have to be revisited and modified
in a way to support different CPU architectures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1016) Add excludeNeighbors and backupFilter to FairAffinityFunction
[
https://issues.apache.org/jira/browse/IGNITE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura reassigned IGNITE-1016:
---
Assignee: Alexey Goncharuk (was: Andrey Gura)
TC looks good. Please, merge.
> Add excludeNeighbors and backupFilter to FairAffinityFunction
> -
>
> Key: IGNITE-1016
> URL: https://issues.apache.org/jira/browse/IGNITE-1016
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Alexey Goncharuk
> Labels: Usability
> Fix For: ignite-1.5
>
> Attachments: ignite-1016.patch, ignite-1016.patch
>
>
> These properties are currently available only for
> {{RendezvousAffinityFunction}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1493) Fatal exception is thrown during queue instantiation when using Ignite with an HP-UX machine.
[
https://issues.apache.org/jira/browse/IGNITE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790790#comment-14790790
]
Nicholas Dzwill commented on IGNITE-1493:
-
Thanks Vladimir.
I have read through the links you posted and am wondering if there is any
work-around if we want to use the Oracle version of java on these machines. A
configuration or an Ignite code change that is in the works that would
alleviate this issue would be great.
Thanks again for your help.
> Fatal exception is thrown during queue instantiation when using Ignite with
> an HP-UX machine.
> -
>
> Key: IGNITE-1493
> URL: https://issues.apache.org/jira/browse/IGNITE-1493
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Environment: * HP-UX B.11.31 IA64W machine
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
>Reporter: Nicholas Dzwill
>Priority: Blocker
> Attachments: ErrorLog.txt, server.log
>
>
> A fatal exception is thrown during queue instantiation when using an HP-UX
> B.11.31 IA64W machine.
> The environment is as follows:
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
> The error logged is as follows:
> * Current thread (01ab2800): JavaThread "main" [_thread_in_vm, id=23,
> lwp_id=3525570, stack(4e501000,4e601000)]
> * siginfo:si_signo=SIGBUS: si_errno=0, si_code=1 (BUS_ADRALN),
> si_addr=5e038d15
>
> The exception above means there is an "invalid address alignment" (writing to
> an odd memory location) when calling the following method:
> * Class: org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream
> * Method:
> {code:borderStyle=solid}
>/** {@inheritDoc} */
> @Override public void writeInt(int v) throws IOException {
> requestFreeSize(4);
> UNSAFE.putInt(bytes, byteArrOff + off, v); // byteArrOff + off =
> 17 when this exception is thrown
> onWrite(4);
> }
> {code}
>
> Basic setup - Ignite is configured with spring and pushed to the constructor
> of a class. That class uses this instance of Ignite to instantiate an
> IgniteQueue as follows:
> {code:borderStyle=solid}
> CollectionConfiguration configuration = new CollectionConfiguration();
> configuration.setCollocated(true);
> IgniteQueue queue = ignite.queue("queue", 0, configuration);
> {code}
>
> Partial stack:
> * Instantiating the queue calls:
> **
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.compatibleConfiguration()
>
> * Which in turn calls:
> ** org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke()
> * Leading to the fatal error when calling:
> **
> org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeInt()
> The error log has been attached with the stack trace of the error. The
> server log is also attached. We are running Ignite in a variety of
> environments and this issue only appears to exist in this specific
> environment and is consistently hit in the same place with no apparent
> work-around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790906#comment-14790906 ] Ivan Veselovsky commented on IGNITE-586: We revealed that the primary cause of the problem is that some tests bring IGFS into incorrect state: some entries in meta & data caches exist, but cannot be found by treversing the file system tree. The fact is that at least renames cause such situation. The problem is localized tightly enough. This happens at least in situation when a file cannot be moved to a destination folder where a file with the same short name already exists: in such situation the source file "disappears" from the file system, while still persists in meta cache. > [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC. > - > > Key: IGNITE-586 > URL: https://issues.apache.org/jira/browse/IGNITE-586 > Project: Ignite > Issue Type: Bug > Components: hadoop >Reporter: Artem Shutak >Assignee: Ivan Veselovsky > Labels: failedtest > Fix For: ignite-1.5 > > > The problem is that format() doesn't clean all previously written data. > See GG-8578 (the issue was closed, but stay reproducible) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1493) Fatal exception is thrown during queue instantiation when using Ignite with an HP-UX machine.
[
https://issues.apache.org/jira/browse/IGNITE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790939#comment-14790939
]
Vladimir Ozerov commented on IGNITE-1493:
-
Nicholas,
Looks like we have two places where discussion happens: here and on SO
(http://stackoverflow.com/questions/32510157/apache-ignite-bus-adraln-error-during-installation-of-cache),
where I asked for several debug steps to help us understand the issue. To
avoid miscommunication, lets continue discussion here.
Crash occurs inside OptimizedMarshaller. The easiest workaround which comes to
my mind is to replace it with another one, e.g. JdkMarshaller which relies on
standard Java serialization mechanism and is more resource consuming. Insert
the following code snippet inside "IgniteConfiguration" bean in your XML
configuration:
{code}
{code}
To provide a fix for OptimizedMarshaller we need to better understand what is
going on. Could you please provide the following additional information if
possible:
1) "GridUnsafeDataOutput.bytes" array length at the moment of crash. From the
crash report I see that there is some array of length 4096 on the stack. Most
probably this is GridUnsafeDataOutput.bytes, but we need to be 100% sure.
2) Run the following program on affected machine and provide the output. This
way we will know some important runtime parameters of your JVM.
{code}
public static void main(String[] args) {
sun.misc.Unsafe unsafe =
org.apache.ignite.internal.util.GridUnsafe.unsafe();
System.out.println(unsafe.arrayBaseOffset(byte[].class));
System.out.println(unsafe.arrayIndexScale(byte[].class));
}
{code}
> Fatal exception is thrown during queue instantiation when using Ignite with
> an HP-UX machine.
> -
>
> Key: IGNITE-1493
> URL: https://issues.apache.org/jira/browse/IGNITE-1493
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Environment: * HP-UX B.11.31 IA64W machine
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
>Reporter: Nicholas Dzwill
>Priority: Blocker
> Attachments: ErrorLog.txt, server.log
>
>
> A fatal exception is thrown during queue instantiation when using an HP-UX
> B.11.31 IA64W machine.
> The environment is as follows:
> * JRE version: Java(TM) SE Runtime Environment (7.0) (build
> 1.7.0.14-jinteg_2015_08_07_03_06-b00)
> * Java VM: Java HotSpot(TM) Server VM (24.85-b05-jre1.7.0.14-rc1 mixed mode
> hp-ux-ia64 )
> The error logged is as follows:
> * Current thread (01ab2800): JavaThread "main" [_thread_in_vm, id=23,
> lwp_id=3525570, stack(4e501000,4e601000)]
> * siginfo:si_signo=SIGBUS: si_errno=0, si_code=1 (BUS_ADRALN),
> si_addr=5e038d15
>
> The exception above means there is an "invalid address alignment" (writing to
> an odd memory location) when calling the following method:
> * Class: org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream
> * Method:
> {code:borderStyle=solid}
>/** {@inheritDoc} */
> @Override public void writeInt(int v) throws IOException {
> requestFreeSize(4);
> UNSAFE.putInt(bytes, byteArrOff + off, v); // byteArrOff + off =
> 17 when this exception is thrown
> onWrite(4);
> }
> {code}
>
> Basic setup - Ignite is configured with spring and pushed to the constructor
> of a class. That class uses this instance of Ignite to instantiate an
> IgniteQueue as follows:
> {code:borderStyle=solid}
> CollectionConfiguration configuration = new CollectionConfiguration();
> configuration.setCollocated(true);
> IgniteQueue queue = ignite.queue("queue", 0, configuration);
> {code}
>
> Partial stack:
> * Instantiating the queue calls:
> **
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.compatibleConfiguration()
>
> * Which in turn calls:
> ** org.apache.ignite.internal.processors.cache.GridCacheAdapter.invoke()
> * Leading to the fatal error when calling:
> **
> org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeInt()
> The error log has been attached with the stack trace of the error. The
> server log is also attached. We are running Ignite in a variety of
> environments and this issue only appears to exist in this specific
> environment and is consistently hit in the same place with no apparent
> work-around.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Attachment: (was: CacheEvictExample.java)
> putAll after put doesn't update values
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
> Attachments: example-evict.xml
>
>
> 1. Copy example-evict.xml in examples/config directory
> 2. Copy CacheEvictExample in org.apache.ignite.examples.datagrid package
> 3. Start node bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheEvictExample (it makes 100 single key-value puts and
> then putAll with 100 keys/values)
> 5. The output if following:
> {noformat}
> C:\Java\jdk1.8.0_31\bin\java -Didea.launcher.port=7544
> "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
> Community Edition 13.1.4\bin" -Dfile.encoding=UTF-8 -classpath
> "C:\Java\jdk1.8.0_31\jre\lib\charsets.jar;C:\Java\jdk1.8.0_31\jre\lib\deploy.jar;C:\Java\jdk1.8.0_31\jre\lib\javaws.jar;C:\Java\jdk1.8.0_31\jre\lib\jce.jar;C:\Java\jdk1.8.0_31\jre\lib\jfr.jar;C:\Java\jdk1.8.0_31\jre\lib\jfxswt.jar;C:\Java\jdk1.8.0_31\jre\lib\jsse.jar;C:\Java\jdk1.8.0_31\jre\lib\management-agent.jar;C:\Java\jdk1.8.0_31\jre\lib\plugin.jar;C:\Java\jdk1.8.0_31\jre\lib\resources.jar;C:\Java\jdk1.8.0_31\jre\lib\rt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\access-bridge-64.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\cldrdata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\dnsns.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jaccess.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jfxrt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\localedata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\nashorn.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunec.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunjce_provider.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunmscapi.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunpkcs11.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\zipfs.jar;D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\examples\target\classes;D:\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-core\1.4.0-QASVK150901\ignite-core-1.4.0-QASVK150901.jar;D:\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-hibernate\1.4.0-QASVK150901\ignite-hibernate-1.4.0-QASVK150901.jar;D:\.m2\repository\org\hibernate\hibernate-core\4.2.6.Final\hibernate-core-4.2.6.Final.jar;D:\.m2\repository\antlr\antlr\2.7.7\antlr-2.7.7.jar;D:\.m2\repository\org\jboss\logging\jboss-logging\3.1.0.GA\jboss-logging-3.1.0.GA.jar;D:\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\.m2\repository\org\jboss\spec\javax\transaction\jboss-transaction-api_1.1_spec\1.0.1.Final\jboss-transaction-api_1.1_spec-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\javax\persistence\hibernate-jpa-2.0-api\1.0.1.Final\hibernate-jpa-2.0-api-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\common\hibernate-commons-annotations\4.0.2.Final\hibernate-commons-annotations-4.0.2.Final.jar;D:\.m2\repository\org\javassist\javassist\3.15.0-GA\javassist-3.15.0-GA.jar;D:\.m2\repository\org\apache\ignite\ignite-spring\1.4.0-QASVK150901\ignite-spring-1.4.0-QASVK150901.jar;D:\.m2\repository\org\springframework\spring-core\4.1.0.RELEASE\spring-core-4.1.0.RELEASE.jar;D:\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\.m2\repository\org\springframework\spring-aop\4.1.0.RELEASE\spring-aop-4.1.0.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar;D:\.m2\repository\org\springframework\spring-beans\4.1.0.RELEASE\spring-beans-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-context\4.1.0.RELEASE\spring-context-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-expression\4.1.0.RELEASE\spring-expression-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-tx\4.1.0.RELEASE\spring-tx-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-jdbc\4.1.0.RELEASE\spring-jdbc-4.1.0.RELEASE.jar;D:\.m2\repository\org\apache\ignite\ignite-log4j\1.4.0-QASVK150901\ignite-log4j-1.4.0-QASVK150901.jar;D:\.m2\repository\log4j\log4j\1.2.17\log4j-1.2.17.jar;D:\.m2\repository\org\apache\ignite\ignite-indexing\1.4.0-QASVK150901\ignite-indexing-1.4.0-QASVK150901.jar;D:\.m2\repository\commons-codec\commons-codec\1.6\commons-codec-1.6.jar;D:\.m2\repository\org\apache\lucene\lucene-core\3.5.0\lucene-core-3.5.0.jar;D:\.m2\repository\com\h2database\h2\1.3.175\h2-1.3.175.jar;D:\.m2\repository\org\apache\ignite\ignite-schedule\1.4.0-QASVK150901\ignite-schedule-1.4.0-QASVK150901.jar;D:\.m2\repository\it\sauronsoftware\cron4j\cron4j\2.2.5\cron4j-2.2.5.jar;D
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Attachment: (was: example-evict.xml)
> putAll after put doesn't update values
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
>
> 1. Copy example-evict.xml in examples/config directory
> 2. Copy CacheEvictExample in org.apache.ignite.examples.datagrid package
> 3. Start node bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheEvictExample (it makes 100 single key-value puts and
> then putAll with 100 keys/values)
> 5. The output if following:
> {noformat}
> C:\Java\jdk1.8.0_31\bin\java -Didea.launcher.port=7544
> "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
> Community Edition 13.1.4\bin" -Dfile.encoding=UTF-8 -classpath
> "C:\Java\jdk1.8.0_31\jre\lib\charsets.jar;C:\Java\jdk1.8.0_31\jre\lib\deploy.jar;C:\Java\jdk1.8.0_31\jre\lib\javaws.jar;C:\Java\jdk1.8.0_31\jre\lib\jce.jar;C:\Java\jdk1.8.0_31\jre\lib\jfr.jar;C:\Java\jdk1.8.0_31\jre\lib\jfxswt.jar;C:\Java\jdk1.8.0_31\jre\lib\jsse.jar;C:\Java\jdk1.8.0_31\jre\lib\management-agent.jar;C:\Java\jdk1.8.0_31\jre\lib\plugin.jar;C:\Java\jdk1.8.0_31\jre\lib\resources.jar;C:\Java\jdk1.8.0_31\jre\lib\rt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\access-bridge-64.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\cldrdata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\dnsns.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jaccess.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jfxrt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\localedata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\nashorn.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunec.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunjce_provider.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunmscapi.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunpkcs11.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\zipfs.jar;D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\examples\target\classes;D:\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-core\1.4.0-QASVK150901\ignite-core-1.4.0-QASVK150901.jar;D:\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-hibernate\1.4.0-QASVK150901\ignite-hibernate-1.4.0-QASVK150901.jar;D:\.m2\repository\org\hibernate\hibernate-core\4.2.6.Final\hibernate-core-4.2.6.Final.jar;D:\.m2\repository\antlr\antlr\2.7.7\antlr-2.7.7.jar;D:\.m2\repository\org\jboss\logging\jboss-logging\3.1.0.GA\jboss-logging-3.1.0.GA.jar;D:\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\.m2\repository\org\jboss\spec\javax\transaction\jboss-transaction-api_1.1_spec\1.0.1.Final\jboss-transaction-api_1.1_spec-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\javax\persistence\hibernate-jpa-2.0-api\1.0.1.Final\hibernate-jpa-2.0-api-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\common\hibernate-commons-annotations\4.0.2.Final\hibernate-commons-annotations-4.0.2.Final.jar;D:\.m2\repository\org\javassist\javassist\3.15.0-GA\javassist-3.15.0-GA.jar;D:\.m2\repository\org\apache\ignite\ignite-spring\1.4.0-QASVK150901\ignite-spring-1.4.0-QASVK150901.jar;D:\.m2\repository\org\springframework\spring-core\4.1.0.RELEASE\spring-core-4.1.0.RELEASE.jar;D:\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\.m2\repository\org\springframework\spring-aop\4.1.0.RELEASE\spring-aop-4.1.0.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar;D:\.m2\repository\org\springframework\spring-beans\4.1.0.RELEASE\spring-beans-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-context\4.1.0.RELEASE\spring-context-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-expression\4.1.0.RELEASE\spring-expression-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-tx\4.1.0.RELEASE\spring-tx-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-jdbc\4.1.0.RELEASE\spring-jdbc-4.1.0.RELEASE.jar;D:\.m2\repository\org\apache\ignite\ignite-log4j\1.4.0-QASVK150901\ignite-log4j-1.4.0-QASVK150901.jar;D:\.m2\repository\log4j\log4j\1.2.17\log4j-1.2.17.jar;D:\.m2\repository\org\apache\ignite\ignite-indexing\1.4.0-QASVK150901\ignite-indexing-1.4.0-QASVK150901.jar;D:\.m2\repository\commons-codec\commons-codec\1.6\commons-codec-1.6.jar;D:\.m2\repository\org\apache\lucene\lucene-core\3.5.0\lucene-core-3.5.0.jar;D:\.m2\repository\com\h2database\h2\1.3.175\h2-1.3.175.jar;D:\.m2\repository\org\apache\ignite\ignite-schedule\1.4.0-QASVK150901\ignite-schedule-1.4.0-QASVK150901.jar;D:\.m2\repository\it\sauronsoftware\cron4j\cron4j\2.2.5\cron4j-2.2.5.jar;D:\.m2\repository\com\google\code\simple-spring-m
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Summary: putAll after put doesn't update values for some cache
configurations (was: putAll after put doesn't update values)
> putAll after put doesn't update values for some cache configurations
>
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
>
> 1. Copy example-evict.xml in examples/config directory
> 2. Copy CacheEvictExample in org.apache.ignite.examples.datagrid package
> 3. Start node bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheEvictExample (it makes 100 single key-value puts and
> then putAll with 100 keys/values)
> 5. The output if following:
> {noformat}
> C:\Java\jdk1.8.0_31\bin\java -Didea.launcher.port=7544
> "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
> Community Edition 13.1.4\bin" -Dfile.encoding=UTF-8 -classpath
> "C:\Java\jdk1.8.0_31\jre\lib\charsets.jar;C:\Java\jdk1.8.0_31\jre\lib\deploy.jar;C:\Java\jdk1.8.0_31\jre\lib\javaws.jar;C:\Java\jdk1.8.0_31\jre\lib\jce.jar;C:\Java\jdk1.8.0_31\jre\lib\jfr.jar;C:\Java\jdk1.8.0_31\jre\lib\jfxswt.jar;C:\Java\jdk1.8.0_31\jre\lib\jsse.jar;C:\Java\jdk1.8.0_31\jre\lib\management-agent.jar;C:\Java\jdk1.8.0_31\jre\lib\plugin.jar;C:\Java\jdk1.8.0_31\jre\lib\resources.jar;C:\Java\jdk1.8.0_31\jre\lib\rt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\access-bridge-64.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\cldrdata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\dnsns.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jaccess.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jfxrt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\localedata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\nashorn.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunec.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunjce_provider.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunmscapi.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunpkcs11.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\zipfs.jar;D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\examples\target\classes;D:\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-core\1.4.0-QASVK150901\ignite-core-1.4.0-QASVK150901.jar;D:\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-hibernate\1.4.0-QASVK150901\ignite-hibernate-1.4.0-QASVK150901.jar;D:\.m2\repository\org\hibernate\hibernate-core\4.2.6.Final\hibernate-core-4.2.6.Final.jar;D:\.m2\repository\antlr\antlr\2.7.7\antlr-2.7.7.jar;D:\.m2\repository\org\jboss\logging\jboss-logging\3.1.0.GA\jboss-logging-3.1.0.GA.jar;D:\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;D:\.m2\repository\org\jboss\spec\javax\transaction\jboss-transaction-api_1.1_spec\1.0.1.Final\jboss-transaction-api_1.1_spec-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\javax\persistence\hibernate-jpa-2.0-api\1.0.1.Final\hibernate-jpa-2.0-api-1.0.1.Final.jar;D:\.m2\repository\org\hibernate\common\hibernate-commons-annotations\4.0.2.Final\hibernate-commons-annotations-4.0.2.Final.jar;D:\.m2\repository\org\javassist\javassist\3.15.0-GA\javassist-3.15.0-GA.jar;D:\.m2\repository\org\apache\ignite\ignite-spring\1.4.0-QASVK150901\ignite-spring-1.4.0-QASVK150901.jar;D:\.m2\repository\org\springframework\spring-core\4.1.0.RELEASE\spring-core-4.1.0.RELEASE.jar;D:\.m2\repository\commons-logging\commons-logging\1.1.1\commons-logging-1.1.1.jar;D:\.m2\repository\org\springframework\spring-aop\4.1.0.RELEASE\spring-aop-4.1.0.RELEASE.jar;D:\.m2\repository\aopalliance\aopalliance\1.0\aopalliance-1.0.jar;D:\.m2\repository\org\springframework\spring-beans\4.1.0.RELEASE\spring-beans-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-context\4.1.0.RELEASE\spring-context-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-expression\4.1.0.RELEASE\spring-expression-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-tx\4.1.0.RELEASE\spring-tx-4.1.0.RELEASE.jar;D:\.m2\repository\org\springframework\spring-jdbc\4.1.0.RELEASE\spring-jdbc-4.1.0.RELEASE.jar;D:\.m2\repository\org\apache\ignite\ignite-log4j\1.4.0-QASVK150901\ignite-log4j-1.4.0-QASVK150901.jar;D:\.m2\repository\log4j\log4j\1.2.17\log4j-1.2.17.jar;D:\.m2\repository\org\apache\ignite\ignite-indexing\1.4.0-QASVK150901\ignite-indexing-1.4.0-QASVK150901.jar;D:\.m2\repository\commons-codec\commons-codec\1.6\commons-codec-1.6.jar;D:\.m2\repository\org\apache\lucene\lucene-core\3.5.0\lucene-core-3.5.0.jar;D:\.m2\repository\com\h2database\h2\1.3.175\h2-1.3.175.jar;D:\.m2\repository\org\apache\ignite\ignite-schedule\1.4.0-QASVK150901\ignite-schedule
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Description:
1. Copy grid_config_01.xml in examples/config directory (it contains 25
FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
4. Build and run CacheTestExample (it makes 1000 single key-value puts and then
1000 gets)
5. The normal output should be following:
{noformat}
[22:55:58]__
[22:55:58] / _/ ___/ |/ / _/_ __/ __/
[22:55:58] _/ // (7 7// / / / / _/
[22:55:58] /___/\___/_/|_/___/ /_/ /___/
[22:55:58]
[22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
[22:55:58] 2015 Copyright(C) Apache Software Foundation
[22:55:58]
[22:55:58] Ignite documentation: http://ignite.apache.org
[22:55:58]
[22:55:58] Quiet mode.
[22:55:58] ^-- Logging to file
'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
[22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[22:55:58]
[22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[22:56:00] Configured plugins:
[22:56:00] ^-- None
[22:56:00]
[22:56:01] Security status [authentication=off, communication encryption=off]
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_4
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_1
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_10
[22:56:04] Performance suggestions for grid (fix if possible)
[22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[22:56:04] ^-- Disable fully synchronous writes (set
'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
[22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
[22:56:04]
[22:56:04] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[22:56:04]
[22:56:04] Ignite node started OK (id=faa18f29)
[22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
>>>cache_1
Put for 1000
Get for 1000
>>>cache_2
Put for 1000
[23:03:21] New version is available at
http://www.gridgain.com/download/editions: 1.3.3
Get for 1000
>>>cache_3
Put for 1000
Get for 1000
>>>cache_4
Put for 1000
Get for 1000
...
{noformat}
But for some caches I got:
{noformat}
>>>cache_18
Put for 1000
Get for 1000
Wrong value found [key=0, val=null]
Wrong value found [key=1, val=null]
Wrong value found [key=2, val=null]
Wrong value found [key=3, val=null]
Wrong value found [key=4, val=null]
Wrong value found [key=5, val=null]
Wrong value found [key=6, val=null]
Wrong value found [key=7, val=null]
Wrong value found [key=8, val=null]
Wrong value found [key=9, val=null]
...
{noformat}
was:
1. Copy example-evict.xml in examples/config directory
2. Copy CacheEvictExample in org.apache.ignite.examples.datagrid package
3. Start node bin/ignite.sh examples/config/example-evict.xml
4. Build and run CacheEvictExample (it makes 100 single key-value puts and then
putAll with 100 keys/values)
5. The output if following:
{noformat}
C:\Java\jdk1.8.0_31\bin\java -Didea.launcher.port=7544
"-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA
Community Edition 13.1.4\bin" -Dfile.encoding=UTF-8 -classpath
"C:\Java\jdk1.8.0_31\jre\lib\charsets.jar;C:\Java\jdk1.8.0_31\jre\lib\deploy.jar;C:\Java\jdk1.8.0_31\jre\lib\javaws.jar;C:\Java\jdk1.8.0_31\jre\lib\jce.jar;C:\Java\jdk1.8.0_31\jre\lib\jfr.jar;C:\Java\jdk1.8.0_31\jre\lib\jfxswt.jar;C:\Java\jdk1.8.0_31\jre\lib\jsse.jar;C:\Java\jdk1.8.0_31\jre\lib\management-agent.jar;C:\Java\jdk1.8.0_31\jre\lib\plugin.jar;C:\Java\jdk1.8.0_31\jre\lib\resources.jar;C:\Java\jdk1.8.0_31\jre\lib\rt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\access-bridge-64.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\cldrdata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\dnsns.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jaccess.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\jfxrt.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\localedata.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\nashorn.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunec.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunjce_provider.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunmscapi.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\sunpkcs11.jar;C:\Java\jdk1.8.0_31\jre\lib\ext\zipfs.jar;D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\examples\target\classes;D:\.m2\repository\javax\cache\cache-api\1.0.0\cache-api-1.0.0.jar;D:\.m2\repository\org\apache\ignite\ignite-core\1.4.0-QASVK150901\ignite-core-1.4.0-QASVK150901.jar;D:\.m2\repository\org\gridgain\ignite-shmem\1.0.0\ignite-shmem-1.0.0.jar;D:\.m2\repository\org\apache\igni
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Attachment: CacheTestExample.java
grid_config_01.xml
> putAll after put doesn't update values for some cache configurations
>
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.5
>
> Attachments: CacheTestExample.java, grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml in examples/config directory (it contains 25
> FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheTestExample (it makes 1000 single key-value puts and
> then 1000 gets)
> 5. The normal output should be following:
> {noformat}
> [22:55:58]__
> [22:55:58] / _/ ___/ |/ / _/_ __/ __/
> [22:55:58] _/ // (7 7// / / / / _/
> [22:55:58] /___/\___/_/|_/___/ /_/ /___/
> [22:55:58]
> [22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
> [22:55:58] 2015 Copyright(C) Apache Software Foundation
> [22:55:58]
> [22:55:58] Ignite documentation: http://ignite.apache.org
> [22:55:58]
> [22:55:58] Quiet mode.
> [22:55:58] ^-- Logging to file
> 'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
> [22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [22:55:58]
> [22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [22:56:00] Configured plugins:
> [22:56:00] ^-- None
> [22:56:00]
> [22:56:01] Security status [authentication=off, communication encryption=off]
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_4
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_1
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_10
> [22:56:04] Performance suggestions for grid (fix if possible)
> [22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [22:56:04] ^-- Disable fully synchronous writes (set
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
> [22:56:04]
> [22:56:04] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [22:56:04]
> [22:56:04] Ignite node started OK (id=faa18f29)
> [22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
> >>>cache_1
> Put for 1000
> Get for 1000
> >>>cache_2
> Put for 1000
> [23:03:21] New version is available at
> http://www.gridgain.com/download/editions: 1.3.3
> Get for 1000
> >>>cache_3
> Put for 1000
> Get for 1000
> >>>cache_4
> Put for 1000
> Get for 1000
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_18
> Put for 1000
> Get for 1000
> Wrong value found [key=0, val=null]
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Wrong value found [key=5, val=null]
> Wrong value found [key=6, val=null]
> Wrong value found [key=7, val=null]
> Wrong value found [key=8, val=null]
> Wrong value found [key=9, val=null]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1494) putAll after put doesn't update values for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791043#comment-14791043
]
Sergey Kozlov commented on IGNITE-1494:
---
If number of keys is 1000 issue happend for FULL_SYNC also.
> putAll after put doesn't update values for some cache configurations
>
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml in examples/config directory (it contains 25
> FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheTestExample (it makes 1000 single key-value puts and
> then 1000 gets)
> 5. The normal output should be following:
> {noformat}
> [22:55:58]__
> [22:55:58] / _/ ___/ |/ / _/_ __/ __/
> [22:55:58] _/ // (7 7// / / / / _/
> [22:55:58] /___/\___/_/|_/___/ /_/ /___/
> [22:55:58]
> [22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
> [22:55:58] 2015 Copyright(C) Apache Software Foundation
> [22:55:58]
> [22:55:58] Ignite documentation: http://ignite.apache.org
> [22:55:58]
> [22:55:58] Quiet mode.
> [22:55:58] ^-- Logging to file
> 'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
> [22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [22:55:58]
> [22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [22:56:00] Configured plugins:
> [22:56:00] ^-- None
> [22:56:00]
> [22:56:01] Security status [authentication=off, communication encryption=off]
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_4
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_1
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_10
> [22:56:04] Performance suggestions for grid (fix if possible)
> [22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [22:56:04] ^-- Disable fully synchronous writes (set
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
> [22:56:04]
> [22:56:04] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [22:56:04]
> [22:56:04] Ignite node started OK (id=faa18f29)
> [22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
> >>>cache_1
> Put for 1000
> Get for 1000
> >>>cache_2
> Put for 1000
> [23:03:21] New version is available at
> http://www.gridgain.com/download/editions: 1.3.3
> Get for 1000
> >>>cache_3
> Put for 1000
> Get for 1000
> >>>cache_4
> Put for 1000
> Get for 1000
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_18
> Put for 1000
> Get for 1000
> Wrong value found [key=0, val=null]
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Wrong value found [key=5, val=null]
> Wrong value found [key=6, val=null]
> Wrong value found [key=7, val=null]
> Wrong value found [key=8, val=null]
> Wrong value found [key=9, val=null]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Priority: Critical (was: Major)
Fix Version/s: (was: ignite-1.5)
ignite-1.4
> putAll after put doesn't update values for some cache configurations
>
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Yakov Zhdanov
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml in examples/config directory (it contains 25
> FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheTestExample (it makes 1000 single key-value puts and
> then 1000 gets)
> 5. The normal output should be following:
> {noformat}
> [22:55:58]__
> [22:55:58] / _/ ___/ |/ / _/_ __/ __/
> [22:55:58] _/ // (7 7// / / / / _/
> [22:55:58] /___/\___/_/|_/___/ /_/ /___/
> [22:55:58]
> [22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
> [22:55:58] 2015 Copyright(C) Apache Software Foundation
> [22:55:58]
> [22:55:58] Ignite documentation: http://ignite.apache.org
> [22:55:58]
> [22:55:58] Quiet mode.
> [22:55:58] ^-- Logging to file
> 'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
> [22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [22:55:58]
> [22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [22:56:00] Configured plugins:
> [22:56:00] ^-- None
> [22:56:00]
> [22:56:01] Security status [authentication=off, communication encryption=off]
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_4
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_1
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_10
> [22:56:04] Performance suggestions for grid (fix if possible)
> [22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [22:56:04] ^-- Disable fully synchronous writes (set
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
> [22:56:04]
> [22:56:04] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [22:56:04]
> [22:56:04] Ignite node started OK (id=faa18f29)
> [22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
> >>>cache_1
> Put for 1000
> Get for 1000
> >>>cache_2
> Put for 1000
> [23:03:21] New version is available at
> http://www.gridgain.com/download/editions: 1.3.3
> Get for 1000
> >>>cache_3
> Put for 1000
> Get for 1000
> >>>cache_4
> Put for 1000
> Get for 1000
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_18
> Put for 1000
> Get for 1000
> Wrong value found [key=0, val=null]
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Wrong value found [key=5, val=null]
> Wrong value found [key=6, val=null]
> Wrong value found [key=7, val=null]
> Wrong value found [key=8, val=null]
> Wrong value found [key=9, val=null]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) putAll after put doesn't update values for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Assignee: Alexey Goncharuk (was: Yakov Zhdanov)
> putAll after put doesn't update values for some cache configurations
>
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml in examples/config directory (it contains 25
> FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheTestExample (it makes 1000 single key-value puts and
> then 1000 gets)
> 5. The normal output should be following:
> {noformat}
> [22:55:58]__
> [22:55:58] / _/ ___/ |/ / _/_ __/ __/
> [22:55:58] _/ // (7 7// / / / / _/
> [22:55:58] /___/\___/_/|_/___/ /_/ /___/
> [22:55:58]
> [22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
> [22:55:58] 2015 Copyright(C) Apache Software Foundation
> [22:55:58]
> [22:55:58] Ignite documentation: http://ignite.apache.org
> [22:55:58]
> [22:55:58] Quiet mode.
> [22:55:58] ^-- Logging to file
> 'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
> [22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [22:55:58]
> [22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [22:56:00] Configured plugins:
> [22:56:00] ^-- None
> [22:56:00]
> [22:56:01] Security status [authentication=off, communication encryption=off]
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_4
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_1
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_10
> [22:56:04] Performance suggestions for grid (fix if possible)
> [22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [22:56:04] ^-- Disable fully synchronous writes (set
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
> [22:56:04]
> [22:56:04] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [22:56:04]
> [22:56:04] Ignite node started OK (id=faa18f29)
> [22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
> >>>cache_1
> Put for 1000
> Get for 1000
> >>>cache_2
> Put for 1000
> [23:03:21] New version is available at
> http://www.gridgain.com/download/editions: 1.3.3
> Get for 1000
> >>>cache_3
> Put for 1000
> Get for 1000
> >>>cache_4
> Put for 1000
> Get for 1000
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_18
> Put for 1000
> Get for 1000
> Wrong value found [key=0, val=null]
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Wrong value found [key=5, val=null]
> Wrong value found [key=6, val=null]
> Wrong value found [key=7, val=null]
> Wrong value found [key=8, val=null]
> Wrong value found [key=9, val=null]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Summary: Get return nulls for some cache configurations (was: putAll after
put doesn't update values for some cache configurations)
> Get return nulls for some cache configurations
> --
>
> Key: IGNITE-1494
> URL: https://issues.apache.org/jira/browse/IGNITE-1494
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: ignite-1.4
>
> Attachments: CacheTestExample.java, grid_config_01.xml
>
>
> 1. Copy grid_config_01.xml in examples/config directory (it contains 25
> FULL_SYNCed cache configurations)
> 2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
> 3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
> 4. Build and run CacheTestExample (it makes 1000 single key-value puts and
> then 1000 gets)
> 5. The normal output should be following:
> {noformat}
> [22:55:58]__
> [22:55:58] / _/ ___/ |/ / _/_ __/ __/
> [22:55:58] _/ // (7 7// / / / / _/
> [22:55:58] /___/\___/_/|_/___/ /_/ /___/
> [22:55:58]
> [22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
> [22:55:58] 2015 Copyright(C) Apache Software Foundation
> [22:55:58]
> [22:55:58] Ignite documentation: http://ignite.apache.org
> [22:55:58]
> [22:55:58] Quiet mode.
> [22:55:58] ^-- Logging to file
> 'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
> [22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
> "-v" to ignite.{sh|bat}
> [22:55:58]
> [22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [22:56:00] Configured plugins:
> [22:56:00] ^-- None
> [22:56:00]
> [22:56:01] Security status [authentication=off, communication encryption=off]
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_4
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_1
> [22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
> (entries will not be moved to off-heap store): cache_10
> [22:56:04] Performance suggestions for grid (fix if possible)
> [22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [22:56:04] ^-- Disable fully synchronous writes (set
> 'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
> [22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
> [22:56:04]
> [22:56:04] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [22:56:04]
> [22:56:04] Ignite node started OK (id=faa18f29)
> [22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
> >>>cache_1
> Put for 1000
> Get for 1000
> >>>cache_2
> Put for 1000
> [23:03:21] New version is available at
> http://www.gridgain.com/download/editions: 1.3.3
> Get for 1000
> >>>cache_3
> Put for 1000
> Get for 1000
> >>>cache_4
> Put for 1000
> Get for 1000
> ...
> {noformat}
> But for some caches I got:
> {noformat}
> >>>cache_18
> Put for 1000
> Get for 1000
> Wrong value found [key=0, val=null]
> Wrong value found [key=1, val=null]
> Wrong value found [key=2, val=null]
> Wrong value found [key=3, val=null]
> Wrong value found [key=4, val=null]
> Wrong value found [key=5, val=null]
> Wrong value found [key=6, val=null]
> Wrong value found [key=7, val=null]
> Wrong value found [key=8, val=null]
> Wrong value found [key=9, val=null]
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1395) REST HTTP module prints out unnecessary message
[
https://issues.apache.org/jira/browse/IGNITE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh reassigned IGNITE-1395:
Assignee: Roman Shtykh
> REST HTTP module prints out unnecessary message
> ---
>
> Key: IGNITE-1395
> URL: https://issues.apache.org/jira/browse/IGNITE-1395
> Project: Ignite
> Issue Type: Bug
> Components: newbie
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Roman Shtykh
>Priority: Minor
> Labels: newbie
> Fix For: ignite-1.5
>
> Attachments: ignite-1395.patch
>
>
> 1. Copy directory libs/optional/ignite-rest-http in libs/
> 2. Start node in quiet mode.
> 3. The output is following:
> {noformat}
> ...
> [17:49:42] Quiet mode.
> ...
> [17:49:50] Security status [authentication=off, communication encryption=off]
> 2015-09-09 17:49:50.789:INFO::main: Logging initialized @9841ms
> [17:49:52] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [17:49:52]
> [17:49:52] Ignite node started OK (id=54eee2db)
> [17:49:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=1.0GB]
> ...
> {noformat}
> The message after security status is generated by REST HTTP module.
> 1. It has wrong format
> 2. It should not be printed in quiet mode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1395) REST HTTP module prints out unnecessary message
[
https://issues.apache.org/jira/browse/IGNITE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791375#comment-14791375
]
tc_commenter commented on IGNITE-1395:
--
There was triggered next test builds for last attached patch-file:
01. http://204.14.53.153/viewQueued.html?itemId=106375 - Ignite AOP
02. http://204.14.53.153/viewQueued.html?itemId=106376 - Ignite Basic
03. http://204.14.53.153/viewQueued.html?itemId=106377 - Ignite Cache
04. http://204.14.53.153/viewQueued.html?itemId=106378 - Ignite Cache 2
05. http://204.14.53.153/viewQueued.html?itemId=106379 - Ignite Cache 3
06. http://204.14.53.153/viewQueued.html?itemId=106380 - Ignite Cache 4
07. http://204.14.53.153/viewQueued.html?itemId=106381 - Ignite Cache Expiry
Policy
08. http://204.14.53.153/viewQueued.html?itemId=106382 - Ignite Cache Failover
09. http://204.14.53.153/viewQueued.html?itemId=106383 - Ignite Cache Failover
Multi JVM
10. http://204.14.53.153/viewQueued.html?itemId=106384 - Ignite Cache Failover2
11. http://204.14.53.153/viewQueued.html?itemId=106385 - Ignite Cache Full API
12. http://204.14.53.153/viewQueued.html?itemId=106386 - Ignite Cache Full API
Multi JVM
13. http://204.14.53.153/viewQueued.html?itemId=106387 - Ignite Cache Full API
Portable
14. http://204.14.53.153/viewQueued.html?itemId=106388 - Ignite Cache Portable
15. http://204.14.53.153/viewQueued.html?itemId=106389 - Ignite Cache Query
Portable
16. http://204.14.53.153/viewQueued.html?itemId=106390 - Ignite Cache Restarts
17. http://204.14.53.153/viewQueued.html?itemId=106391 - Ignite Cache Tx
Recovery
18. http://204.14.53.153/viewQueued.html?itemId=106392 - Ignite Cloud
19. http://204.14.53.153/viewQueued.html?itemId=106393 - Ignite Compute Grid
20. http://204.14.53.153/viewQueued.html?itemId=106394 - Ignite Data Strucutures
21. http://204.14.53.153/viewQueued.html?itemId=106395 - Ignite Examples
22. http://204.14.53.153/viewQueued.html?itemId=106396 - Ignite GCE
23. http://204.14.53.153/viewQueued.html?itemId=106397 - Ignite Geospacial
Indexing
24. http://204.14.53.153/viewQueued.html?itemId=106398 - Ignite H2 Indexing
25. http://204.14.53.153/viewQueued.html?itemId=106399 - Ignite Hadoop
26. http://204.14.53.153/viewQueued.html?itemId=106400 - Ignite Hibernate
27. http://204.14.53.153/viewQueued.html?itemId=106401 - Ignite IGFS
28. http://204.14.53.153/viewQueued.html?itemId=106402 - Ignite IGFS Examples
29. http://204.14.53.153/viewQueued.html?itemId=106403 - Ignite IGFS Linux and
MacOS
30. http://204.14.53.153/viewQueued.html?itemId=106404 - Ignite Java Client
31. http://204.14.53.153/viewQueued.html?itemId=106405 - Ignite JDBC Driver
32. http://204.14.53.153/viewQueued.html?itemId=106406 - Ignite JTA
33. http://204.14.53.153/viewQueued.html?itemId=106407 - Ignite Logging
34. http://204.14.53.153/viewQueued.html?itemId=106408 - Ignite Portables Basic
35. http://204.14.53.153/viewQueued.html?itemId=106409 - Ignite Queries
36. http://204.14.53.153/viewQueued.html?itemId=106410 - Ignite Scalar Examples
37. http://204.14.53.153/viewQueued.html?itemId=106411 - Ignite SPI
38. http://204.14.53.153/viewQueued.html?itemId=106412 - Ignite Spring
39. http://204.14.53.153/viewQueued.html?itemId=106413 - Ignite Start Nodes
40. http://204.14.53.153/viewQueued.html?itemId=106414 - Ignite URI Deploy SPI
41. http://204.14.53.153/viewQueued.html?itemId=106415 - Ignite Visor Console
42. http://204.14.53.153/viewQueued.html?itemId=106416 - Ignite WebSessions
43. http://204.14.53.153/viewQueued.html?itemId=106417 - JCache TCK
> REST HTTP module prints out unnecessary message
> ---
>
> Key: IGNITE-1395
> URL: https://issues.apache.org/jira/browse/IGNITE-1395
> Project: Ignite
> Issue Type: Bug
> Components: newbie
>Affects Versions: ignite-1.4
>Reporter: Sergey Kozlov
>Assignee: Roman Shtykh
>Priority: Minor
> Labels: newbie
> Fix For: ignite-1.5
>
> Attachments: ignite-1395.patch
>
>
> 1. Copy directory libs/optional/ignite-rest-http in libs/
> 2. Start node in quiet mode.
> 3. The output is following:
> {noformat}
> ...
> [17:49:42] Quiet mode.
> ...
> [17:49:50] Security status [authentication=off, communication encryption=off]
> 2015-09-09 17:49:50.789:INFO::main: Logging initialized @9841ms
> [17:49:52] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [17:49:52]
> [17:49:52] Ignite node started OK (id=54eee2db)
> [17:49:52] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=1.0GB]
> ...
> {noformat}
> The message after security status is generated by REST HTTP module.
> 1. It has wrong format
> 2. It should not be printed in quiet mode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791476#comment-14791476 ] Pavel Konstantinov commented on IGNITE-850: --- Successfully verified > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1146) Implement summary page with configuration downloads.
[ https://issues.apache.org/jira/browse/IGNITE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1146: --- Description: Generate: * sprint xml configuration; * Java class with configuration; * Java snippet with configuration; * docker file for run with this configuration. Download all generated files as zip archive, generate client configuration. was: Generate: * sprint xml configuration; * java class with configuration; * java snipplet with configuration; * docker file for run with this configuration. Download all generated files as zip archive, generate client configuration. > Implement summary page with configuration downloads. > > > Key: IGNITE-1146 > URL: https://issues.apache.org/jira/browse/IGNITE-1146 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: summary - client.png, summary - server.png, > test-cluster-2.xml > > > Generate: > * sprint xml configuration; > * Java class with configuration; > * Java snippet with configuration; > * docker file for run with this configuration. > Download all generated files as zip archive, generate client configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-1147: Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) I'm facing with issue when I trying to change my password. I'm setting a new password and Confirm then clicking on Save button, but nothing happens. Then I clicking 'Configuration' link and getting 'Internal system error'. > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1147) Implement profile page for user.
[ https://issues.apache.org/jira/browse/IGNITE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791569#comment-14791569 ] Pavel Konstantinov commented on IGNITE-1147: Verified > Implement profile page for user. > > > Key: IGNITE-1147 > URL: https://issues.apache.org/jira/browse/IGNITE-1147 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: profile.png > > > Need add possibility to change email, password, username. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571 ] Dmitriy Setrakyan commented on IGNITE-843: -- I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screen should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen. Same goes for other screens with similar behavior. # Red tooltips look to offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x > # Auxiliary: jQuery 2.x / AngularJS UI 0.x > # HTTP server: node.js > # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable > Install node.js locally. > Install Angular, LESS, and Grunt plugins into IDEA. > Use LESS instead of CSS. >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: ig-843.png > > > Frameworks to be used: > # Bootstrap > # AngularJS > # NodeJS > # MongoDB > Web control Center will communicate with Ignite Cluster via special > lightweight proxy (so called web-agent) implemented on web-sockets. > Test server: http://104.197.2.239 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-851) Implement caches screen
[ https://issues.apache.org/jira/browse/IGNITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791573#comment-14791573 ] Pavel Konstantinov commented on IGNITE-851: --- Verified > Implement caches screen > --- > > Key: IGNITE-851 > URL: https://issues.apache.org/jira/browse/IGNITE-851 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Alexey Kuznetsov > Fix For: ignite-1.5 > > Attachments: Caches.pdf, caches-page-advanced-2.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571 ] Dmitriy Setrakyan edited comment on IGNITE-843 at 9/17/15 4:36 AM: --- I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screen should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen. Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). was (Author: dsetrakyan): I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screen should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen. Same goes for other screens with similar behavior. # Red tooltips look to offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: sprint-5 > Environment: Specific frameworks: > # Main SPA stack: H
[jira] [Comment Edited] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571 ] Dmitriy Setrakyan edited comment on IGNITE-843 at 9/17/15 4:39 AM: --- I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screen should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen. Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). # Docker image should download OpenJDK, not Oracle JDK (due to the license). was (Author: dsetrakyan): I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screen should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen. Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versio
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791574#comment-14791574 ] Pavel Konstantinov commented on IGNITE-850: --- Verified > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571 ] Dmitriy Setrakyan edited comment on IGNITE-843 at 9/17/15 4:43 AM: --- I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screens should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen). Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). # Docker image should download OpenJDK, not Oracle JDK (due to the license). was (Author: dsetrakyan): I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screen should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen. Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). # Docker image should download OpenJDK, not Oracle JDK (due to the license). > Web configuration tools development > --- > > Key: IGNITE-843 > URL: https://issues.apache.org/jira/browse/IGNITE-843 > Project: Ignite
[jira] [Commented] (IGNITE-850) Implement clusters screen
[ https://issues.apache.org/jira/browse/IGNITE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791576#comment-14791576 ] Pavel Konstantinov commented on IGNITE-850: --- I think we should add validation of 'Local class path exclude' value (that it contain package name) > Implement clusters screen > - > > Key: IGNITE-850 > URL: https://issues.apache.org/jira/browse/IGNITE-850 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Goncharuk >Assignee: Pavel Konstantinov > Fix For: ignite-1.5 > > Attachments: cluster page.png, clusters-page-2.png, > clusters-page-3.png, clusters.pdf, ig-850-zones.png > > > See screenshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571 ] Dmitriy Setrakyan edited comment on IGNITE-843 at 9/17/15 4:49 AM: --- I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screens should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen). Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). # Docker image should download OpenJDK, not Oracle JDK (due to the license). # In Profile page, the Change Password checkbox should be changed to a link (same as we do for "Show advanced settings" links). was (Author: dsetrakyan): I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screens should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen). Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). # Docker image should download OpenJDK, not Oracle JDK (due to the license). > Web configuration tools development > --- > >
[jira] [Comment Edited] (IGNITE-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571 ] Dmitriy Setrakyan edited comment on IGNITE-843 at 9/17/15 4:51 AM: --- I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screens should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen). Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I think we should provide a sample data source (user should clearly see that it is a sample). # Docker image should download OpenJDK, not Oracle JDK (due to the license). # In Profile page, the Change Password checkbox should be changed to a link (same as we do for "Show advanced settings" links). # The SQL screen should describe that it connects to either live Ignite cluster and test-mode in the agent. It should explicitly say that the cluster should be started. It should also describe how the connection to the cluster works through an agent. was (Author: dsetrakyan): I had another look at UI and have the following comments that apply to all screens in general. I am using a numbered list, so that we can keep track which change was fixed by its number. # What’s Now -> On This Screen # What’s next -> Next Steps # Use normal popup dialog when leaving screen with unsaved changes (do not use standard web browser popup). The popup should have an option to Save before leaving the screen. # "New" button on all the screens should be renamed to describe the action: "Add cluster", "Add Cache", etc. # For multi-select dropdown, whenever names are short, we should list the names instead of the number of entries selected. This does not work for metadata selection, as class-names are too long, so let's keep the number there. # Cache (add) should take a user to the New Cache screen (no need to force the user to explicitly press "New" again on the cache screen). Same goes for other screens with similar behavior. # Red tooltips look too offensive. Can we try changing the background of tooltips to blue? # Instead of having a hidden "copy" action inside the button, let's add explicit button called "Clone" # We should not show the security token on UI screen (should be "**" with "Show Token" link next to it). Would also be nice to add "Copy to clipboard" icon next to it as well. # Every time we show the security token, we should provide a tooltip explaining what it is for. # Not sure why "Reset password" screen shows the security token. I would prefer that it shows the email address. # After the password was reset, user should have a message on the screen: Your password has been reset, please [link: login]. # Assigning metadata to caches one-by-one is inconvenient. User should be able to associate multiple or all metadata with a cache in one action. # User should have a confirmation popup if he decides to change the security token. # Load from Database wizard should provide instructions on how to change the database driver. # XML code snippet does not have data source. I
[jira] [Updated] (IGNITE-967) Internal thread locals are not always cleaned
[
https://issues.apache.org/jira/browse/IGNITE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-967:
---
Fix Version/s: ignite-1.5
> Internal thread locals are not always cleaned
> -
>
> Key: IGNITE-967
> URL: https://issues.apache.org/jira/browse/IGNITE-967
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: ignite-1.5
>
>
> One of our users reported that he sees warnings in Tomcat's log when the
> application that's running Ignite in embedded mode is undeployed:
> {code}
> SEVERE: The web application [/XXX] created a ThreadLocal with key of type
> [org.apache.ignite.internal.util.GridSpinReadWriteLock$1] (value
> [org.apache.ignite.internal.util.GridSpinReadWriteLock$1@2c2858af]) and a
> value of type [java.lang.Integer] (value [0]) but failed to remove it when
> the web application was stopped. Threads are going to be renewed over time to
> try and avoid a probable memory leak.
> {code}
> There is also the similar warning for {{GridToStringBuilder.threadCache}}.
> While it's usually OK not to clean thread locals on standalone node, in app
> server it can cause a memory leak.
> To avoid such issues I suggest to add a special step after all test suites
> that will check thread locals in test runner thread. If we have this check in
> CI, we will fix it once and for always.
> Thread local values can be introspected through {{Thread.threadLocals}}
> variable. It would also be a good idea to check Tomcat's sources on how it's
> done there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-967) Internal thread locals are not always cleaned
[
https://issues.apache.org/jira/browse/IGNITE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-967:
--
Assignee: Valentin Kulichenko
> Internal thread locals are not always cleaned
> -
>
> Key: IGNITE-967
> URL: https://issues.apache.org/jira/browse/IGNITE-967
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: ignite-1.5
>
>
> One of our users reported that he sees warnings in Tomcat's log when the
> application that's running Ignite in embedded mode is undeployed:
> {code}
> SEVERE: The web application [/XXX] created a ThreadLocal with key of type
> [org.apache.ignite.internal.util.GridSpinReadWriteLock$1] (value
> [org.apache.ignite.internal.util.GridSpinReadWriteLock$1@2c2858af]) and a
> value of type [java.lang.Integer] (value [0]) but failed to remove it when
> the web application was stopped. Threads are going to be renewed over time to
> try and avoid a probable memory leak.
> {code}
> There is also the similar warning for {{GridToStringBuilder.threadCache}}.
> While it's usually OK not to clean thread locals on standalone node, in app
> server it can cause a memory leak.
> To avoid such issues I suggest to add a special step after all test suites
> that will check thread locals in test runner thread. If we have this check in
> CI, we will fix it once and for always.
> Thread local values can be introspected through {{Thread.threadLocals}}
> variable. It would also be a good idea to check Tomcat's sources on how it's
> done there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1494) Get return nulls for some cache configurations
[
https://issues.apache.org/jira/browse/IGNITE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kozlov updated IGNITE-1494:
--
Description:
1. Copy grid_config_01.xml in examples/config directory (it contains 25
FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/grid_config_01.xml
4. Build and run CacheTestExample (it makes 1000 single key-value puts and then
1000 gets)
5. The normal output should be following:
{noformat}
[22:55:58]__
[22:55:58] / _/ ___/ |/ / _/_ __/ __/
[22:55:58] _/ // (7 7// / / / / _/
[22:55:58] /___/\___/_/|_/___/ /_/ /___/
[22:55:58]
[22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
[22:55:58] 2015 Copyright(C) Apache Software Foundation
[22:55:58]
[22:55:58] Ignite documentation: http://ignite.apache.org
[22:55:58]
[22:55:58] Quiet mode.
[22:55:58] ^-- Logging to file
'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
[22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[22:55:58]
[22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[22:56:00] Configured plugins:
[22:56:00] ^-- None
[22:56:00]
[22:56:01] Security status [authentication=off, communication encryption=off]
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_4
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_1
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_10
[22:56:04] Performance suggestions for grid (fix if possible)
[22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[22:56:04] ^-- Disable fully synchronous writes (set
'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
[22:56:04] ^-- Decrease number of backups (set 'keyBackups' to 0)
[22:56:04]
[22:56:04] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[22:56:04]
[22:56:04] Ignite node started OK (id=faa18f29)
[22:56:04] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4, heap=5.5GB]
>>>cache_1
Put for 1000
Get for 1000
>>>cache_2
Put for 1000
[23:03:21] New version is available at
http://www.gridgain.com/download/editions: 1.3.3
Get for 1000
>>>cache_3
Put for 1000
Get for 1000
>>>cache_4
Put for 1000
Get for 1000
...
{noformat}
But for some caches I got:
{noformat}
>>>cache_18
Put for 1000
Get for 1000
Wrong value found [key=0, val=null]
Wrong value found [key=1, val=null]
Wrong value found [key=2, val=null]
Wrong value found [key=3, val=null]
Wrong value found [key=4, val=null]
Wrong value found [key=5, val=null]
Wrong value found [key=6, val=null]
Wrong value found [key=7, val=null]
Wrong value found [key=8, val=null]
Wrong value found [key=9, val=null]
...
{noformat}
was:
1. Copy grid_config_01.xml in examples/config directory (it contains 25
FULL_SYNCed cache configurations)
2. Copy CacheTestExample in org.apache.ignite.examples.datagrid package
3. Start two nodes by bin/ignite.sh examples/config/example-evict.xml
4. Build and run CacheTestExample (it makes 1000 single key-value puts and then
1000 gets)
5. The normal output should be following:
{noformat}
[22:55:58]__
[22:55:58] / _/ ___/ |/ / _/_ __/ __/
[22:55:58] _/ // (7 7// / / / / _/
[22:55:58] /___/\___/_/|_/___/ /_/ /___/
[22:55:58]
[22:55:58] ver. 1.4.0-QASVK150901#20150915-sha1:3e762e25
[22:55:58] 2015 Copyright(C) Apache Software Foundation
[22:55:58]
[22:55:58] Ignite documentation: http://ignite.apache.org
[22:55:58]
[22:55:58] Quiet mode.
[22:55:58] ^-- Logging to file
'D:\1.4.0\gridgain-community-fabric-1.4.0-QASVK150901\work\log\ignite-faa18f29.log'
[22:55:58] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[22:55:58]
[22:55:58] Initial heap size is 256MB (should be no less than 512MB, use
-Xms512m -Xmx512m).
[22:56:00] Configured plugins:
[22:56:00] ^-- None
[22:56:00]
[22:56:01] Security status [authentication=off, communication encryption=off]
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_4
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_1
[22:56:02] Eviction policy not enabled with ONHEAP_TIERED mode for cache
(entries will not be moved to off-heap store): cache_10
[22:56:04] Performance suggestions for grid (fix if possible)
[22:56:04] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[22:56:04] ^-- Disable fully synchronous writes (set
'writeSyn
[jira] [Created] (IGNITE-1498) Add support for specifying config via command line option
Alexey Kuznetsov created IGNITE-1498: Summary: Add support for specifying config via command line option Key: IGNITE-1498 URL: https://issues.apache.org/jira/browse/IGNITE-1498 Project: Ignite Issue Type: Bug Components: UI Affects Versions: sprint-1 Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Priority: Blocker Fix For: ignite-1.4 Add support for "-cfg path" for command line Visor . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
