[jira] [Resolved] (IGNITE-1498) Add support for specifying config via command line option
[ https://issues.apache.org/jira/browse/IGNITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-1498. -- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) I added support for "-cfg=path" to command line Visor. Also test "-help" option. Please test in ignite-1.4 branch. > 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: Pavel Konstantinov >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)
[jira] [Updated] (IGNITE-586) [Test] GridGgfsAbstractSelfTest.testFormat() fails on TC.
[ https://issues.apache.org/jira/browse/IGNITE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-586: --- Fix Version/s: (was: ignite-1.5) ignite-1.4 > [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.4 > > > 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-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=14791774#comment-14791774 ] Vladimir Ozerov commented on IGNITE-586: Looks like we should try including it into ignite-1.4 becuase potentially every IGFS user can be seriously affected by it. > [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.4 > > > 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-1496) Platform .Net: Add .Net examples
[ https://issues.apache.org/jira/browse/IGNITE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791840#comment-14791840 ] ASF GitHub Bot commented on IGNITE-1496: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/96 IGNITE-1496 Platform .Net: Add .Net examples You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1496 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/96.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 #96 commit 6feef10b995f9c0914ea13acf952e084df6c3662 Author: ptupitsyn Date: 2015-09-16T13:58:18Z IGNITE-1496 Platform .Net: Add .Net examples commit 2f3207f2ce6fc1c60a991248bd17e8b2a20360bb Author: ptupitsyn Date: 2015-09-16T14:08:02Z IGNITE-1496 Platform .Net: Add .Net examples commit d790e5d9e007fd74fea92572709ec0cd9e625149 Author: ptupitsyn Date: 2015-09-16T14:13:44Z wip commit a81ed6bd3b8b29cad209b9b840d38ccc5959ff79 Author: ptupitsyn Date: 2015-09-16T14:17:44Z Fix headers and assemblyInfo commit ea77c1154eb3120e6f8d8f234a45b79ab611d4f6 Author: ptupitsyn Date: 2015-09-16T14:27:42Z fixing build commit 8dfd691bffbc7379b77ba77113239c616b40991c Author: ptupitsyn Date: 2015-09-16T14:31:31Z wip commit 964bad847789aee9084071c899a664775d24be36 Author: ptupitsyn Date: 2015-09-16T14:39:04Z fix namespaces commit 30eb5b6b283251132a8c3a7545e3b4a3e383b1ac Author: ptupitsyn Date: 2015-09-16T14:46:49Z wip commit c5c03de28014b63f0a4599d0769c6d70adbc92e4 Author: ptupitsyn Date: 2015-09-16T14:56:46Z wip commit e78280c230966ff0209025cd851d1ab16f097a23 Author: ptupitsyn Date: 2015-09-16T14:58:33Z wip commit c09d90bcced0af3d83e50c6dfc35d83dcd37f1c4 Author: ptupitsyn Date: 2015-09-16T15:08:42Z Add examples to main sln commit 397f5f7c153a7a0f3a30de20f2a7b83d39f328cd Author: ptupitsyn Date: 2015-09-16T15:34:28Z Adding example tests commit 57cf34558739d3632132a5cc7b5458d1e3b4 Author: ptupitsyn Date: 2015-09-16T15:46:34Z wip commit 434b569c05be0e853bcc5690e247da9fe06b955e Author: ptupitsyn Date: 2015-09-16T16:04:03Z wip commit c3f22e68c162ff78a8db854775ac45c9a2e7616f Author: ptupitsyn Date: 2015-09-16T16:09:32Z Fixing configs commit ff733cebb059a465de0bbe693947b7b2babecfa1 Author: ptupitsyn Date: 2015-09-17T09:03:56Z Merge remote-tracking branch 'remotes/upstream/master' into ignite-1496 commit 7916c98b935b829f2cdf34da328e922b1a636259 Author: ptupitsyn Date: 2015-09-17T09:09:05Z wip commit b37b196939d11e2b42514f2241ac19ac93c17db5 Author: ptupitsyn Date: 2015-09-17T09:18:22Z GG-10684 Interop .Net: Fix or suppress remaining FxCop warnings commit 3bc317744d9600698da3a7bfc36d34e5b32145e3 Author: ptupitsyn Date: 2015-09-17T09:32:13Z Set intensive test category commit 0e8b23c79984d8193299848412c5c5f5159c8252 Author: ptupitsyn Date: 2015-09-17T09:32:47Z wip > 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] [Updated] (IGNITE-1369) CacheClientPortableQueryExample fails when remote node is started without test objects in classpath
[
https://issues.apache.org/jira/browse/IGNITE-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-1369:
---
Component/s: (was: documentation)
general
> CacheClientPortableQueryExample fails when remote node is started without
> test objects in classpath
> ---
>
> Key: IGNITE-1369
> URL: https://issues.apache.org/jira/browse/IGNITE-1369
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Vasilisa Sidorova
>Assignee: Denis Magda
>Priority: Critical
>
> CacheClientPortableQueryExample fails with exception:
> {noformat}
> Exception in thread "main" javax.cache.CacheException: Failed to run map
> query remotely.
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:575)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:864)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:898)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
> at
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:73)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.sqlQuery(CacheClientPortableQueryExample.java:196)
> at
> org.apache.ignite.examples.portable.datagrid.CacheClientPortableQueryExample.main(CacheClientPortableQueryExample.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
> Caused by: javax.cache.CacheException: Failed to execute map query on the
> node: da4ddf09-acdd-4b4b-a945-64c1a60fd8b1, class
> org.apache.ignite.IgniteCheckedException:Failed to parse SQL query: SELECT
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._KEY __C0,
> "CacheClientPortableQueryExampleEmployees".EMPLOYEE._VAL __C1
> FROM "CacheClientPortableQueryExampleEmployees".EMPLOYEE
> WHERE ZIP = ?1
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:255)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:226)
> at
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:174)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1887)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> if it's running with node from command line. And
> CacheClientPortableQueryExample is running OK with GridExampleNodeStartup.
> So, it's need to delete text:
> {noformat}
> * Alternatively you can run {@link ExamplePortableNodeStartup} in another JVM
> which will
> * start node with {@code
> examples/config/portable/example-ignite-portable.xml} configuration.
> {noformat}
> from example description
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-1435) Platform .Net: Make it possible to sign core assembly with msbuild
[ https://issues.apache.org/jira/browse/IGNITE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1435. --- > Platform .Net: Make it possible to sign core assembly with msbuild > -- > > Key: IGNITE-1435 > URL: https://issues.apache.org/jira/browse/IGNITE-1435 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: ignite-1.5 > > > Currently we use InternalsVisibleTo attribute in Apache.Ignite.Core > AssemblyInfo, which prevents signing the assembly with msbuild > /p:SignAssembly file. > Need to wrap them in a preprocessor check so that msbuild flag > /p:DefineConstants will exclude that code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1498) Add support for specifying config via command line option
[ https://issues.apache.org/jira/browse/IGNITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802726#comment-14802726 ] Pavel Konstantinov commented on IGNITE-1498: Successfully tested in 1.4 > 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: Pavel Konstantinov >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)
[jira] [Closed] (IGNITE-1498) Add support for specifying config via command line option
[ https://issues.apache.org/jira/browse/IGNITE-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-1498. -- Assignee: (was: Pavel Konstantinov) > 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 >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)
[jira] [Commented] (IGNITE-1496) Platform .Net: Add .Net examples
[ https://issues.apache.org/jira/browse/IGNITE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802740#comment-14802740 ] Pavel Tupitsyn commented on IGNITE-1496: - Tests added to Long Running suite. > 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] [Updated] (IGNITE-1152) Distribution of backup partitions is not uniform
[ https://issues.apache.org/jira/browse/IGNITE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-1152: -- Fix Version/s: (was: ignite-1.5) > Distribution of backup partitions is not uniform > > > Key: IGNITE-1152 > URL: https://issues.apache.org/jira/browse/IGNITE-1152 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Goncharuk > Attachments: CacheBackupPartitionsTest.java > > > I started 4 nodes with partitioned cache with 1 backup. > And found that primary parts more or less uniform, but backup parts - not: > Node n1: : pri=244, bak=367 > Node n2: : pri=260, bak=590 > Node n3: : pri=244, bak=367 > Node n4: : pri=260, bak=590 > Code to test this issue attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1416) .Net: Implement "atomic" data structures.
[ https://issues.apache.org/jira/browse/IGNITE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-1416: --- Assignee: Pavel Tupitsyn > .Net: Implement "atomic" data structures. > - > > Key: IGNITE-1416 > URL: https://issues.apache.org/jira/browse/IGNITE-1416 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Pavel Tupitsyn >Priority: Critical > Fix For: ignite-1.5 > > > This includes: > - atomicLong; > - atomicSequence; > - atomicStamped; > - atomicReference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
Pavel Tupitsyn created IGNITE-1499:
---
Summary: Platform .Net: fix naming and use properties where
appropriate in the API
Key: IGNITE-1499
URL: https://issues.apache.org/jira/browse/IGNITE-1499
Project: Ignite
Issue Type: Sub-task
Components: interop
Affects Versions: ignite-1.5
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: ignite-1.5
* See IIgnite & IClusterGroup: things like Events() and Compute() can be
changed to properties.
* Things like Events(IClusterGroup) are redundant and should be removed from API
* Methods should comply to naming conventions: GetEvents() is a method, Events
{get;} is a property
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
[
https://issues.apache.org/jira/browse/IGNITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1499:
Description:
* Methods should comply to naming conventions: GetEvents() instead of Events()
* Change IIgniteTransactions to be a method like all other things. Properties
are not suitable because we may return different instances in future.
was:
* See IIgnite & IClusterGroup: things like Events() and Compute() can be
changed to properties.
* Things like Events(IClusterGroup) are redundant and should be removed from API
* Methods should comply to naming conventions: GetEvents() is a method, Events
{get;} is a property
> Platform .Net: fix naming and use properties where appropriate in the API
> -
>
> Key: IGNITE-1499
> URL: https://issues.apache.org/jira/browse/IGNITE-1499
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Affects Versions: ignite-1.5
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
> Fix For: ignite-1.5
>
>
> * Methods should comply to naming conventions: GetEvents() instead of Events()
> * Change IIgniteTransactions to be a method like all other things. Properties
> are not suitable because we may return different instances in future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
[ https://issues.apache.org/jira/browse/IGNITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-1499: Description: * Methods should comply to naming conventions: GetEvents() instead of Events() * Change IIgniteTransactions to be a method like all other things. Properties are not suitable because we may return different instances in future. * Compute(IClusterGroup) and similar methods are redundant, get rid of them to clean the API. was: * Methods should comply to naming conventions: GetEvents() instead of Events() * Change IIgniteTransactions to be a method like all other things. Properties are not suitable because we may return different instances in future. > Platform .Net: fix naming and use properties where appropriate in the API > - > > Key: IGNITE-1499 > URL: https://issues.apache.org/jira/browse/IGNITE-1499 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > > * Methods should comply to naming conventions: GetEvents() instead of Events() > * Change IIgniteTransactions to be a method like all other things. Properties > are not suitable because we may return different instances in future. > * Compute(IClusterGroup) and similar methods are redundant, get rid of them > to clean the API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1152) Distribution of backup partitions is not uniform
[
https://issues.apache.org/jira/browse/IGNITE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802893#comment-14802893
]
Anton Vinogradov commented on IGNITE-1152:
--
doing
for (int i = 0; i < 10; i++) {
n1.cache("c1").put(i, 1);
n2.cache("c1").put(i, 1);
n3.cache("c1").put(i, 1);
n4.cache("c1").put(i, 1);
}
before counting backups solves problem.
Seems backup evictions depends on cache operations.
Result before warmup:
<16:16:34,071> Node n1: : pri=238, bak=341
<16:16:34,072> Node n2: : pri=230, bak=633
<16:16:34,072> Node n3: : pri=288, bak=410
<16:16:34,073> Node n4: : pri=268, bak=260
Result after warmup:
<16:15:55,716> Node n1: : pri=238, bak=340
<16:15:55,717> Node n2: : pri=230, bak=349
<16:15:55,717> Node n3: : pri=288, bak=293
<16:15:55,717> Node n4: : pri=268, bak=260
> Distribution of backup partitions is not uniform
>
>
> Key: IGNITE-1152
> URL: https://issues.apache.org/jira/browse/IGNITE-1152
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Goncharuk
> Attachments: CacheBackupPartitionsTest.java
>
>
> I started 4 nodes with partitioned cache with 1 backup.
> And found that primary parts more or less uniform, but backup parts - not:
> Node n1: : pri=244, bak=367
> Node n2: : pri=260, bak=590
> Node n3: : pri=244, bak=367
> Node n4: : pri=260, bak=590
> Code to test this issue attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
[ https://issues.apache.org/jira/browse/IGNITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802899#comment-14802899 ] ASF GitHub Bot commented on IGNITE-1499: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/97 IGNITE-1499 Platform .Net: fix naming and use properties where appropriate in the API You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1499 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/97.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 #97 commit b87dede5d80100feec160561824f80f6e56617b1 Author: ptupitsyn Date: 2015-09-17T12:55:21Z wip commit 0e319af45d8bb258c55352a32a1c440eb48de4b6 Author: ptupitsyn Date: 2015-09-17T12:57:37Z wip commit 884ab5e14c38e8a9ab4db2bcd8d7c7f4f87acd06 Author: ptupitsyn Date: 2015-09-17T12:59:38Z wip commit 795424bb155f2a985ab4a5915738c4fe12525c13 Author: ptupitsyn Date: 2015-09-17T13:01:53Z wip commit 60cc89fd35a3fe009a85e7c13f201f61c94c5e3d Author: ptupitsyn Date: 2015-09-17T13:04:13Z wip commit d86b8a80c05075c2ad910be6b51078ae4732bc75 Author: ptupitsyn Date: 2015-09-17T13:06:07Z wip commit 58846e4442c8cbde55b91e8167cbb0a9e326b045 Author: ptupitsyn Date: 2015-09-17T13:08:47Z wip commit 73da409f5f33be71c62ad909df27aa82cb6394b8 Author: ptupitsyn Date: 2015-09-17T13:11:02Z wip commit 9866c016956029d3d8f799e9e7ecfe1604496d50 Author: ptupitsyn Date: 2015-09-17T13:13:36Z wip commit 74c4b01833f43c4cbcffd13a7dfd1dfd1373ec6c Author: ptupitsyn Date: 2015-09-17T13:16:11Z wip > Platform .Net: fix naming and use properties where appropriate in the API > - > > Key: IGNITE-1499 > URL: https://issues.apache.org/jira/browse/IGNITE-1499 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > > * Methods should comply to naming conventions: GetEvents() instead of Events() > * Change IIgniteTransactions to be a method like all other things. Properties > are not suitable because we may return different instances in future. > * Compute(IClusterGroup) and similar methods are redundant, get rid of them > to clean the API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
[ https://issues.apache.org/jira/browse/IGNITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802935#comment-14802935 ] ASF GitHub Bot commented on IGNITE-1499: Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/97 > Platform .Net: fix naming and use properties where appropriate in the API > - > > Key: IGNITE-1499 > URL: https://issues.apache.org/jira/browse/IGNITE-1499 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Vladimir Ozerov > Fix For: ignite-1.5 > > > * Methods should comply to naming conventions: GetEvents() instead of Events() > * Change IIgniteTransactions to be a method like all other things. Properties > are not suitable because we may return different instances in future. > * Compute(IClusterGroup) and similar methods are redundant, get rid of them > to clean the API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
[ https://issues.apache.org/jira/browse/IGNITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802936#comment-14802936 ] Pavel Tupitsyn commented on IGNITE-1499: - Merged to ignite-1282 > Platform .Net: fix naming and use properties where appropriate in the API > - > > Key: IGNITE-1499 > URL: https://issues.apache.org/jira/browse/IGNITE-1499 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > > * Methods should comply to naming conventions: GetEvents() instead of Events() > * Change IIgniteTransactions to be a method like all other things. Properties > are not suitable because we may return different instances in future. > * Compute(IClusterGroup) and similar methods are redundant, get rid of them > to clean the API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1499) Platform .Net: fix naming and use properties where appropriate in the API
[ https://issues.apache.org/jira/browse/IGNITE-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-1499. --- > Platform .Net: fix naming and use properties where appropriate in the API > - > > Key: IGNITE-1499 > URL: https://issues.apache.org/jira/browse/IGNITE-1499 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.5 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Fix For: ignite-1.5 > > > * Methods should comply to naming conventions: GetEvents() instead of Events() > * Change IIgniteTransactions to be a method like all other things. Properties > are not suitable because we may return different instances in future. > * Compute(IClusterGroup) and similar methods are redundant, get rid of them > to clean the API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1500) Invalid docs in distributed data structures classes.
Vladimir Ozerov created IGNITE-1500:
---
Summary: Invalid docs in distributed data structures classes.
Key: IGNITE-1500
URL: https://issues.apache.org/jira/browse/IGNITE-1500
Project: Ignite
Issue Type: Bug
Components: cache, general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Fix For: ignite-1.5
Problem: it is mentioned that async operations are supported, while they are
not:
{code}All previously described methods have asynchronous analogs.{code}
Affected classes:
- IgniteAtomicLong
- IgniteAtomicReference
- IgniteAtomicSequence
- IgniteAtomicStamped
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1501) Add compare-and-set operation which returns currnet value in case of failure.
Vladimir Ozerov created IGNITE-1501: --- Summary: Add compare-and-set operation which returns currnet value in case of failure. Key: IGNITE-1501 URL: https://issues.apache.org/jira/browse/IGNITE-1501 Project: Ignite Issue Type: Task Components: cache, general Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Fix For: ignite-1.5 Currently our distributed atomics can only return boolean flag in case of failed CAS. We need to extend this and add another method returning previous value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1501) Add compare-and-set operation which returns current value in case of failure.
[ https://issues.apache.org/jira/browse/IGNITE-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-1501: Summary: Add compare-and-set operation which returns current value in case of failure. (was: Add compare-and-set operation which returns currnet value in case of failure.) > Add compare-and-set operation which returns current value in case of failure. > - > > Key: IGNITE-1501 > URL: https://issues.apache.org/jira/browse/IGNITE-1501 > Project: Ignite > Issue Type: Task > Components: cache, general >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov > Fix For: ignite-1.5 > > > Currently our distributed atomics can only return boolean flag in case of > failed CAS. We need to extend this and add another method returning previous > value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1501) Add compare-and-set operation which returns currnet value in case of failure.
[ https://issues.apache.org/jira/browse/IGNITE-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802951#comment-14802951 ] Vladimir Ozerov commented on IGNITE-1501: - At the very least, this includes IgniteAtomicLong and IgniteAtomicReferences classes. May be we can also add it to IgniteAtomicStamped, but what to return in this case? IgniteBiTuple? > Add compare-and-set operation which returns currnet value in case of failure. > - > > Key: IGNITE-1501 > URL: https://issues.apache.org/jira/browse/IGNITE-1501 > Project: Ignite > Issue Type: Task > Components: cache, general >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov > Fix For: ignite-1.5 > > > Currently our distributed atomics can only return boolean flag in case of > failed CAS. We need to extend this and add another method returning previous > value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1496) Platform .Net: Add .Net examples
[ https://issues.apache.org/jira/browse/IGNITE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-1496. --- > 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: Vladimir Ozerov > 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] [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=14802991#comment-14802991 ] Ivan Veselovsky commented on IGNITE-586: intermediate review: https://github.com/apache/ignite/pull/98 > [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.4 > > > 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] [Resolved] (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 resolved IGNITE-1494.
---
Assignee: Sergey Kozlov (was: Alexey Goncharuk)
> 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: Sergey Kozlov
>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/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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (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 closed IGNITE-1494.
-
> 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: Sergey Kozlov
>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/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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1452) OptimizedMarshaller.unmarshal hangs in IgniteCacheQueryNodeRestartSelfTest2
[
https://issues.apache.org/jira/browse/IGNITE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov resolved IGNITE-1452.
--
Resolution: Fixed
Added cache futures cancelling before stopping CacheIoManager.
> 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:
[jira] [Closed] (IGNITE-1452) OptimizedMarshaller.unmarshal hangs in IgniteCacheQueryNodeRestartSelfTest2
[
https://issues.apache.org/jira/browse/IGNITE-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov closed IGNITE-1452.
Assignee: (was: Semen Boikov)
> 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
>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]W: [org.apache.ignite:ignite-indexing] at
> o.a.i.i.p
[jira] [Assigned] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov reassigned IGNITE-973:
---
Assignee: Sergi Vladykin (was: Semen Boikov)
Sergi,
I created test (CacheIndexStreamerTest) reproducing this issue. Looks like
there is no issues on cache side, but something goes wrong in offheap indexing.
Could you please take a look.
Thanks
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803196#comment-14803196
]
Lalit Kumar Jha commented on IGNITE-530:
I want to work on this. Can anyone assignt his to me.
As per my underatanding this is to integrate Twitter Streaming API (public
streams) from https://dev.twitter.com/streaming/overview
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data 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-1135) GridPartitionedGetFuture assertion error
[
https://issues.apache.org/jira/browse/IGNITE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803308#comment-14803308
]
Andrey Gura commented on IGNITE-1135:
-
The problem is reproduced again. During debuging I found that {{containsKey}}
call lead to throwing {{AssertionError}} exception in
{{GridCacheContext.addResult}} method because internally {{containsKey}} method
invokes {{getAllAsync}} method with {{skipVals == true}} flag. In some cases
key already exists on node but still has no value (created by preloading demand
worker but not initialized). It seems that {{GirdCacheContext.addResult}}
contains wrong assertion.
PR based on ignite-1.4 branch created: https://github.com/apache/ignite/pull/99
Waiting for TC.
> GridPartitionedGetFuture assertion error
>
>
> Key: IGNITE-1135
> URL: https://issues.apache.org/jira/browse/IGNITE-1135
> 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}
> Failed processing message [senderId=7a07cc81-11e5-42f2-8ffc-184c6c377fc5,
> msg=GridNearGetResponse
> [futId=575ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df,
> miniId=675ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=3, globalTime=1437493884602,
> order=1437493880034], entries=[GridCacheEntryInfo [key=KeyCacheObjectImpl
> [val=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, hasValBytes=true],
> cacheId=414885281, val=null, ttl=0, expireTime=0, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=7, globalTime=1437493884824,
> order=1437493880064], isNew=false, deleted=false]], invalidParts=[],
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], err=null]]
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1811)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.createResultMap(GridPartitionedGetFuture.java:535)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.access$200(GridPartitionedGetFuture.java:45)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture$MiniFuture.onResult(GridPartitionedGetFuture.java:715)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.onResult(GridPartitionedGetFuture.java:234)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearGetResponse(GridDhtAtomicCache.java:2345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1000(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:218)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:216)
> 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.handleMessage(GridCacheIoManager.java:158)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:761)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:724)
> 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}
> In order to reproduce this need to start IgniteComplexHATest (see
> https://github.com/agura/vertx-ignite) and run tests several times. Test
> hangs. Thread dump contains thread that hangs on waiting for future
> completion:
> {noformat}
> "vert.x-worker-thread-3" #4236 prio=5 os_prio=0 tid=0x7f47f43c3800
> nid=0xc2f waiting on condition [0x7f475ebe6000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x
[jira] [Comment Edited] (IGNITE-1135) GridPartitionedGetFuture assertion error
[
https://issues.apache.org/jira/browse/IGNITE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803308#comment-14803308
]
Andrey Gura edited comment on IGNITE-1135 at 9/17/15 5:56 PM:
--
The problem was reproduced again. During debuging I found that {{containsKey}}
call lead to throwing {{AssertionError}} exception in
{{GridCacheContext.addResult}} method because internally {{containsKey}} method
invokes {{getAllAsync}} method with {{skipVals == true}} flag. In some cases
key already exists on node but still has no value (created by preloading demand
worker but not initialized). It seems that {{GirdCacheContext.addResult}}
contains wrong assertion.
PR based on ignite-1.4 branch created: https://github.com/apache/ignite/pull/99
Waiting for TC.
was (Author: agura):
The problem is reproduced again. During debuging I found that {{containsKey}}
call lead to throwing {{AssertionError}} exception in
{{GridCacheContext.addResult}} method because internally {{containsKey}} method
invokes {{getAllAsync}} method with {{skipVals == true}} flag. In some cases
key already exists on node but still has no value (created by preloading demand
worker but not initialized). It seems that {{GirdCacheContext.addResult}}
contains wrong assertion.
PR based on ignite-1.4 branch created: https://github.com/apache/ignite/pull/99
Waiting for TC.
> GridPartitionedGetFuture assertion error
>
>
> Key: IGNITE-1135
> URL: https://issues.apache.org/jira/browse/IGNITE-1135
> 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}
> Failed processing message [senderId=7a07cc81-11e5-42f2-8ffc-184c6c377fc5,
> msg=GridNearGetResponse
> [futId=575ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df,
> miniId=675ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=3, globalTime=1437493884602,
> order=1437493880034], entries=[GridCacheEntryInfo [key=KeyCacheObjectImpl
> [val=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, hasValBytes=true],
> cacheId=414885281, val=null, ttl=0, expireTime=0, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=7, globalTime=1437493884824,
> order=1437493880064], isNew=false, deleted=false]], invalidParts=[],
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], err=null]]
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1811)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.createResultMap(GridPartitionedGetFuture.java:535)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.access$200(GridPartitionedGetFuture.java:45)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture$MiniFuture.onResult(GridPartitionedGetFuture.java:715)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.onResult(GridPartitionedGetFuture.java:234)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearGetResponse(GridDhtAtomicCache.java:2345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1000(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:218)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:216)
> 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.handleMessage(GridCacheIoManager.java:158)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:761)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:724)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> jav
[jira] [Updated] (IGNITE-1502) Move web console to HTTPS protocol.
[ https://issues.apache.org/jira/browse/IGNITE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Ivanov updated IGNITE-1502: -- Summary: Move web console to HTTPS protocol. (was: Move to HTTPS.) > Move web console to HTTPS protocol. > --- > > Key: IGNITE-1502 > URL: https://issues.apache.org/jira/browse/IGNITE-1502 > Project: Ignite > Issue Type: New Feature > Components: UI >Reporter: Nikita Ivanov >Assignee: Alexey Kuznetsov > > I think it makes sense to move to HTTPS since we are dealing with potentially > sensitive user information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1502) Move to HTTPS.
Nikita Ivanov created IGNITE-1502: - Summary: Move to HTTPS. Key: IGNITE-1502 URL: https://issues.apache.org/jira/browse/IGNITE-1502 Project: Ignite Issue Type: New Feature Components: UI Reporter: Nikita Ivanov Assignee: Alexey Kuznetsov I think it makes sense to move to HTTPS since we are dealing with potentially sensitive user information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-973) Failed to get value for key: 13791. at o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
[
https://issues.apache.org/jira/browse/IGNITE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804526#comment-14804526
]
Sergi Vladykin commented on IGNITE-973:
---
Semyon,
I've ran the test in 1.4 with tracing and got the results below. They basically
mean that value was not unswapped into indexing when the key was removed.
To fix this behavior we have two options: either method
IgniteH2Indexing.onUnswap must be called before remove
or cache value must be provided in IgniteH2Indexing.remove (it is null right
now).
{code}
<01:11:29,335><~DBG~>
[idx.store: , 3232, CacheObjectImpl [val=0, hasValBytes=true]]
<01:11:29,335><~DBG~>
[tbl.update: , 3232, CacheObjectImpl [val=0, hasValBytes=true], rmv=, false]
<01:11:29,335><~DBG~>
[idx.onSwap: , 3232]
<01:11:29,335><~DBG~>
[tbl.onSwapUnswap: , 3232, null]
<01:11:34,805><~DBG~> [idx.store: , 3232,
CacheObjectImpl [val=3232, hasValBytes=true]]
<01:11:34,805><~DBG~> [tbl.update: , 3232,
CacheObjectImpl [val=3232, hasValBytes=true], rmv=, false]
<01:11:34,805><~DBG~> [idx.onSwap: , 3232]
<01:11:34,805><~DBG~> [tbl.onSwapUnswap: , 3232, null]
<01:11:34,805><~DBG~> [idx.remove: , 3232, null]
<01:11:34,805><~DBG~> [tbl.update: , 3232, null, rmv=,
true]
{code}
> Failed to get value for key: 13791. at
> o.a.i.i.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> -
>
> Key: IGNITE-973
> URL: https://issues.apache.org/jira/browse/IGNITE-973
> Project: Ignite
> Issue Type: Bug
> Components: SQL
>Affects Versions: sprint-5
>Reporter: Pavel Konstantinov
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: ignite-1.4
>
>
> {code}
> class org.apache.ignite.IgniteException: Failed to get value for key: 13791.
> This can happen due to a long GC pause.
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2AbstractKeyValueRow.getValue(GridH2AbstractKeyValueRow.java:223)
> at org.h2.index.BaseIndex.compareRows(BaseIndex.java:245)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:199)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex.compare(GridH2TreeIndex.java:39)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1336)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap$2.compareTo(GridOffHeapSnapTreeMap.java:1332)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2088)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.attemptUpdate(GridOffHeapSnapTreeMap.java:2203)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.updateUnderRoot(GridOffHeapSnapTreeMap.java:2020)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.update(GridOffHeapSnapTreeMap.java:1901)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:1850)
> at
> org.apache.ignite.internal.util.offheap.unsafe.GridOffHeapSnapTreeMap.put(GridOffHeapSnapTreeMap.java:94)
> {code}
--
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=14804702#comment-14804702
]
Nicholas Dzwill commented on IGNITE-1493:
-
Thank you again, the workaround you suggested made it past the fatal error on
startup.
I am working on obtaining the debugging information that you requested in hopes
of helping shed some light on this issue.
> 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-1135) GridPartitionedGetFuture assertion error
[
https://issues.apache.org/jira/browse/IGNITE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804739#comment-14804739
]
Alexey Goncharuk commented on IGNITE-1135:
--
Andrey,
On the second thought and after looking more at the code I do not think the
assertion change is correct: even when {{skipVals == true}} primary node should
have sent either boolean {{true}} if value was present in the cache, or did not
send en entry at all if entry was not present in the cache.
This is how {{NearGetRequest}} is processed:
{{processNearGetRequest}}
{{GridDhtCacheAdapter#getDhtAsync()}}
{{GridDhtGetFuture#init()}}
eventually we get to
{{GridDhtCacheAdapter#getDhtAllAsync()}}
{{GridCacheAdapter#getAllAsync0}}
Now, {{GridCacheAdapter:1851}} gets executed only if {{val != null}}, otherwise
no entries will be sent to the near node.
We need to debug further to understand how we get {{null}} value on the near
node.
> GridPartitionedGetFuture assertion error
>
>
> Key: IGNITE-1135
> URL: https://issues.apache.org/jira/browse/IGNITE-1135
> 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}
> Failed processing message [senderId=7a07cc81-11e5-42f2-8ffc-184c6c377fc5,
> msg=GridNearGetResponse
> [futId=575ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df,
> miniId=675ef41be41-1a1482a7-e1b9-48c8-9cb7-382fe83792df, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=3, globalTime=1437493884602,
> order=1437493880034], entries=[GridCacheEntryInfo [key=KeyCacheObjectImpl
> [val=7a07cc81-11e5-42f2-8ffc-184c6c377fc5, hasValBytes=true],
> cacheId=414885281, val=null, ttl=0, expireTime=0, ver=GridCacheVersion
> [topVer=48973890, nodeOrderDrId=7, globalTime=1437493884824,
> order=1437493880064], isNew=false, deleted=false]], invalidParts=[],
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], err=null]]
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1811)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.createResultMap(GridPartitionedGetFuture.java:535)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.access$200(GridPartitionedGetFuture.java:45)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture$MiniFuture.onResult(GridPartitionedGetFuture.java:715)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.onResult(GridPartitionedGetFuture.java:234)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearGetResponse(GridDhtAtomicCache.java:2345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1000(GridDhtAtomicCache.java:64)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:218)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$9.apply(GridDhtAtomicCache.java:216)
> 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.handleMessage(GridCacheIoManager.java:158)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:48)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:761)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:724)
> 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}
> In order to reproduce this need to start IgniteComplexHATest (see
> https://github.com/agura/vertx-ignite) and run tests several times. Test
> hangs. Thread dump contains thread that hangs on waiting for future
> completion:
> {noformat}
> "vert.x-worker-thread-3" #4236 prio=5 os_prio=0 tid=0x7f47f43c3800
>
[jira] [Commented] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804880#comment-14804880 ] Pavel Konstantinov commented on IGNITE-1489: Web agent - print out user e-mail after success connection > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1489) Usability issues
[ https://issues.apache.org/jira/browse/IGNITE-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804880#comment-14804880 ] Pavel Konstantinov edited comment on IGNITE-1489 at 9/18/15 2:37 AM: - Web agent - print out user e-mail after successful connection was (Author: pkonstantinov): Web agent - print out user e-mail after success connection > Usability issues > > > Key: IGNITE-1489 > URL: https://issues.apache.org/jira/browse/IGNITE-1489 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: ignite-1.5 > > > Sub-ticket for collecting usability issues -- 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=14804908#comment-14804908 ] Vasiliy Sisko commented on IGNITE-843: -- Implemented: 4, 8, 10, 11, 12, 14, 18 > 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] [Created] (IGNITE-1503) Do not ask user to provide node ID8 for cache details
Pavel Konstantinov created IGNITE-1503:
--
Summary: Do not ask user to provide node ID8 for cache details
Key: IGNITE-1503
URL: https://issues.apache.org/jira/browse/IGNITE-1503
Project: Ignite
Issue Type: Task
Components: UI
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Priority: Trivial
Fix For: ignite-1.5
Currently user must set -id8=NODE_ID8 option to get detailed cache configuration
{code}
cache -c=cache1 -id8=12345678 -a
{code}
Since now cache starts with identical configuration on all nodes we can discard
option '-id8' for getting detailed cache configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1503) visorcmd: Do not ask user to provide node ID8 for cache details
[
https://issues.apache.org/jira/browse/IGNITE-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1503:
---
Summary: visorcmd: Do not ask user to provide node ID8 for cache details
(was: Do not ask user to provide node ID8 for cache details )
> visorcmd: Do not ask user to provide node ID8 for cache details
>
>
> Key: IGNITE-1503
> URL: https://issues.apache.org/jira/browse/IGNITE-1503
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: ignite-1.4
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Trivial
> Fix For: ignite-1.5
>
>
> Currently user must set -id8=NODE_ID8 option to get detailed cache
> configuration
> {code}
> cache -c=cache1 -id8=12345678 -a
> {code}
> Since now cache starts with identical configuration on all nodes we can
> discard option '-id8' for getting detailed cache configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1504) Add cache name to the warning
Pavel Konstantinov created IGNITE-1504:
--
Summary: Add cache name to the warning
Key: IGNITE-1504
URL: https://issues.apache.org/jira/browse/IGNITE-1504
Project: Ignite
Issue Type: Task
Components: UI
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
Priority: Trivial
Fix For: ignite-1.5
I got this warning but I don't understand what cache this warning is about.
Please add cache name.
{code}
[10:58:21,931][WARNING][ignite-#21%sys-tester%][GridDhtPartitionsExchangeFuture]
Retrying preload partition exchange due to timeout [done=false, dummy=false,
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4,
minorTopVer=0], nodeId=2135f8b4, evt=NODE_JOINED], rcvdIds=[],
rmtIds=[dec935df, 0237a5ca], remaining=[dec935df, 0237a5ca], init=true,
initFut=true, ready=true, replied=false, added=true, oldest=dec935df,
oldestOrder=1, evtLatch=0, locNodeOrder=4, locNodeId=2135f8b
4-9633-447e-be13-b7285e76bab3]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804950#comment-14804950 ] Pavel Konstantinov edited comment on IGNITE-1177 at 9/18/15 4:31 AM: - Load metadata from DB: 1) Need to validate package name 2) Load only matched items if filter is set. was (Author: pkonstantinov): 1) Need to validate package name 2) Load only matched items if filter is set. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1177) Implement metadata screen
[ https://issues.apache.org/jira/browse/IGNITE-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804950#comment-14804950 ] Pavel Konstantinov commented on IGNITE-1177: 1) Need to validate package name 2) Load only matched items if filter is set. > Implement metadata screen > - > > Key: IGNITE-1177 > URL: https://issues.apache.org/jira/browse/IGNITE-1177 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.1.4 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.1.4 > > > Implement metadata screen that should: > 1) Add/edit metadata manually. > 2) Import metadata from database metadata. -- 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=14804954#comment-14804954 ] Alexey Kuznetsov commented on IGNITE-843: - Fixed #1, #2. > 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] [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=14804954#comment-14804954 ] Alexey Kuznetsov edited comment on IGNITE-843 at 9/18/15 4:37 AM: -- Fixed #1, #2, #7. was (Author: kuaw26): Fixed #1, #2. > 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-843) Web configuration tools development
[ https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804958#comment-14804958 ] Alexey Kuznetsov commented on IGNITE-843: - >> 13. 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. If dropdown contains more than 5 items then "Select All" and "Clear All" items will be shown. > 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] [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=14804954#comment-14804954 ] Alexey Kuznetsov edited comment on IGNITE-843 at 9/18/15 4:44 AM: -- Fixed #1, #2, #7, #17. was (Author: kuaw26): Fixed #1, #2, #7. > 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] [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=14804958#comment-14804958 ] Alexey Kuznetsov edited comment on IGNITE-843 at 9/18/15 4:44 AM: -- >> 13. 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. If dropdown contains more than 5 items then "Select All" and "Clear All" items will be shown. >> 16.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). On Summary screen we show data source both for XML and Java. As for preview - I think no need to show data source, because it will take too much space. was (Author: kuaw26): >> 13. 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. If dropdown contains more than 5 items then "Select All" and "Clear All" items will be shown. > 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] [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=14804954#comment-14804954 ] Alexey Kuznetsov edited comment on IGNITE-843 at 9/18/15 4:52 AM: -- Fixed #1, #2, #7, #17. Fixed #15 by adding more info into (?) tooltip was (Author: kuaw26): Fixed #1, #2, #7, #17. > 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] [Updated] (IGNITE-582) [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction
[ https://issues.apache.org/jira/browse/IGNITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-582: Fix Version/s: ignite-1.5 > [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction > -- > > Key: IGNITE-582 > URL: https://issues.apache.org/jira/browse/IGNITE-582 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak > Labels: failedtest > Fix For: ignite-1.5 > > > Ticket is related to this issue > http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions. > I added more simple test to the GridCacheTxMultiThreadedAbstractTest. > Original test is also attached to the ticket. Sometimes commit fails with > GridCacheTxOptimisticException, but two threads still can commit duplicated > values so that increment is lost. > see GG-8063 > Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-582) [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction
[ https://issues.apache.org/jira/browse/IGNITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-582: Assignee: Alexey Goncharuk > [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction > -- > > Key: IGNITE-582 > URL: https://issues.apache.org/jira/browse/IGNITE-582 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Assignee: Alexey Goncharuk >Priority: Blocker > Labels: failedtest > Fix For: ignite-1.5 > > > Ticket is related to this issue > http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions. > I added more simple test to the GridCacheTxMultiThreadedAbstractTest. > Original test is also attached to the ticket. Sometimes commit fails with > GridCacheTxOptimisticException, but two threads still can commit duplicated > values so that increment is lost. > see GG-8063 > Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-582) [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction
[ https://issues.apache.org/jira/browse/IGNITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-582: Priority: Blocker (was: Major) > [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction > -- > > Key: IGNITE-582 > URL: https://issues.apache.org/jira/browse/IGNITE-582 > Project: Ignite > Issue Type: Bug >Reporter: Artem Shutak >Priority: Blocker > Labels: failedtest > Fix For: ignite-1.5 > > > Ticket is related to this issue > http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions. > I added more simple test to the GridCacheTxMultiThreadedAbstractTest. > Original test is also attached to the ticket. Sometimes commit fails with > GridCacheTxOptimisticException, but two threads still can commit duplicated > values so that increment is lost. > see GG-8063 > Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1505) Error on stopping cache in visorcmd
Pavel Konstantinov created IGNITE-1505:
--
Summary: Error on stopping cache in visorcmd
Key: IGNITE-1505
URL: https://issues.apache.org/jira/browse/IGNITE-1505
Project: Ignite
Issue Type: Bug
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko
Priority: Minor
Fix For: ignite-1.5
{code}
visor> cache -stop
Time of the snapshot: 09/18/15, 13:31:40
+===+
| # | Name(@) |Mode | Size |
+===+
| 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
| | | | avg: 1.50 |
| | | | max: 3|
+---+-+-+---+
| 1 | c_replicated(@c5) | REPLICATED | min: 0|
| | | | avg: 8121.00 |
| | | | max: 10828|
+---+-+-+---+
| 2 | dcp_1(@c6) | PARTITIONED | min: 0|
| | | | avg: 2700.00 |
| | | | max: 3773 |
+---+-+-+---+
| 3 | dcp_2(@c7) | PARTITIONED | min: 2496 |
| | | | avg: 2672.00 |
| | | | max: 2809 |
+---+-+-+---+
| 4 | dcr_1(@c8) | REPLICATED | min: 0|
| | | | avg: 8075.50 |
| | | | max: 10768|
+---+-+-+---+
| 5 | dcr_2(@c9) | REPLICATED | min: 0|
| | | | avg: 8039.75 |
| | | | max: 10720|
+---+-+-+---+
| 6 | local-nid(@c10) | LOCAL | min: 10792|
| | | | avg: 10792.00 |
| | | | max: 10792|
+---+
Choose cache number ('c' to cancel) [c]: 6
java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not be
empty.
at
org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
at
org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
at
org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
at scala.Option.foreach(Option.scala:245)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
at
scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.collection.immutable.List.foreach(List.scala:381)
at
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
at scala.App$class.main(App.scala:76)
at
org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:315)
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1505) Error on stopping cache in visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov updated IGNITE-1505:
---
Description:
I'm start my tester and trying to stop cache created only on one node and got
{code}
visor> cache -stop
Time of the snapshot: 09/18/15, 13:31:40
+===+
| # | Name(@) |Mode | Size |
+===+
| 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
| | | | avg: 1.50 |
| | | | max: 3|
+---+-+-+---+
| 1 | c_replicated(@c5) | REPLICATED | min: 0|
| | | | avg: 8121.00 |
| | | | max: 10828|
+---+-+-+---+
| 2 | dcp_1(@c6) | PARTITIONED | min: 0|
| | | | avg: 2700.00 |
| | | | max: 3773 |
+---+-+-+---+
| 3 | dcp_2(@c7) | PARTITIONED | min: 2496 |
| | | | avg: 2672.00 |
| | | | max: 2809 |
+---+-+-+---+
| 4 | dcr_1(@c8) | REPLICATED | min: 0|
| | | | avg: 8075.50 |
| | | | max: 10768|
+---+-+-+---+
| 5 | dcr_2(@c9) | REPLICATED | min: 0|
| | | | avg: 8039.75 |
| | | | max: 10720|
+---+-+-+---+
| 6 | local-nid(@c10) | LOCAL | min: 10792|
| | | | avg: 10792.00 |
| | | | max: 10792|
+---+
Choose cache number ('c' to cancel) [c]: 6
java.lang.IllegalArgumentException: Ouch! Argument is invalid: ids must not be
empty.
at
org.apache.ignite.internal.util.GridArgumentCheck.notEmpty(GridArgumentCheck.java:122)
at
org.apache.ignite.internal.cluster.ClusterGroupAdapter.forNodeIds(ClusterGroupAdapter.java:481)
at org.apache.ignite.visor.visor$.groupForDataNode(visor.scala:272)
at
org.apache.ignite.visor.commands.cache.VisorCacheStopCommand.scan(VisorCacheStopCommand.scala:96)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:284)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$cache$1.apply(VisorCacheCommand.scala:274)
at scala.Option.foreach(Option.scala:245)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand.cache(VisorCacheCommand.scala:274)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.cache.VisorCacheCommand$$anonfun$20.apply(VisorCacheCommand.scala:783)
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:214)
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:326)
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:315)
at scala.Function0$class.apply$mcV$sp(Function0.scala:40)
at
scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.collection.immutable.List.foreach(List.scala:381)
at
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
at scala.App$class.main(App.scala:76)
at
org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:315)
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
{code}
was:
{code}
visor> cache -stop
Time of the snapshot: 09/18/15, 13:31:40
+===+
| # | Name(@) |Mode | Size |
+===+
| 0 | c_partitioned3(@c4) | PARTITIONED | min: 0|
| | | | avg: 1.50 |
| | | | max: 3|
+---+-+-+---+
| 1 | c_replicated(@c5) | REPLICATED | min: 0|
| | | | avg: 8121.00 |
| | | | max: 10828|
+---+---
