[GitHub] ignite pull request #3873: IGNITE-5979

[dgarus]

Github user dgarus closed the pull request at:

https://github.com/apache/ignite/pull/3873


---

Re: Dose Iginte implement lock and latch in transaction，and where is the code ？

[Igor Sapego]

Re-sending to dev-list.

Best Regards,
Igor

On Sat, May 19, 2018 at 6:02 PM, zhouxy1123  wrote:

> Dose Iginte implement lock and latch in transaction，and where is the code ？
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

How to run an Ignite node inside Intellij Idea?

[Ray]

I try to run an Ignite ndoe inside Intellij Idea for debug reasons.
I ran the mvn clean install -Pall-java,all-scala,licenses -DskipTests
command from devnotes and it completed without error.
But when I try to run Ignite node from this class CommandLineStartup and
selected default xml config.
But I got following error

Choose configuration file ('c' to cancel) [0]: 0

Using configuration: config/default-config.xml

class org.apache.ignite.IgniteException: Failed to create Ignite component
(consider adding ignite-spring module to classpath) [component=SPRING,
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
at org.apache.ignite.Ignition.start(Ignition.java:355)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create
Ignite component (consider adding ignite-spring module to classpath)
[component=SPRING,
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
at
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
at
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
at
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:742)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:945)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
at org.apache.ignite.Ignition.start(Ignition.java:352)
... 1 more
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
... 8 more
Failed to start grid: Failed to create Ignite component (consider adding
ignite-spring module to classpath) [component=SPRING,
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
Note! You may use 'USER_LIBS' environment variable to specify your
classpath.

Any advice?



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-8551) Web console - User -profile: do not disable the 'Save Changes' button

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-8551:
--

 Summary: Web console - User -profile: do not disable the 'Save 
Changes' button
 Key: IGNITE-8551
 URL: https://issues.apache.org/jira/browse/IGNITE-8551
 Project: Ignite
  Issue Type: Improvement
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


Currently, we disable the Save Changes button in case of an invalid field.
It will be better make the button always enabled and show an error message.



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

[jira] [Created] (IGNITE-8552) Unable to use date as primary key

[Pavel Vinokurov (JIRA)]

Pavel Vinokurov created IGNITE-8552:
---

 Summary: Unable to use date as primary key
 Key: IGNITE-8552
 URL: https://issues.apache.org/jira/browse/IGNITE-8552
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.4
Reporter: Pavel Vinokurov


It' is unable to create cache via ddl:
create table tab(id date primary key, date_field date);

Result:
ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to 
rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
class org.apache.ignite.IgniteCheckedException: Failed to find value class in 
the node classpath (use default marshaller to enable binary objects) : 
SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
at 
org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)




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

[jira] [Created] (IGNITE-8553) Web Console: Double click on table column border make it super wide

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8553:


 Summary: Web Console: Double click on table column border make it 
super wide
 Key: IGNITE-8553
 URL: https://issues.apache.org/jira/browse/IGNITE-8553
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.6


Point mouse between two columns and do a double click.
Column become super wide.
If this a first "pined" column - no scroll will be available.



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

[jira] [Created] (IGNITE-8554) Cache metrics: expose metrics with rebalance info about keys

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8554:


 Summary: Cache metrics: expose metrics with rebalance info about 
keys
 Key: IGNITE-8554
 URL: https://issues.apache.org/jira/browse/IGNITE-8554
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


In order to show info about rebalance progress we need to expose 
estimatedRebalancingKeys and rebalancedKeys metrics.



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

[GitHub] ignite pull request #3897: IGNITE-6538: test 500 times

[Mmuzaf]

Github user Mmuzaf closed the pull request at:

https://github.com/apache/ignite/pull/3897


---

[jira] [Created] (IGNITE-8555) Web console - Admin panel: the users table is partially empty

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-8555:
--

 Summary: Web console - Admin panel: the users table is partially 
empty
 Key: IGNITE-8555
 URL: https://issues.apache.org/jira/browse/IGNITE-8555
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
 Attachments: image-2018-05-22-16-27-52-342.png

 !image-2018-05-22-16-27-52-342.png! 



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

[GitHub] ignite pull request #4044: IGNITE-6538: run 200 times

[Mmuzaf]

GitHub user Mmuzaf opened a pull request:

https://github.com/apache/ignite/pull/4044

IGNITE-6538: run 200 times



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Mmuzaf/ignite ignite-6538

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4044.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 #4044


commit d37470c7a4c76e11aca60adc06d9ff4a4584aa28
Author: Maxim Muzafarov 
Date:   2018-04-22T14:00:01Z

IGNITE-6538: run 200 times




---

RE: control.bat authentication support

[Stanislav Lukyanov]

// Bcc’ed user-list and added dev-list

I think that having stubs for the functionality unavailable in Ignite confuses 
more people.
If someone has extended Ignite’s functionality, as did Oleksandr, that’s great 
– but it’s up to them to also develop the necessary tooling.
But I’ll be happy to hear other opinions.

Thanks,
Stan

From: Alexey Kuznetsov
Sent: 22 мая 2018 г. 12:23
To: u...@ignite.apache.org
Subject: Re: control.bat authentication support

Stan,

I think that we should add support for authentication in control.sh
One more tool will confuse Ignite users.

On Tue, May 22, 2018 at 3:53 AM, Stanislav Lukyanov  
wrote:
Hi,
 
Ignite doesn’t provide built-in support for authentication, so the built-in 
control.bat/sh also don’t have stubs for that. 
So yes, I guess you need to write your own tool.
 
A tool like that would be pretty simple though – just start a client node, 
parse command line arguments and
map them to the methods of the ignite.cluster().
 
Stan
 
From: Olexandr K
Sent: 17 мая 2018 г. 17:09
To: u...@ignite.apache.org
Subject: control.bat authentication support
 
Hi guys,
 
I configured Ignite user/password authentication by adding custom plugin.
It works fine in server/client nodes and visor but I can't find any auth 
support in control.bat
I checked it's source code and don't see any place where I can provide 
credentials.
 
Should I write my own control tool or how can I solve this?
 
BR, Oleksandr
 




-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-8556) Web Console: Improve Webpack DEV mode

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8556:


 Summary: Web Console: Improve Webpack DEV mode
 Key: IGNITE-8556
 URL: https://issues.apache.org/jira/browse/IGNITE-8556
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov






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

[jira] [Created] (IGNITE-8557) Web Console: Webpack add support for SVG images

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8557:


 Summary: Web Console: Webpack add support for SVG images
 Key: IGNITE-8557
 URL: https://issues.apache.org/jira/browse/IGNITE-8557
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.6


In current implementation we forced to store images in special folder and copy 
them via copy plugin. But as we are going towards Angular with components it 
will be better to store images near components (as we do for css).

Lets add such loader to Webpack



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

[jira] [Created] (IGNITE-8558) Provide an opportunity to stop grids and cancel tasks after execution all tests

[Maxim Muzafarov (JIRA)]

Maxim Muzafarov created IGNITE-8558:
---

 Summary: Provide an opportunity to stop grids and cancel tasks 
after execution all tests
 Key: IGNITE-8558
 URL: https://issues.apache.org/jira/browse/IGNITE-8558
 Project: Ignite
  Issue Type: Sub-task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
 Fix For: 2.6


IGNITE-6842 guarantee us stopping all Ignite instances after test completion by 
default and stopping it without cancelling tasks.

User should have abiliti to override this behavior and use stopAllGirds(true) 
after all tests execution.



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

[jira] [Created] (IGNITE-8559) WAL rollOver can be blocked by WAL iterator reservation

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8559:


 Summary: WAL rollOver can be blocked by WAL iterator reservation
 Key: IGNITE-8559
 URL: https://issues.apache.org/jira/browse/IGNITE-8559
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


I've got the following thread dump from one of the Ignite nodes (only 
meaningful threads are kept for simplicity)
WAL archiver is waiting for locked segment release
TX commit is waiting for WAL rollover
WAL rollover is blocked by the archiver
Exchange is blocked by TX commit

{code}
"sys-stripe-55-#56%GRID%GridNodeName%" #246 daemon prio=5 os_prio=0 
tid=0x7fdd1eeff000 nid=0x164252 waiting on condition [0x7fdb36eec000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x7fe0a5e96278> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)
at 
org.apache.ignite.internal.util.IgniteUtils.awaitQuiet(IgniteUtils.java:7400)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.awaitNext(FileWriteAheadLogManager.java:2819)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$2900(FileWriteAheadLogManager.java:2390)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1065)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:715)
at 
org.gridgain.grid.internal.processors.cache.database.snapshot.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:2436)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$9.applyx(GridCacheDatabaseSharedManager.java:942)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$9.applyx(GridCacheDatabaseSharedManager.java:935)
at 
org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1341)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:415)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:409)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:287)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:282)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.insertDataRow(AbstractFreeList.java:509)
at 
org.apache.ignite.internal.processors.cache.persistence.RowStore.addRow(RowStore.java:102)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:1252)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.createRow(GridCacheOffheapManager.java:1370)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:4429)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:4374)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3083)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2977)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1726)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1703)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1703)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1610)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1199)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCache

Re: Upgrading Ignite to JCache 1.1

[Dmitry Pavlov]

Hi Denis,

What was improved in JCache 1.1?

Would it be useful for product to change supported spec. version?

Sincerely,
Dmitriy Pavlov

пн, 21 мая 2018 г. в 20:12, Denis Magda :

> Igniters,
>
> Eventually, JCache was relicensed to Apache 2.0 and released 1.1 version:
> https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU
>
> Is there anyone interested in upgrading Ignite to the new version for the
> next release?
> https://issues.apache.org/jira/browse/IGNITE-8548
>
> --
> Denis
>

[jira] [Created] (IGNITE-8560) Update index validation utility to use statistical check approach

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8560:


 Summary: Update index validation utility to use statistical check 
approach
 Key: IGNITE-8560
 URL: https://issues.apache.org/jira/browse/IGNITE-8560
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


Currently, the check index feature of {{control.sh}} scans the full data set 
which has N * logN complexity. On large data sets this takes too long to 
complete. 

To mitigate this, I suggest to add an option 
* to check either first K entries
* to check each Kth entry




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

[jira] [Created] (IGNITE-8561) SinglSegmentLogicalRecordsIterator is broken

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-8561:
-

 Summary: SinglSegmentLogicalRecordsIterator is broken
 Key: IGNITE-8561
 URL: https://issues.apache.org/jira/browse/IGNITE-8561
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Kalashnikov
Assignee: Anton Kalashnikov






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

[GitHub] ignite pull request #3553: Ignite 7776 - long constants calculation

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3553


---

[GitHub] ignite pull request #4045: IGNITE-8561 in SingleSegmentLogicalRecordsIterato...

[akalash]

GitHub user akalash opened a pull request:

https://github.com/apache/ignite/pull/4045

IGNITE-8561 in SingleSegmentLogicalRecordsIterator changed archivedSe…

…gIdx to curWalSegmIdx from super class

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8561

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4045.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 #4045


commit 64f4ce0232c2504065e6329a2da32ee2704fcc68
Author: Anton Kalashnikov 
Date:   2018-05-22T13:16:52Z

IGNITE-8561 in SingleSegmentLogicalRecordsIterator changed archivedSegIdx 
to curWalSegmIdx from super class




---

[jira] [Created] (IGNITE-8562) Turn system-critical Ignite threads into GridWorkers

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-8562:


 Summary: Turn system-critical Ignite threads into GridWorkers
 Key: IGNITE-8562
 URL: https://issues.apache.org/jira/browse/IGNITE-8562
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Kuznetsov
Assignee: Andrey Kuznetsov
 Fix For: 2.6


The goal of the change is to make system-critical threads (in terms of IEP-14, 
[1]) available to {{WorkersControlMXBean}}.

[1] 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling



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

[GitHub] ignite pull request #4004: IGNITE-8501: Retry on GridServiceNotFoundExceptio...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4004


---

[jira] [Created] (IGNITE-8563) WAL file archiver does not propagate file archiving error to error handler

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8563:


 Summary: WAL file archiver does not propagate file archiving error 
to error handler
 Key: IGNITE-8563
 URL: https://issues.apache.org/jira/browse/IGNITE-8563
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Alexey Goncharuk
 Fix For: 2.6


I observed this error when a disk with WAL archive left out of space:
{code}
...
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:464)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:517)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:940)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:819)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:775)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:97)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:189)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:187)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.ignite.IgniteException: Runtime failure on row: 
Row@1ec13b23[ key: 4458000681143704309, val: 
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2119)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2066)
at 
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:247)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:548)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:480)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:659)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1866)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1393)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1257)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1511)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:352)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3602)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3578)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerSet(GridCacheMapEntry.java:1040)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:652)
... 22 common frames omitted
Caused by: org.apache.ignite.IgniteException: Failed to archive WAL segmen

Re: How to run an Ignite node inside Intellij Idea?

[Alexey Goncharuk]

Hi,

Most likely you are trying to start an Ignite node using XML config in the
scope of ignite-core module. This fails because ignite-core is a standalone
module and does not have a dependency on ignite-spring. You can either
create an IgniteConfiguration instance programmatically instead of XML or
run your test inside the ignite-spring test sources.

--AG

вт, 22 мая 2018 г. в 11:42, Ray :

> I try to run an Ignite ndoe inside Intellij Idea for debug reasons.
> I ran the mvn clean install -Pall-java,all-scala,licenses -DskipTests
> command from devnotes and it completed without error.
> But when I try to run Ignite node from this class CommandLineStartup and
> selected default xml config.
> But I got following error
>
> Choose configuration file ('c' to cancel) [0]: 0
>
> Using configuration: config/default-config.xml
>
> class org.apache.ignite.IgniteException: Failed to create Ignite component
> (consider adding ignite-spring module to classpath) [component=SPRING,
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at
>
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:990)
> at org.apache.ignite.Ignition.start(Ignition.java:355)
> at
>
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create
> Ignite component (consider adding ignite-spring module to classpath)
> [component=SPRING,
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> at
>
> org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
> at
>
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
> at
>
> org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
> at
>
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:742)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:945)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
> at org.apache.ignite.Ignition.start(Ignition.java:352)
> ... 1 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
>
> org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
> ... 8 more
> Failed to start grid: Failed to create Ignite component (consider adding
> ignite-spring module to classpath) [component=SPRING,
> cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
> Note! You may use 'USER_LIBS' environment variable to specify your
> classpath.
>
> Any advice?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #3829: IGNITE-6075 'CacheLoadingConcurrentGridStartSelfT...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3829


---

Re: Lucene CorruptIndexException (checksum failed) on GridLuceneIndex - suggested patch

[Andrew Mashenkov]

Hi Manu,

We've fixed CRC issue, but still can't make reproducer.
Seems, we've missed smth.

Can you share a repro?



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Docker update review

[Petr Ivanov]

Hi, Igniters!


Who can / is willing to help with review and merge of [1]

In this task I have:
 - added new docker image specification for standalone web agent run (for k8s 
like environments);
 - reorganised docker images’ definitions, moving them from disjoint places to 
one.

Changes are tested on Nightly Build configuration [2] and approved by reporter.


[1] https://issues.apache.org/jira/browse/IGNITE-8526
[2] https://ci.ignite.apache.org/viewLog.html?buildId=1320479

Re: Docker update review

[Alexey Kuznetsov]

Andrey,

Could you review Peter's PR?

On Tue, May 22, 2018 at 10:35 PM, Petr Ivanov  wrote:

> Hi, Igniters!
>
>
> Who can / is willing to help with review and merge of [1]
>
> In this task I have:
>  - added new docker image specification for standalone web agent run (for
> k8s like environments);
>  - reorganised docker images’ definitions, moving them from disjoint
> places to one.
>
> Changes are tested on Nightly Build configuration [2] and approved by
> reporter.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8526
> [2] https://ci.ignite.apache.org/viewLog.html?buildId=1320479




-- 
Alexey Kuznetsov

Re: Orphaned, duplicate, and main-class tests!

[Ilya Kasnacheev]

Hello, Igniters!

One moment more of your time. One, we seem to have a consensus now that
tests should be added to suites, but commented out. They should be
uncommented out later, for which numerous tickets will be created. This way
we can tackle.

Another issue sprang up, just now I have discovered an 'ignored-tests'
module. My proposal thus is to:
- Move tests from this suite to relevant suites, comment them out.
- Kill this module (with fire).

Would be glad to her your input,



-- 
Ilya Kasnacheev

2018-05-03 20:03 GMT+03:00 Ilya Kasnacheev :

> Hello Dmitry, igniters!
>
> Still, the policy of removal of unused tests is not clear to me.
>
> We have roughly three groups of such tests:
> - Odd ancient main class tests. I think we can remove those.
> - JVM features/quirks tests (some are main class, some are JUnit tests.
> Reside in package jvmtest. Should we remove these?
> - JUnit "load" tests. Should we kill all of these? I'm asking since you've
> commited such test recently. I think you wanted it to linger. And yet,
> what's our policy? How do I determine whether it's safe to nuke a "load"
> test not in any suite? Or just tuck them in a fake TestSuite and keep?
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-04-24 17:54 GMT+03:00 Dmitry Pavlov :
>
>> I agree with Yakov here. If nobody responds here we can consider we have
>> lazy consensus on removal of tests.
>>
>> I'm going to review PRs from Ilya.
>>
>> вт, 24 апр. 2018 г. в 6:11, Yakov Zhdanov :
>>
>> > Alexey Goncharuk, Vladimir Ozerov, what do you think about these tests?
>> >
>> > I believe they were created as a part of variuos optimization and
>> profiling
>> > activities. I also think we can remove them since nobody cares about
>> them
>> > for too long.
>> >
>> > Thoughts?
>> >
>> > Yakov Zhdanov
>> >
>> > ср, 18 апр. 2018 г., 16:42 Ilya Kasnacheev :
>> >
>> > > Hello!
>> > >
>> > > I've decided to return to this task after a break.
>> > >
>> > > Can you please tell me why do we have main-class tests? Such as
>> > >
>> > > GridBasicPerformanceTest.class,
>> > > GridBenchmarkCacheGetLoadTest.class,
>> > > GridBoundedConcurrentLinkedHashSetLoadTest.class,
>> > > GridCacheDataStructuresLoadTest.class,
>> > > GridCacheReplicatedPreloadUndeploysTest.class,
>> > > GridCacheLoadTest.class,
>> > > GridCacheMultiNodeDataStructureTest.class,
>> > > GridCapacityLoadTest.class,
>> > > GridContinuousOperationsLoadTest.class,
>> > > GridFactoryVmShutdownTest.class,
>> > > GridFutureListenPerformanceTest.class,
>> > > GridFutureQueueTest.class,
>> > > GridGcTimeoutTest.class,
>> > > GridJobExecutionSingleNodeLoadTest.class,
>> > > GridJobExecutionSingleNodeSemaphoreLoadTest.class,
>> > > GridJobLoadTest.class,
>> > > GridMergeSortLoadTest.class,
>> > > GridNioBenchmarkTest.class,
>> > > GridThreadPriorityTest.class,
>> > > GridSystemCurrentTimeMillisTest.class,
>> > > BlockingQueueTest.class,
>> > > MultipleFileIOTest.class,
>> > > GridSingleExecutionTest.class
>> > >
>> > >
>> > > If nobody wants them, how about we delete them in master branch? Start
>> > > afresh?
>> > >
>> > > --
>> > > Ilya Kasnacheev
>> > >
>> > > 2018-02-13 17:02 GMT+03:00 Ilya Kasnacheev > >:
>> > >
>> > > > Anton,
>> > > >
>> > > > >Tests should be attached to appropriate suites
>> > > >
>> > > > This I can do
>> > > >
>> > > > > and muted if necessary, Issues should be created on each mute.
>> > > >
>> > > > This is roughly a week of work. I can't spare that right now. I
>> doubt
>> > > > anyone can.
>> > > >
>> > > > Can we approach this by smaller steps?
>> > > >
>> > > > --
>> > > > Ilya Kasnacheev
>> > > >
>> > > > 2018-02-06 19:55 GMT+03:00 Anton Vinogradov <
>> avinogra...@gridgain.com
>> > >:
>> > > >
>> > > >> Val,
>> > > >>
>> > > >> Tests should be attached to appropriate suites and muted if
>> necessary,
>> > > >> Issues should be created on each mute.
>> > > >>
>> > > >> On Tue, Feb 6, 2018 at 7:23 PM, Valentin Kulichenko <
>> > > >> valentin.kuliche...@gmail.com> wrote:
>> > > >>
>> > > >> > Anton,
>> > > >> >
>> > > >> > I tend to agree with Ilya that identifying and fixing all the
>> > possible
>> > > >> > broken tests in one go is not feasible. What is the proper way in
>> > your
>> > > >> > view? What are you suggesting?
>> > > >> >
>> > > >> > -Val
>> > > >> >
>> > > >> > On Mon, Feb 5, 2018 at 2:18 AM, Anton Vinogradov <
>> > > >> avinogra...@gridgain.com
>> > > >> > >
>> > > >> > wrote:
>> > > >> >
>> > > >> > > Ilya,
>> > > >> > >
>> > > >> > > 1) Still see no reason for such changes. Does this break
>> > something?
>> > > >> > >
>> > > >> > > 2) Looks like you're trying to add Trash*TestSuite.java which
>> will
>> > > >> never
>> > > >> > be
>> > > >> > > refactored.
>> > > >> > > We should do everything in proper way now, not sometime.
>> > > >> > >
>> > > >> > > 3) Your comments looks odd to me.
>> > > >> > > Issue should be resolved in proper way.
>> > > >> > >
>> > > 

[jira] [Created] (IGNITE-8564) DataStreamer fails if client reconnected to the cluster and allowOverride = true

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-8564:
---

 Summary: DataStreamer fails if client reconnected to the cluster 
and allowOverride = true
 Key: IGNITE-8564
 URL: https://issues.apache.org/jira/browse/IGNITE-8564
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Ilya Kasnacheev
Assignee: Ilya Kasnacheev
 Attachments: DataStreamerClientReconnectAfterClusterRestartTest.java

But wait, there's more.

This only happens when client has reconnected to a new cluster and topology 
version after that is exactly the same like when it left.

Please see the attached test.



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

Re: Baseline topology documentation clarified: usage scenarios and definition

[Ivan Rakov]

I used to present some slides introducing baseline topology concept. 
Please feel free to use or change any pictures.

https://docs.google.com/presentation/d/1DVLwlaR0zPIuL5YMkX8MyGLutZw-tvK9InDTCvubAEQ/edit?usp=sharing

Best Regards,
Ivan Rakov

On 18.05.2018 15:20, Dmitriy Setrakyan wrote:

Great docs! Any chance we could add some pictures to illustrate the concept
better.

On Fri, May 18, 2018 at 2:15 AM, Denis Magda  wrote:


Igniters,

With the help of Stanislav Lukyanov and Ivan Rakov, we could make our
baseline topology documentation much better and vivid. Check up the new
sections that did a better job explaining the topology, cover common usage
scenarious and explain how to trigger the rebalancing programmatically if
it's not expected that the baseline topology's node count to be recovered
soon:

- https://apacheignite.readme.io/v2.4/docs/cluster-
activation#section-baseline-topology


- https://apacheignite.readme.io/v2.4/docs/cluster-
activation#section-usage-scenarios


- https://apacheignite.readme.io/v2.4/docs/cluster-
activation#section-triggering-rebalancing-programmatically



--
Denis

Re: Discussion: Upgrade Ignite Spark Module's Spark version to 2.3.0

[Denis Magda]

Thanks, Ray,

Personally, I'm fine with the proposed changes. According to Maven stats
spark-2.10 we have 12x times fewer downloads for ignite-spark-2.10 vs.
ignite-spark. So it sounds reasonable to drop the legacy Spark version in
favor of the Spark 2.3 optimizations.

--
Denis


On Mon, May 21, 2018 at 7:31 PM, Ray  wrote:

> Spark released its newest version 2.3.0 on Feb 28th, so I'd like to open a
> discussion about whether we should upgrade Ignite Spark module to to the
> latest version.
> In the release notes
> https://spark.apache.org/releases/spark-release-2-3-0.html, spark 2.3
> introduced many useful new features and as well as many performance and
> stability changes.
>
> So in the next release, I think we should support the Spark 2.3 in Ignite
> Spark module.
> I already created a ticket in jira
> https://issues.apache.org/jira/browse/IGNITE-8534, and the patch is ready
> for review.
>
> Spark 2.3 dropped support for scala 2.10
> https://issues.apache.org/jira/browse/SPARK-19810, so we also need to
> remove
> spark-2.10 module if we decide to support Spark 2.3.
>
> Please share your input, Igniters.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Upgrading Ignite to JCache 1.1

[Denis Magda]

Here is a list of all changes:
https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU

The primary argument for the migration is a license. JCache 1.0 is licensed
by Oracle that causes legal issues for some of the users. Once we upgrade
to JCache 1.1 the won't longer be a big deal.

However, once we move to 1.1 we need to be sure that we comply with the
updated specification.

--
Denis

On Tue, May 22, 2018 at 5:20 AM, Dmitry Pavlov 
wrote:

> Hi Denis,
>
> What was improved in JCache 1.1?
>
> Would it be useful for product to change supported spec. version?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 21 мая 2018 г. в 20:12, Denis Magda :
>
> > Igniters,
> >
> > Eventually, JCache was relicensed to Apache 2.0 and released 1.1 version:
> > https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU
> >
> > Is there anyone interested in upgrading Ignite to the new version for the
> > next release?
> > https://issues.apache.org/jira/browse/IGNITE-8548
> >
> > --
> > Denis
> >
>

Re: Upgrading Ignite to JCache 1.1

[Dmitriy Setrakyan]

Igniters,

It will be great if someone in the community would pick this up. The amount
of changes are minimal and many of them only have to do with clarifying the
documentation. However, removing JSR 107 license confusion in 1.1 would be
great for Ignite.

D.

On Tue, May 22, 2018 at 3:04 PM, Denis Magda  wrote:

> Here is a list of all changes:
> https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU
>
> The primary argument for the migration is a license. JCache 1.0 is licensed
> by Oracle that causes legal issues for some of the users. Once we upgrade
> to JCache 1.1 the won't longer be a big deal.
>
> However, once we move to 1.1 we need to be sure that we comply with the
> updated specification.
>
> --
> Denis
>
> On Tue, May 22, 2018 at 5:20 AM, Dmitry Pavlov 
> wrote:
>
> > Hi Denis,
> >
> > What was improved in JCache 1.1?
> >
> > Would it be useful for product to change supported spec. version?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 21 мая 2018 г. в 20:12, Denis Magda :
> >
> > > Igniters,
> > >
> > > Eventually, JCache was relicensed to Apache 2.0 and released 1.1
> version:
> > > https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU
> > >
> > > Is there anyone interested in upgrading Ignite to the new version for
> the
> > > next release?
> > > https://issues.apache.org/jira/browse/IGNITE-8548
> > >
> > > --
> > > Denis
> > >
> >
>

[jira] [Created] (IGNITE-8566) Web console: replace extract-text-webpack-plugin with mini-css-extract-plugin

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-8566:


 Summary: Web console: replace extract-text-webpack-plugin with 
mini-css-extract-plugin
 Key: IGNITE-8566
 URL: https://issues.apache.org/jira/browse/IGNITE-8566
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Ilya Borisov
Assignee: Ilya Borisov


The extract-text-webpack-plugin documentations says that "Since webpack v4 the 
extract-text-webpack-plugin should not be used for css. Use 
mini-css-extract-plugin instead.", so I think that's what should be done.



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

RE: Null check removal in IGNITE-5779

[Sunny Chan, CLSA]

Actually I have worked it out:

The null check is actually moved to the loadAll method in CassandraCacheStore 
(https://github.com/apache/ignite/blob/b4a95e7b1574404333912e9cf5564d336fb39130/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/CassandraCacheStore.java#L275).
 What happens is that the code which keep tracks of the number of items being 
processed is implemented in the GenericBatchExecutionAssistant 
(https://github.com/apache/ignite/blob/master/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/GenericBatchExecutionAssistant.java)
 and the null check at CassandraSessionImpl would actually skip the "processed 
count" logic in GenericBatchExecutionAssistant and you will get into an 
infinite loop as the processed count has not been updated.

I think it would be useful to update the JavaDoc for 
BatchExecutionAssistant.process to say that Row can be null (for e.g. when you 
update an entry, Cassandra returns null for row) - is that a good idea?

Thanks.

-Original Message-
From: Dmitry Pavlov [mailto:dpavlov@gmail.com] 
Sent: Tuesday, May 15, 2018 9:08 PM
To: dev@ignite.apache.org; Igor Rudyak 
Cc: igor.rud...@rallyhealth.com
Subject: Re: Null check removal in IGNITE-5779

Hi Igor,

Could you please help with answering to this question?

Sincerely,
Dmitriy Pavlov

вт, 15 мая 2018 г. в 5:18, Sunny Chan, CLSA :

> Hello,
>
>
>
> In Ignite-5779 patch, CassandraSessionImpl.java line 289 a null check 
> for row has been removed (before the change: 
> https://github.com/apache/ignite/blob/924b1faa64026107bf933ba441e743cf
> 52cb94d1/modules/cassandra/store/src/main/java/org/apache/ignite/cache
> /store/cassandra/session/CassandraSessionImpl.java#L289
>
> )
>
>
>
> I cannot tell immediately why the null check is no longer needed, 
> especially the row assignment in line 289 can definitely return a 
> null. Is it a mistake or we are expecting BatchExecutionAssistant is 
> able to deal with null?
>
>
>
> Thanks.
>
>
>
> *Sunny Chan*
>
> *Senior Lead Engineer, Executive Services*
>
> D  +852 2600 8907 <+852%202600%208907>  |  M  +852 6386 1835 
> <+852%206386%201835>  |  T  +852 2600  <+852%202600%20>
>
> 5/F, One Island East, 18 Westlands Road 
> ,
> Island East, Hong Kong
>
>
>
> [image: :1. Social Media Icons:CLSA_Social Media Icons_linkedin.png]
> [image: :1. Social Media 
> Icons:CLSA_Social Media Icons_twitter.png]
> [image: :1. Social Media 
> Icons:CLSA_Social Media Icons_youtube.png]
> [image: :1.
> Social Media Icons:CLSA_Social Media Icons_facebook.png] 
> 
>
>
>
> *clsa.com* 
>
> *Insights. Liquidity. Capital. *
>
>
>
> [image: CLSA_RGB] 
>
>
>
> *A CITIC Securities Company*
>
>
>
> The content of this communication is intended for the recipient and is 
> subject to CLSA Legal and Regulatory Notices.
> These can be viewed at https://www.clsa.com/disclaimer.html or sent to 
> you upon request.
> Please consider before printing. CLSA is ISO14001 certified and 
> committed to reducing its impact on the environment.
>

The content of this communication is intended for the recipient and is subject 
to CLSA Legal and Regulatory Notices.
These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon 
request.
Please consider before printing. CLSA is ISO14001 certified and committed to 
reducing its impact on the environment.

[GitHub] ignite pull request #4020: IGNITE-8525: Support for IgniteZeroMqStreamer non...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4020


---