date:20180122


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

Pavel Konstantinov commented on IGNITE-7238:


Tested

> Web console: incorrect "Download agent" button color
> 
>
> Key: IGNITE-7238
> URL: https://issues.apache.org/jira/browse/IGNITE-7238
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> *How to reproduce:*
> 1. Start demo mode, do not start a web agent.
> 2. Wait for "Connection to Ignite Web Agent is not established" dialog to 
> appear.
> 3. Focus on "Download agent" using Tab button (or any other way).
> *What happens:*
> "Download agent" label becomes red.
> *What should happen:*
> "Download agent" label should remain white.



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

[jira] [Closed] (IGNITE-7238) Web console: incorrect "Download agent" button color


 [ 
https://issues.apache.org/jira/browse/IGNITE-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-7238.
--

> Web console: incorrect "Download agent" button color
> 
>
> Key: IGNITE-7238
> URL: https://issues.apache.org/jira/browse/IGNITE-7238
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> *How to reproduce:*
> 1. Start demo mode, do not start a web agent.
> 2. Wait for "Connection to Ignite Web Agent is not established" dialog to 
> appear.
> 3. Focus on "Download agent" using Tab button (or any other way).
> *What happens:*
> "Download agent" label becomes red.
> *What should happen:*
> "Download agent" label should remain white.



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

[jira] [Updated] (IGNITE-7484) Documentation for new lin reg trainer.


 [ 
https://issues.apache.org/jira/browse/IGNITE-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Babak updated IGNITE-7484:
---
Labels: documentaion  (was: )

> Documentation for new lin reg trainer.
> --
>
> Key: IGNITE-7484
> URL: https://issues.apache.org/jira/browse/IGNITE-7484
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Yury Babak
>Priority: Major
>  Labels: documentaion
>




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

[jira] [Commented] (IGNITE-7420) Too thick modal body


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

Pavel Konstantinov commented on IGNITE-7420:


Tested

> Too thick modal body
> 
>
> Key: IGNITE-7420
> URL: https://issues.apache.org/jira/browse/IGNITE-7420
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
> Attachments: yz0r1o.jpg
>
>
> !yz0r1o.jpg!



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

[jira] [Closed] (IGNITE-7040) Web console: Invalid user table height


 [ 
https://issues.apache.org/jira/browse/IGNITE-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-7040.
--

> Web console: Invalid user table height
> --
>
> Key: IGNITE-7040
> URL: https://issues.apache.org/jira/browse/IGNITE-7040
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> # Filter user list (f.e. to 2 rows)
> # Change period of showed activity metrics.
> Height of table changed to maximum available but show only filtered rows.



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

[jira] [Updated] (IGNITE-7484) Documentation for new lin reg trainer.


 [ 
https://issues.apache.org/jira/browse/IGNITE-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Babak updated IGNITE-7484:
---
Description: We need to add documentation for changes in IGNITE-5217

> Documentation for new lin reg trainer.
> --
>
> Key: IGNITE-7484
> URL: https://issues.apache.org/jira/browse/IGNITE-7484
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>Priority: Major
>  Labels: documentaion
>
> We need to add documentation for changes in IGNITE-5217



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

[jira] [Assigned] (IGNITE-7484) Documentation for new lin reg trainer.


 [ 
https://issues.apache.org/jira/browse/IGNITE-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Babak reassigned IGNITE-7484:
--

Assignee: Anton Dmitriev

> Documentation for new lin reg trainer.
> --
>
> Key: IGNITE-7484
> URL: https://issues.apache.org/jira/browse/IGNITE-7484
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>Priority: Major
>  Labels: documentaion
>




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

[jira] [Commented] (IGNITE-7040) Web console: Invalid user table height


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

Pavel Konstantinov commented on IGNITE-7040:


Tested

> Web console: Invalid user table height
> --
>
> Key: IGNITE-7040
> URL: https://issues.apache.org/jira/browse/IGNITE-7040
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> # Filter user list (f.e. to 2 rows)
> # Change period of showed activity metrics.
> Height of table changed to maximum available but show only filtered rows.



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

[jira] [Commented] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-01-22 Thread Pavel Pereslegin (JIRA)


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

Pavel Pereslegin commented on IGNITE-7472:
--

Hello, [~vozerov].

I can't find test with such name in ignite sources, am I missed something? Or 
it should be created according to this description?

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 2.5
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



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

[jira] [Commented] (IGNITE-6113) Partition eviction prevents exchange from completion

2018-01-22 Thread Pavel Kovalenko (JIRA)


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

Pavel Kovalenko commented on IGNITE-6113:
-

Partition recreation after eviction finish breaks his `updateCounter` which can 
not be safely restored on Rebalance phase due to possible races.

> Partition eviction prevents exchange from completion
> 
>
> Key: IGNITE-6113
> URL: https://issues.apache.org/jira/browse/IGNITE-6113
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Priority: Major
>
> I has waited for 3 hours for completion without any success.
> exchange-worker is blocked.
> {noformat}
> "exchange-worker-#92%DPL_GRID%grid554.ca.sbrf.ru%" #173 prio=5 os_prio=0 
> tid=0x7f0835c2e000 nid=0xb907 runnable [0x7e74ab1d]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7efee630a7c0> (a 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition$1)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.assign(GridDhtPreloader.java:340)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1801)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
>Locked ownable synchronizers:
> - None
> {noformat}
> {noformat}
> "sys-#124%DPL_GRID%grid554.ca.sbrf.ru%" #278 prio=5 os_prio=0 
> tid=0x7e731c02d000 nid=0xbf4d runnable [0x7e734e7f7000]
>java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
> at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
> at sun.nio.ch.IOUtil.write(IOUtil.java:51)
> at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211)
> - locked <0x7f056161bf88> (a java.lang.Object)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.writeBuffer(FileWriteAheadLogManager.java:1829)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.flush(FileWriteAheadLogManager.java:1572)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:1421)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.access$800(FileWriteAheadLogManager.java:1331)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:339)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.beforeReleaseWrite(PageMemoryImpl.java:1287)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1142)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageImpl.releaseWrite(PageImpl.java:167)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:193)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:242)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:119)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.doRemoveFromLeaf(BPlusTree.java:2886)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.removeFromLeaf(BPlusTree.java:2865)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.access$6900(BPlusTree.java:2515)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1607)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
> at 
>

[jira] [Commented] (IGNITE-7485) control.sh utility does not support authentication


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

ASF GitHub Bot commented on IGNITE-7485:


GitHub user macrergate opened a pull request:

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

IGNITE-7485 add support for authentication parameters



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

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

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

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


commit ee446b4079df3ab07db299041607431a6fc99dab
Author: macrergate 
Date:   2018-01-22T10:10:58Z

IGNITE-7485 add support for authentication parameters




> control.sh utility does not support authentication
> --
>
> Key: IGNITE-7485
> URL: https://issues.apache.org/jira/browse/IGNITE-7485
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Currently controls.sh utility does not work if cluster is running under 
> authentication.
> Error is shown:
> Failed to get cluster state.
> Authentication error.
>  
> it is suggested to introduce authentication parameters to the utitlity
> --login LOGIN
> --password PASSWORD
>  
> Main Utility class ( CommandHandler )  is located in ignite-core module 
> currently. 
>  



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

[jira] [Created] (IGNITE-7486) Сache operation failed after transaction rolled back due to deadlock

Alexey Kuznetsov created IGNITE-7486:


 Summary: Сache operation failed after transaction rolled back due 
to deadlock
 Key: IGNITE-7486
 URL: https://issues.apache.org/jira/browse/IGNITE-7486
 Project: Ignite
  Issue Type: Bug
Reporter: Alexey Kuznetsov
 Attachments: CacheOperationAfterTxDeadlockDetectedTest.java

When you have your transaction rolled back due to detected deadlock, you are 
unabled to perform cache operations (in thread where tx was started and rolled 
back), because it leads to TransactionTimeoutException.

The reason of such behavior is that tx thread map (txManager#threadMap) was not 
cleared from tx when roll back occured.

In GridNearTxLocal#onTimeout you can find comment on that :

// Note: if rollback asynchronously on timeout should not clear thread map
// since thread started tx still should be able to see this 
tx.

Cache operation picks up tx from that map and throws exception.



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

[jira] [Created] (IGNITE-7487) .NET: Thin client: Documentation

Pavel Tupitsyn created IGNITE-7487:
--

 Summary: .NET: Thin client: Documentation
 Key: IGNITE-7487
 URL: https://issues.apache.org/jira/browse/IGNITE-7487
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Document .NET Thin Client usage on readme.io



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

[jira] [Commented] (IGNITE-7019) Cluster can not survive after IgniteOOM

2018-01-22 Thread Dmitriy Sorokin (JIRA)


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

Dmitriy Sorokin commented on IGNITE-7019:
-

We discussed possible solutions with [~mcherkasov] and [~avinogradov], and 
chose the following: first, when IOOME occured on page moving from bucket with 
lower index to higher one, we leave page on old bucket; second, we add 
periodical task for looking up such pages (placed on wrong buckets) and 
correcting its placement if possible (no IOOME on page moving).

Also we need reproducer for this bug, I'll make it at first.

> Cluster can not survive after IgniteOOM
> ---
>
> Key: IGNITE-7019
> URL: https://issues.apache.org/jira/browse/IGNITE-7019
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Dmitriy Sorokin
>Priority: Critical
>  Labels: iep-7
> Fix For: 2.5
>
>
> even if we have full sync mode and transactional cache we can't add new nodes 
> if there  was IgniteOOM, after adding new nodes and re-balancing, old nodes 
> can't evict partitions:
> {code}
> [2017-11-17 20:02:24,588][ERROR][sys-#65%DR1%][GridDhtPreloader] Partition 
> eviction failed, this can cause grid hang.
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not enough 
> memory allocated [policyName=100MB_Region_Eviction, size=104.9 MB]
> Consider increasing memory policy size, enabling evictions, adding more nodes 
> to the cluster, reducing number of backups or reducing model size.
> at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:294)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePageNoReuse(DataStructure.java:117)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePage(DataStructure.java:105)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.addStripe(PagesList.java:413)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.getPageForPut(PagesList.java:528)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.put(PagesList.java:617)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.addForRecycle(FreeListImpl.java:582)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.reuseFreePages(BPlusTree.java:3847)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.releaseAll(BPlusTree.java:4106)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.access$6900(BPlusTree.java:3166)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1782)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1567)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1387)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:374)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3233)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:892)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:750)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6639)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> 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:748)
> {code}
> Discussion on the dev list: 
> http://apache-ignite-developers.2346864.n4.nabble.com/How-properly-handle-IgniteOOM-td25288.html



--
This message was sent by Atlassian JIRA

[jira] [Commented] (IGNITE-7485) add support for authentication parameters to control.sh utility


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

Sergey Kosarev commented on IGNITE-7485:


[~avinogradov], Please review my changes.

> add support for authentication parameters to control.sh utility
> ---
>
> Key: IGNITE-7485
> URL: https://issues.apache.org/jira/browse/IGNITE-7485
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Currently controls.sh utility does not work if cluster is running under 
> authentication.
> Error is shown:
> Failed to get cluster state.
> Authentication error.
>  
> it is suggested to introduce authentication parameters to the utitlity
> --login LOGIN
> --password PASSWORD
>  
> Main Utility class ( CommandHandler )  is located in ignite-core module 
> currently. 
>  



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

[jira] [Commented] (IGNITE-7485) add support for authentication parameters to control.sh utility


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

Alexey Kuznetsov commented on IGNITE-7485:
--

[~macrergate] How about use "–user" instead of "--login"?

> add support for authentication parameters to control.sh utility
> ---
>
> Key: IGNITE-7485
> URL: https://issues.apache.org/jira/browse/IGNITE-7485
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Currently controls.sh utility does not work if cluster is running under 
> authentication.
> Error is shown:
> Failed to get cluster state.
> Authentication error.
>  
> it is suggested to introduce authentication parameters to the utitlity
> --login LOGIN
> --password PASSWORD
>  
> Main Utility class ( CommandHandler )  is located in ignite-core module 
> currently. 
>  



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

[jira] [Created] (IGNITE-7488) fix javadoc and license check failures introduced per IGNITE-7284

Oleg Ignatenko created IGNITE-7488:
--

 Summary: fix javadoc and license check failures introduced per 
IGNITE-7284
 Key: IGNITE-7488
 URL: https://issues.apache.org/jira/browse/IGNITE-7488
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Oleg Ignatenko


fix javadoc and license check failures introduced per IGNITE-7284. One example 
is:
{noformat}
[15:22:32][Step 7/7] [WARNING] Javadoc Warnings
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:97:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:117:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:137:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:168:
 warning - @implSpec is an unknown tag.
[15:22:32][Step 7/7] [WARNING] 
/data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:199:
 warning - @implSpec is an unknown tag. {noformat}

and there may be others. Link for Teamcity task to verify that there are no 
violations: 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc



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

[jira] [Assigned] (IGNITE-7488) fix javadoc and license check failures introduced per IGNITE-7284


 [ 
https://issues.apache.org/jira/browse/IGNITE-7488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Ignatenko reassigned IGNITE-7488:
--

Assignee: Stanislav Lukyanov

> fix javadoc and license check failures introduced per IGNITE-7284
> -
>
> Key: IGNITE-7488
> URL: https://issues.apache.org/jira/browse/IGNITE-7488
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Stanislav Lukyanov
>Priority: Major
>
> fix javadoc and license check failures introduced per IGNITE-7284. One 
> example is:
> {noformat}
> [15:22:32][Step 7/7] [WARNING] Javadoc Warnings
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:97:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:117:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:137:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:168:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:199:
>  warning - @implSpec is an unknown tag. {noformat}
> and there may be others. Link for Teamcity task to verify that there are no 
> violations: 
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc



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

[jira] [Commented] (IGNITE-7477) Ignite.NET does not work on Java 9


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

ASF GitHub Bot commented on IGNITE-7477:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-7477 Ignite.NET does not work on Java 9



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

$ git pull https://github.com/ptupitsyn/ignite ignite-7477

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

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


commit c69ce7b5e0339cec245df1ba2246238645d3efcd
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:05:12Z

IGNITE-7477 .NET: Add JVM options to start on Java 9

commit 33ab0cb6cb6daff6fc6e155efc3119e07c8f413d
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:09:34Z

wip

commit a7612ab44e89d3a931eb3fc8a33a53b680d1c3fc
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:20:41Z

Fix Java9Options

commit 98cc21b0c6f852d96c01c49cf3df72a68fa2fd46
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:25:34Z

Fix assert

commit 851567bf6e01bbb5f0677bf54e74278f65d70c84
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:30:31Z

Refactor JVM options cleanup

commit 5c970fea1e34aeed693fd0f4c13f02108b9ea48a
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:50:42Z

wip

commit e1556018c6f2dd0a716cccb523ecb7725432df1a
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:32:58Z

wip java version detect

commit 510601740fb914a3b76bca8a722f5d10cc1d4795
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:37:51Z

wip

commit d090fcae8a07f1ebb0f413a961bcfdcd58629407
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:38:40Z

wip

commit 658accfa5ac4b1a83ea8cecd9bd0376bc28dd9ff
Author: Pavel Tupitsyn 
Date:   2018-01-22T08:53:20Z

wip

commit cb19997cba88f2928a594e1d8dc5f06f43433768
Author: Pavel Tupitsyn 
Date:   2018-01-22T08:55:35Z

wip

commit 4deac669014e93e3cf7d4421245d9a67234d99d1
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:18:22Z

wip IsJava9

commit 45ed0e7220212974088993930d4dd8d36e349d4b
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:22:36Z

Java 9 detection done

commit fe0907b45a4f47f43346fd2a5601a1f238f316ae
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:24:17Z

Fixed

commit 4a0c15a10a17ff9edcab14c9f79e177cecbae045
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:37:07Z

wip

commit e683cff718040ba03bf19e14aed041301e20a7b6
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:40:30Z

JNI_GetDefaultJavaVMInitArgs on Linux / macOS




> Ignite.NET does not work on Java 9
> --
>
> Key: IGNITE-7477
> URL: https://issues.apache.org/jira/browse/IGNITE-7477
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Ignite.NET does not work properly on Java 9 (IGNITE-6730).
> Some additional JVM settings are required:
> {code}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
> {code}



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

[jira] [Assigned] (IGNITE-6113) Partition eviction prevents exchange from completion

2018-01-22 Thread Pavel Kovalenko (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Kovalenko reassigned IGNITE-6113:
---

Assignee: Pavel Kovalenko

> Partition eviction prevents exchange from completion
> 
>
> Key: IGNITE-6113
> URL: https://issues.apache.org/jira/browse/IGNITE-6113
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Pavel Kovalenko
>Priority: Major
>
> I has waited for 3 hours for completion without any success.
> exchange-worker is blocked.
> {noformat}
> "exchange-worker-#92%DPL_GRID%grid554.ca.sbrf.ru%" #173 prio=5 os_prio=0 
> tid=0x7f0835c2e000 nid=0xb907 runnable [0x7e74ab1d]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7efee630a7c0> (a 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition$1)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.assign(GridDhtPreloader.java:340)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1801)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
>Locked ownable synchronizers:
> - None
> {noformat}
> {noformat}
> "sys-#124%DPL_GRID%grid554.ca.sbrf.ru%" #278 prio=5 os_prio=0 
> tid=0x7e731c02d000 nid=0xbf4d runnable [0x7e734e7f7000]
>java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
> at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
> at sun.nio.ch.IOUtil.write(IOUtil.java:51)
> at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211)
> - locked <0x7f056161bf88> (a java.lang.Object)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.writeBuffer(FileWriteAheadLogManager.java:1829)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.flush(FileWriteAheadLogManager.java:1572)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:1421)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.access$800(FileWriteAheadLogManager.java:1331)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:339)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.beforeReleaseWrite(PageMemoryImpl.java:1287)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1142)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageImpl.releaseWrite(PageImpl.java:167)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:193)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:242)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:119)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.doRemoveFromLeaf(BPlusTree.java:2886)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.removeFromLeaf(BPlusTree.java:2865)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.access$6900(BPlusTree.java:2515)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1607)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.removeDown(BPlusTree.java:1574)
> at 
>

[jira] [Updated] (IGNITE-7485) add support for authentication parameters to control.sh utility


 [ 
https://issues.apache.org/jira/browse/IGNITE-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Kosarev updated IGNITE-7485:
---
Summary: add support for authentication parameters to control.sh utility  
(was: control.sh utility does not support authentication)

> add support for authentication parameters to control.sh utility
> ---
>
> Key: IGNITE-7485
> URL: https://issues.apache.org/jira/browse/IGNITE-7485
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Currently controls.sh utility does not work if cluster is running under 
> authentication.
> Error is shown:
> Failed to get cluster state.
> Authentication error.
>  
> it is suggested to introduce authentication parameters to the utitlity
> --login LOGIN
> --password PASSWORD
>  
> Main Utility class ( CommandHandler )  is located in ignite-core module 
> currently. 
>  



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

[jira] [Comment Edited] (IGNITE-6113) Partition eviction prevents exchange from completion

2018-01-22 Thread Pavel Kovalenko (JIRA)


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

Pavel Kovalenko edited comment on IGNITE-6113 at 1/22/18 9:59 AM:
--

Partition recreation after eviction finish breaks his `updateCounter` which can 
not be safely restored on Rebalance phase due to possible races. We should not 
destroy partition after eviction.


was (Author: jokser):
Partition recreation after eviction finish breaks his `updateCounter` which can 
not be safely restored on Rebalance phase due to possible races.

> Partition eviction prevents exchange from completion
> 
>
> Key: IGNITE-6113
> URL: https://issues.apache.org/jira/browse/IGNITE-6113
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Priority: Major
>
> I has waited for 3 hours for completion without any success.
> exchange-worker is blocked.
> {noformat}
> "exchange-worker-#92%DPL_GRID%grid554.ca.sbrf.ru%" #173 prio=5 os_prio=0 
> tid=0x7f0835c2e000 nid=0xb907 runnable [0x7e74ab1d]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7efee630a7c0> (a 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition$1)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.assign(GridDhtPreloader.java:340)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1801)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
>Locked ownable synchronizers:
> - None
> {noformat}
> {noformat}
> "sys-#124%DPL_GRID%grid554.ca.sbrf.ru%" #278 prio=5 os_prio=0 
> tid=0x7e731c02d000 nid=0xbf4d runnable [0x7e734e7f7000]
>java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
> at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
> at sun.nio.ch.IOUtil.write(IOUtil.java:51)
> at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211)
> - locked <0x7f056161bf88> (a java.lang.Object)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.writeBuffer(FileWriteAheadLogManager.java:1829)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.flush(FileWriteAheadLogManager.java:1572)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:1421)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.access$800(FileWriteAheadLogManager.java:1331)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:339)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.beforeReleaseWrite(PageMemoryImpl.java:1287)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1142)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageImpl.releaseWrite(PageImpl.java:167)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:193)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:242)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:119)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.doRemoveFromLeaf(BPlusTree.java:2886)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.removeFromLeaf(BPlusTree.java:2865)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree$Remove.access$6900(BPlusTree.java:2515)
> at 
>

[jira] [Commented] (IGNITE-7485) add support for authentication parameters to control.sh utility


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

Sergey Kosarev commented on IGNITE-7485:


TC Run

https://ci.ignite.apache.org/viewQueued.html?itemId=1053368

> add support for authentication parameters to control.sh utility
> ---
>
> Key: IGNITE-7485
> URL: https://issues.apache.org/jira/browse/IGNITE-7485
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Currently controls.sh utility does not work if cluster is running under 
> authentication.
> Error is shown:
> Failed to get cluster state.
> Authentication error.
>  
> it is suggested to introduce authentication parameters to the utitlity
> --login LOGIN
> --password PASSWORD
>  
> Main Utility class ( CommandHandler )  is located in ignite-core module 
> currently. 
>  



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

[jira] [Commented] (IGNITE-6810) ODBC: Add secure connection support

2018-01-22 Thread Sergey Kalashnikov (JIRA)


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

Sergey Kalashnikov commented on IGNITE-6810:


[~isapego], I did the review. The changes look good to me.

BTW, can we add the test where server rejects the client certificate?

> ODBC: Add secure connection support
> ---
>
> Key: IGNITE-6810
> URL: https://issues.apache.org/jira/browse/IGNITE-6810
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>  Labels: odbc
> Fix For: 2.5
>
> Attachments: new-ui.png
>
>
> Need to add support of SSL/TLS for ODBC.



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

[jira] [Created] (IGNITE-7485) control.sh utility does not support authentication

Sergey Kosarev created IGNITE-7485:
--

 Summary: control.sh utility does not support authentication
 Key: IGNITE-7485
 URL: https://issues.apache.org/jira/browse/IGNITE-7485
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Sergey Kosarev
Assignee: Sergey Kosarev


Currently controls.sh utility does not work if cluster is running under 
authentication.

Error is shown:

Failed to get cluster state.
Authentication error.

 

it is suggested to introduce authentication parameters to the utitlity

--login LOGIN

--password PASSWORD

 

Main Utility class ( CommandHandler )  is located in ignite-core module 
currently. 

 



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

[jira] [Comment Edited] (IGNITE-7477) Ignite.NET does not work on Java 9


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

Pavel Tupitsyn edited comment on IGNITE-7477 at 1/22/18 9:47 AM:
-

GitHub user ptupitsyn opened a pull request:

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

IGNITE-7477 Ignite.NET does not work on Java 9



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

$ git pull https://github.com/ptupitsyn/ignite ignite-7477

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

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


was (Author: githubbot):
GitHub user ptupitsyn opened a pull request:

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

IGNITE-7477 Ignite.NET does not work on Java 9



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

$ git pull https://github.com/ptupitsyn/ignite ignite-7477

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

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


commit c69ce7b5e0339cec245df1ba2246238645d3efcd
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:05:12Z

IGNITE-7477 .NET: Add JVM options to start on Java 9

commit 33ab0cb6cb6daff6fc6e155efc3119e07c8f413d
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:09:34Z

wip

commit a7612ab44e89d3a931eb3fc8a33a53b680d1c3fc
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:20:41Z

Fix Java9Options

commit 98cc21b0c6f852d96c01c49cf3df72a68fa2fd46
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:25:34Z

Fix assert

commit 851567bf6e01bbb5f0677bf54e74278f65d70c84
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:30:31Z

Refactor JVM options cleanup

commit 5c970fea1e34aeed693fd0f4c13f02108b9ea48a
Author: Pavel Tupitsyn 
Date:   2018-01-19T14:50:42Z

wip

commit e1556018c6f2dd0a716cccb523ecb7725432df1a
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:32:58Z

wip java version detect

commit 510601740fb914a3b76bca8a722f5d10cc1d4795
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:37:51Z

wip

commit d090fcae8a07f1ebb0f413a961bcfdcd58629407
Author: Pavel Tupitsyn 
Date:   2018-01-19T15:38:40Z

wip

commit 658accfa5ac4b1a83ea8cecd9bd0376bc28dd9ff
Author: Pavel Tupitsyn 
Date:   2018-01-22T08:53:20Z

wip

commit cb19997cba88f2928a594e1d8dc5f06f43433768
Author: Pavel Tupitsyn 
Date:   2018-01-22T08:55:35Z

wip

commit 4deac669014e93e3cf7d4421245d9a67234d99d1
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:18:22Z

wip IsJava9

commit 45ed0e7220212974088993930d4dd8d36e349d4b
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:22:36Z

Java 9 detection done

commit fe0907b45a4f47f43346fd2a5601a1f238f316ae
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:24:17Z

Fixed

commit 4a0c15a10a17ff9edcab14c9f79e177cecbae045
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:37:07Z

wip

commit e683cff718040ba03bf19e14aed041301e20a7b6
Author: Pavel Tupitsyn 
Date:   2018-01-22T09:40:30Z

JNI_GetDefaultJavaVMInitArgs on Linux / macOS




> Ignite.NET does not work on Java 9
> --
>
> Key: IGNITE-7477
> URL: https://issues.apache.org/jira/browse/IGNITE-7477
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Ignite.NET does not work properly on Java 9 (IGNITE-6730).
> Some additional JVM settings are required:
> {code}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
> {code}



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

[jira] [Commented] (IGNITE-6810) ODBC: Add secure connection support

2018-01-22 Thread Igor Sapego (JIRA)


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

Igor Sapego commented on IGNITE-6810:
-

Thanks for review, guys.

> ODBC: Add secure connection support
> ---
>
> Key: IGNITE-6810
> URL: https://issues.apache.org/jira/browse/IGNITE-6810
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>  Labels: odbc
> Fix For: 2.5
>
> Attachments: new-ui.png
>
>
> Need to add support of SSL/TLS for ODBC.



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

[jira] [Commented] (IGNITE-6810) ODBC: Add secure connection support

2018-01-22 Thread Igor Sapego (JIRA)


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

Igor Sapego commented on IGNITE-6810:
-

[~skalashnikov], yeah, I guess, we can.

> ODBC: Add secure connection support
> ---
>
> Key: IGNITE-6810
> URL: https://issues.apache.org/jira/browse/IGNITE-6810
> Project: Ignite
>  Issue Type: New Feature
>  Components: odbc
>Affects Versions: 2.3
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>  Labels: odbc
> Fix For: 2.5
>
> Attachments: new-ui.png
>
>
> Need to add support of SSL/TLS for ODBC.



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

[jira] [Resolved] (IGNITE-7003) Ability to disable WAL (Non recoverable case)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-7003.
-
Resolution: Fixed

> Ability to disable WAL (Non recoverable case)
> -
>
> Key: IGNITE-7003
> URL: https://issues.apache.org/jira/browse/IGNITE-7003
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache, persistence, sql
>Reporter: Anton Vinogradov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.4
>
>
> 1) WAL should be disabled by custom discovery message 
> - without triggering exchange,
> - without triggering checkpoint (since it's non recoverable case)
> In case someone is trying to disable already disabled WAL he should be 
> notified that WAL already disabled
> Only cachegroups containing one cache can de disabled
> 2) WAL should be prepared to be enabled by custom discovery message with 
> - triggering exchange, 
> - disabling cache proxies,
> - waiting for checkpoints at every node.
> In case someone is trying to enable already enablling WAL he should be 
> notified that enabling in progress.
> 3) WAL should be enabled by custom discovery message 
> - without triggering exchange
> but
> - with enabling proxies 
> once all nodes finished their checkpoints.
> Failover:
> On any failure during loading (while WAL disabled or enabling) we should be 
> able to reactivate cluster without affected caches content.
> Originating node fail should be covered (at WAL disabled and enabling cases)
> API:
> Public API should be located at IgniteCluster



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

[jira] [Created] (IGNITE-7494) WAL management commands for control.sh script

Vladimir Ozerov created IGNITE-7494:
---

 Summary: WAL management commands for control.sh script
 Key: IGNITE-7494
 URL: https://issues.apache.org/jira/browse/IGNITE-7494
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.5


Need to add WAL mode management commands for {{control.sh}} script:
- enableWal
- disableWal
- isWalEnabled

See {{IgniteCluster}} API.



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

[jira] [Resolved] (IGNITE-6411) Add ability to disable WAL for ceratin caches in runtime


 [ 
https://issues.apache.org/jira/browse/IGNITE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-6411.
-
Resolution: Fixed

> Add ability to disable WAL for ceratin caches in runtime
> 
>
> Key: IGNITE-6411
> URL: https://issues.apache.org/jira/browse/IGNITE-6411
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: iep-1, performance
> Fix For: 2.5
>
>
> Currently every cache update require write to WAL. When doing bulk data load 
> usually crash recovery is not needed. If something went wrong during data 
> load, we should simply purge all intermediate data on cache restart.
> It makes sense to add ability to disable WAL for ceratin caches. Depending on 
> restrictions of current architecture, it could be done on per-cache, 
> per-cache-group or per-memory-policy level.



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

[jira] [Updated] (IGNITE-7003) Ability to disable WAL (Non recoverable case)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7003:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-6411)

> Ability to disable WAL (Non recoverable case)
> -
>
> Key: IGNITE-7003
> URL: https://issues.apache.org/jira/browse/IGNITE-7003
> Project: Ignite
>  Issue Type: Task
>  Components: cache, persistence, sql
>Reporter: Anton Vinogradov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.4
>
>
> 1) WAL should be disabled by custom discovery message 
> - without triggering exchange,
> - without triggering checkpoint (since it's non recoverable case)
> In case someone is trying to disable already disabled WAL he should be 
> notified that WAL already disabled
> Only cachegroups containing one cache can de disabled
> 2) WAL should be prepared to be enabled by custom discovery message with 
> - triggering exchange, 
> - disabling cache proxies,
> - waiting for checkpoints at every node.
> In case someone is trying to enable already enablling WAL he should be 
> notified that enabling in progress.
> 3) WAL should be enabled by custom discovery message 
> - without triggering exchange
> but
> - with enabling proxies 
> once all nodes finished their checkpoints.
> Failover:
> On any failure during loading (while WAL disabled or enabling) we should be 
> able to reactivate cluster without affected caches content.
> Originating node fail should be covered (at WAL disabled and enabling cases)
> API:
> Public API should be located at IgniteCluster



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

[jira] [Updated] (IGNITE-7005) Ability to disable WAL (Recoverable case)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7005:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-6411)

> Ability to disable WAL (Recoverable case)
> -
>
> Key: IGNITE-7005
> URL: https://issues.apache.org/jira/browse/IGNITE-7005
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.5
>
>
> In addition to non recoverable case(IGNITE-7003):
> On WAL disabling we should (on each node)
> - trigger exchange to guarantie consistent state
> - schedule new checkpoint. This checkpoint should be recorded to special 
> place (temporary checkpoint location), to prevent damage of latest one.
> All new checkpoints should update temporary checkpoint.
> On WAL enabling we should (on each node) after all nodes reported that 
> checkpoints finished
> - merge temp checkpoint with stable (scheduled before WAL disabling)
> - clean WAL
> before enabling proxies 
> On any failure during loading (while WAL disabled or enabling) we should be 
> able to reactivate cluster with
> - data from original checkpoints & WAL for affected caches
> - latest state for non affected caches
> Failover:
> Any topology change should be covered(while WAL disabled or enabling)
> - Node(s) Left (inc. coordinator)
> - Node(s) Join



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

[jira] [Updated] (IGNITE-7003) Ability to disable WAL (Non recoverable case)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7003:

Issue Type: New Feature  (was: Task)

> Ability to disable WAL (Non recoverable case)
> -
>
> Key: IGNITE-7003
> URL: https://issues.apache.org/jira/browse/IGNITE-7003
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache, persistence, sql
>Reporter: Anton Vinogradov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.4
>
>
> 1) WAL should be disabled by custom discovery message 
> - without triggering exchange,
> - without triggering checkpoint (since it's non recoverable case)
> In case someone is trying to disable already disabled WAL he should be 
> notified that WAL already disabled
> Only cachegroups containing one cache can de disabled
> 2) WAL should be prepared to be enabled by custom discovery message with 
> - triggering exchange, 
> - disabling cache proxies,
> - waiting for checkpoints at every node.
> In case someone is trying to enable already enablling WAL he should be 
> notified that enabling in progress.
> 3) WAL should be enabled by custom discovery message 
> - without triggering exchange
> but
> - with enabling proxies 
> once all nodes finished their checkpoints.
> Failover:
> On any failure during loading (while WAL disabled or enabling) we should be 
> able to reactivate cluster without affected caches content.
> Originating node fail should be covered (at WAL disabled and enabling cases)
> API:
> Public API should be located at IgniteCluster



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

[jira] [Updated] (IGNITE-7005) Ability to disable WAL (Recoverable case)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7005:

Fix Version/s: 2.5

> Ability to disable WAL (Recoverable case)
> -
>
> Key: IGNITE-7005
> URL: https://issues.apache.org/jira/browse/IGNITE-7005
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.5
>
>
> In addition to non recoverable case(IGNITE-7003):
> On WAL disabling we should (on each node)
> - trigger exchange to guarantie consistent state
> - schedule new checkpoint. This checkpoint should be recorded to special 
> place (temporary checkpoint location), to prevent damage of latest one.
> All new checkpoints should update temporary checkpoint.
> On WAL enabling we should (on each node) after all nodes reported that 
> checkpoints finished
> - merge temp checkpoint with stable (scheduled before WAL disabling)
> - clean WAL
> before enabling proxies 
> On any failure during loading (while WAL disabled or enabling) we should be 
> able to reactivate cluster with
> - data from original checkpoints & WAL for affected caches
> - latest state for non affected caches
> Failover:
> Any topology change should be covered(while WAL disabled or enabling)
> - Node(s) Left (inc. coordinator)
> - Node(s) Join



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

[jira] [Updated] (IGNITE-7004) Ability to disable WAL (Cross-cache tx should be rescricted while WAL disabled)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7004:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-6411)

> Ability to disable WAL (Cross-cache tx should be rescricted while WAL 
> disabled)
> ---
>
> Key: IGNITE-7004
> URL: https://issues.apache.org/jira/browse/IGNITE-7004
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Anton Vinogradov
>Priority: Major
> Fix For: 2.5
>
>
> Cross-cache transactions affecting caches with different modes (e.g. one 
> enabled, another disabled) are not allowed



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

[jira] [Updated] (IGNITE-7415) Ability to disable WAL (Documentation)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7415:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-6411)

> Ability to disable WAL (Documentation)
> --
>
> Key: IGNITE-7415
> URL: https://issues.apache.org/jira/browse/IGNITE-7415
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Anton Vinogradov
>Priority: Major
> Fix For: 2.4
>
>
> Need to update
> [https://apacheignite.readme.io/docs/write-ahead-log#section-wal-modes]
> [https://apacheignite.readme.io/docs/data-loading]



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

[jira] [Updated] (IGNITE-7004) Ability to disable WAL (Cross-cache tx should be rescricted while WAL disabled)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7004:

Fix Version/s: 2.5

> Ability to disable WAL (Cross-cache tx should be rescricted while WAL 
> disabled)
> ---
>
> Key: IGNITE-7004
> URL: https://issues.apache.org/jira/browse/IGNITE-7004
> Project: Ignite
>  Issue Type: Sub-task
>  Components: persistence
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.5
>
>
> Cross-cache transactions affecting caches with different modes (e.g. one 
> enabled, another disabled) are not allowed



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

[jira] [Assigned] (IGNITE-7415) Ability to disable WAL (Documentation)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-7415:
---

Assignee: Vladimir Ozerov

> Ability to disable WAL (Documentation)
> --
>
> Key: IGNITE-7415
> URL: https://issues.apache.org/jira/browse/IGNITE-7415
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Anton Vinogradov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.4
>
>
> Need to update
> [https://apacheignite.readme.io/docs/write-ahead-log#section-wal-modes]
> [https://apacheignite.readme.io/docs/data-loading]



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

[jira] [Updated] (IGNITE-7493) .NET: Propagate WAL management API


 [ 
https://issues.apache.org/jira/browse/IGNITE-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7493:
---
Labels: .NET  (was: )

> .NET: Propagate WAL management API
> --
>
> Key: IGNITE-7493
> URL: https://issues.apache.org/jira/browse/IGNITE-7493
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Need to add the following methods to .NET:
> {code}
> ICluster.disableWal member is missing in .NET.
> ICluster.enableWal member is missing in .NET.
> ICluster.isWalEnabled member is missing in .NET.
> {code}



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

[jira] [Updated] (IGNITE-7493) .NET: Propagate WAL management API


 [ 
https://issues.apache.org/jira/browse/IGNITE-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7493:
---
Description: 
Add the following methods to .NET:
{code}
ICluster.disableWal member is missing in .NET.
ICluster.enableWal member is missing in .NET.
ICluster.isWalEnabled member is missing in .NET.
{code}

  was:
Need to add the following methods to .NET:
{code}
ICluster.disableWal member is missing in .NET.
ICluster.enableWal member is missing in .NET.
ICluster.isWalEnabled member is missing in .NET.
{code}


> .NET: Propagate WAL management API
> --
>
> Key: IGNITE-7493
> URL: https://issues.apache.org/jira/browse/IGNITE-7493
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Add the following methods to .NET:
> {code}
> ICluster.disableWal member is missing in .NET.
> ICluster.enableWal member is missing in .NET.
> ICluster.isWalEnabled member is missing in .NET.
> {code}



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

[jira] [Updated] (IGNITE-7495) Ability to disable WAL globally for data region


 [ 
https://issues.apache.org/jira/browse/IGNITE-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7495:

Description: 
Recently we introduced a set of commands to control WAL state of particular 
caches. I.e. using SQL API user could do the following to disable WAL in order 
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}

Now consider that user has a lot of tables and would like to disable WAL for 
the whole data region at once (e.g. to load data for the whole schema). 
Currently to achieve this he would have to issue a number of commands for each 
and every table. 

Instead, we should provide tiered approach, when user could disable WAL for 
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING;   // Disable for table
{code}

*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be 
possible to have a data region with disabled WAL, while still being able to 
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
handling.

  was:
Recently we introduced a set of commands to control WAL state of particular 
caches. I.e. using SQL API user could do the following to disable WAL in order 
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}

Now consider that user has a lot of tables and would like to disable WAL for 
the whole data region at once (e.g. to load data for the whole schema). 
Currently to achieve this he would have to issue a number of commands for each 
and every table. 

Instead, we should provide tiered approach, when user could disable WAL for 
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING; // Disable for table
{code}

*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be 
possible to have a data region with disabled WAL, while still being able to 
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
handling.


> Ability to disable WAL globally for data region
> ---
>
> Key: IGNITE-7495
> URL: https://issues.apache.org/jira/browse/IGNITE-7495
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 2.5
>
>
> Recently we introduced a set of commands to control WAL state of particular 
> caches. I.e. using SQL API user could do the following to disable WAL in 
> order to speedup data load:
> {code}
> ALTER TABLE my_table NOLOGGING
> {code}
> Now consider that user has a lot of tables and would like to disable WAL for 
> the whole data region at once (e.g. to load data for the whole schema). 
> Currently to achieve this he would have to issue a number of commands for 
> each and every table. 
> Instead, we should provide tiered approach, when user could disable WAL for 
> both cache and data region. Proposed commands:
> {code}
> ALTER DATA REGION my_region NOLOGGING; // Disable for region
> ALTER TABLE my_table NOLOGGING;   // Disable for table
> {code}
> *NOTE*
> Semantics of tiered behaviour should be designed carefully. E.g. it should be 
> possible to have a data region with disabled WAL, while still being able to 
> have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
> handling.



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

[jira] [Updated] (IGNITE-7495) Ability to disable WAL globally for data region


 [ 
https://issues.apache.org/jira/browse/IGNITE-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7495:

Description: 
Recently we introduced a set of commands to control WAL state of particular 
caches. I.e. using SQL API user could do the following to disable WAL in order 
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}

Now consider that user has a lot of tables and would like to disable WAL for 
the whole data region at once (e.g. to load data for the whole schema). 
Currently to achieve this he would have to issue a number of commands for each 
and every table. 

Instead, we should provide tiered approach, when user could disable WAL for 
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING;// Disable for table
{code}

*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be 
possible to have a data region with disabled WAL, while still being able to 
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
handling.

  was:
Recently we introduced a set of commands to control WAL state of particular 
caches. I.e. using SQL API user could do the following to disable WAL in order 
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}

Now consider that user has a lot of tables and would like to disable WAL for 
the whole data region at once (e.g. to load data for the whole schema). 
Currently to achieve this he would have to issue a number of commands for each 
and every table. 

Instead, we should provide tiered approach, when user could disable WAL for 
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING;   // Disable for table
{code}

*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be 
possible to have a data region with disabled WAL, while still being able to 
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
handling.


> Ability to disable WAL globally for data region
> ---
>
> Key: IGNITE-7495
> URL: https://issues.apache.org/jira/browse/IGNITE-7495
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 2.5
>
>
> Recently we introduced a set of commands to control WAL state of particular 
> caches. I.e. using SQL API user could do the following to disable WAL in 
> order to speedup data load:
> {code}
> ALTER TABLE my_table NOLOGGING
> {code}
> Now consider that user has a lot of tables and would like to disable WAL for 
> the whole data region at once (e.g. to load data for the whole schema). 
> Currently to achieve this he would have to issue a number of commands for 
> each and every table. 
> Instead, we should provide tiered approach, when user could disable WAL for 
> both cache and data region. Proposed commands:
> {code}
> ALTER DATA REGION my_region NOLOGGING; // Disable for region
> ALTER TABLE my_table NOLOGGING;// Disable for table
> {code}
> *NOTE*
> Semantics of tiered behaviour should be designed carefully. E.g. it should be 
> possible to have a data region with disabled WAL, while still being able to 
> have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
> handling.



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

[jira] [Created] (IGNITE-7495) Ability to disable WAL globally for data region

Vladimir Ozerov created IGNITE-7495:
---

 Summary: Ability to disable WAL globally for data region
 Key: IGNITE-7495
 URL: https://issues.apache.org/jira/browse/IGNITE-7495
 Project: Ignite
  Issue Type: New Feature
  Components: cache
Reporter: Vladimir Ozerov
 Fix For: 2.5


Recently we introduced a set of commands to control WAL state of particular 
caches. I.e. using SQL API user could do the following to disable WAL in order 
to speedup data load:
{code}
ALTER TABLE my_table NOLOGGING
{code}

Now consider that user has a lot of tables and would like to disable WAL for 
the whole data region at once (e.g. to load data for the whole schema). 
Currently to achieve this he would have to issue a number of commands for each 
and every table. 

Instead, we should provide tiered approach, when user could disable WAL for 
both cache and data region. Proposed commands:
{code}
ALTER DATA REGION my_region NOLOGGING; // Disable for region
ALTER TABLE my_table NOLOGGING; // Disable for table
{code}

*NOTE*
Semantics of tiered behaviour should be designed carefully. E.g. it should be 
possible to have a data region with disabled WAL, while still being able to 
have a cache in it with enabled WAL. Please refer to Oracle's {{NOLOGGING}} 
handling.



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

[jira] [Closed] (IGNITE-6411) Add ability to disable WAL for ceratin caches in runtime


 [ 
https://issues.apache.org/jira/browse/IGNITE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-6411.
---

> Add ability to disable WAL for ceratin caches in runtime
> 
>
> Key: IGNITE-6411
> URL: https://issues.apache.org/jira/browse/IGNITE-6411
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: iep-1, performance
> Fix For: 2.5
>
>
> Currently every cache update require write to WAL. When doing bulk data load 
> usually crash recovery is not needed. If something went wrong during data 
> load, we should simply purge all intermediate data on cache restart.
> It makes sense to add ability to disable WAL for ceratin caches. Depending on 
> restrictions of current architecture, it could be done on per-cache, 
> per-cache-group or per-memory-policy level.



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

[jira] [Created] (IGNITE-7493) Propagate WAL management API to .NET

Vladimir Ozerov created IGNITE-7493:
---

 Summary: Propagate WAL management API to .NET
 Key: IGNITE-7493
 URL: https://issues.apache.org/jira/browse/IGNITE-7493
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Vladimir Ozerov
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Need to add the following methods to .NET:
{code}
ICluster.disableWal member is missing in .NET.
ICluster.enableWal member is missing in .NET.
ICluster.isWalEnabled member is missing in .NET.
{code}



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

[jira] [Assigned] (IGNITE-7004) Ability to disable WAL (Cross-cache tx should be rescricted while WAL disabled)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-7004:
---

Assignee: (was: Anton Vinogradov)

> Ability to disable WAL (Cross-cache tx should be rescricted while WAL 
> disabled)
> ---
>
> Key: IGNITE-7004
> URL: https://issues.apache.org/jira/browse/IGNITE-7004
> Project: Ignite
>  Issue Type: Sub-task
>  Components: persistence
>Reporter: Anton Vinogradov
>Priority: Major
> Fix For: 2.5
>
>
> Cross-cache transactions affecting caches with different modes (e.g. one 
> enabled, another disabled) are not allowed



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

[jira] [Commented] (IGNITE-7488) fix javadoc and license check failures introduced per IGNITE-7284

2018-01-22 Thread Stanislav Lukyanov (JIRA)


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

Stanislav Lukyanov commented on IGNITE-7488:


@implSpec is a tag introduced in Java 8. It supposed to be present in all 
`default` methods specifying the part of the method contract that is not 
inherited by overriding methods.

Need to check why Ignite's Javadoc build doesn't allow Java 8's tags, fix the 
build and restore the tags.

> fix javadoc and license check failures introduced per IGNITE-7284
> -
>
> Key: IGNITE-7488
> URL: https://issues.apache.org/jira/browse/IGNITE-7488
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Stanislav Lukyanov
>Priority: Major
>
> fix javadoc and license check failures introduced per IGNITE-7284. One 
> example is:
> {noformat}
> [15:22:32][Step 7/7] [WARNING] Javadoc Warnings
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:97:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:117:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:137:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:168:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:199:
>  warning - @implSpec is an unknown tag. {noformat}
> and there may be others. Link for Teamcity task to verify that there are no 
> violations: 
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc



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

[jira] [Commented] (IGNITE-7485) add support for authentication parameters to control.sh utility


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

Sergey Kosarev commented on IGNITE-7485:


[~kuaw26], I don't mind. Just used same naming as in  
org.apache.ignite.plugin.security.SecurityCredentials

> add support for authentication parameters to control.sh utility
> ---
>
> Key: IGNITE-7485
> URL: https://issues.apache.org/jira/browse/IGNITE-7485
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> Currently controls.sh utility does not work if cluster is running under 
> authentication.
> Error is shown:
> Failed to get cluster state.
> Authentication error.
>  
> it is suggested to introduce authentication parameters to the utitlity
> --login LOGIN
> --password PASSWORD
>  
> Main Utility class ( CommandHandler )  is located in ignite-core module 
> currently. 
>  



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

[jira] [Commented] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.


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

Oleg Ignatenko commented on IGNITE-6899:


I pulled the recent changes and rerun unit tests in GAGridTestSuite and 
modified example (with non-default elitism count) - everything is OK. I also 
reviewed recent changes made to javadocs - as far as I can tell most issues 
were corrected.

To make sure that nothing critical is missed I plan to run [automated check for 
licenses and javadocs on 
TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc]
 (plan to update this comment with check results).

All of my prior review comments appear to be addressed, including those about 
docs at readme.io. Speaking of enum {{SELECTION_METHOD}}, please disregard my 
comments from previous review round: upon a closer inspection it looks good 
enough as is to me. Back then I also recommended a second round design review - 
I asked [~chief] and he promised to take a look.

> Adding GA Grid to Apache Ignite ML module.
> --
>
> Key: IGNITE-6899
> URL: https://issues.apache.org/jira/browse/IGNITE-6899
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Turik Campbell
>Priority: Major
> Fix For: 2.5
>
> Attachments: coverage.zip
>
>
> We want to add GA Grid to our ML Module.
> This is the first iteration of this integration. On this step we will simple 
> add GA Grid to the separate package in ML module.
> (i) This is a good package for GA Grid: org.apache.ignite.ml.genetic 
> (i) For GA Grid we need unit tests as well as examples



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

[jira] [Commented] (IGNITE-7345) Spark Data Frames and Ignite Documentation

2018-01-22 Thread Nikolay Izhikov (JIRA)


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

Nikolay Izhikov commented on IGNITE-7345:
-

Hello, [~dmagda].

I wrote documentation about Ignite Data Frames.
Please, review 

https://apacheignite-fs.readme.io/v2.3/docs/ignite-data-frame

> Spark Data Frames and Ignite Documentation
> --
>
> Key: IGNITE-7345
> URL: https://issues.apache.org/jira/browse/IGNITE-7345
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Nikolay Izhikov
>Priority: Critical
> Fix For: 2.4
>
>
> Spark Data frames integration [1] needs to be documented in this [2] domain.
> [1] 
> http://apache-ignite-developers.2346864.n4.nabble.com/Spark-data-frames-integration-merged-td25817.html
> [2] https://apacheignite-fs.readme.io/docs



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

[jira] [Commented] (IGNITE-6193) ML profile is missing in 2.1 binary release


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

ASF GitHub Bot commented on IGNITE-6193:


Github user oignatenko closed the pull request at:

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


> ML profile is missing in 2.1 binary release
> ---
>
> Key: IGNITE-6193
> URL: https://issues.apache.org/jira/browse/IGNITE-6193
> Project: Ignite
>  Issue Type: Bug
>  Components: examples, ml
>Reporter: Denis Magda
>Assignee: Oleg Ignatenko
>Priority: Blocker
>  Labels: important, ml
> Fix For: 2.3
>
>
> In Apache Ignite 2.0 we added the ML profile to the binary release that 
> allowed activating this functionality and running the examples easily. The 
> getting started is written based on the profile presence:
> https://apacheignite.readme.io/docs/machine-learning#section-getting-started
> The profile is missing for 2.1 release. To reproduce the issue just download 
> 2.1 binary release and follow the getting started section, you'll stumble on 
> step 4:
> https://apacheignite.readme.io/docs/machine-learning#section-getting-started
> This has to be fixed as soon as possible and the fix should be merged both in 
> the master and in a branch of the urgent Ignite release that is discussed 
> here:
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Urgent-Ignite-bug-fix-release-td21292.html



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

[jira] [Deleted] (IGNITE-7487) .NET: Thin client: Documentation


 [ 
https://issues.apache.org/jira/browse/IGNITE-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn deleted IGNITE-7487:
---


> .NET: Thin client: Documentation
> 
>
> Key: IGNITE-7487
> URL: https://issues.apache.org/jira/browse/IGNITE-7487
> Project: Ignite
>  Issue Type: Task
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
>
> Document .NET Thin Client usage on readme.io



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

[jira] [Commented] (IGNITE-6711) DataRegionMetrics#totalAllocatedPages is not valid after node restart


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

ASF GitHub Bot commented on IGNITE-6711:


Github user andrey-kuznetsov closed the pull request at:

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


> DataRegionMetrics#totalAllocatedPages is not valid after node restart
> -
>
> Key: IGNITE-6711
> URL: https://issues.apache.org/jira/browse/IGNITE-6711
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: iep-6, newbie
> Fix For: 2.4
>
>
> Currently, data region metric tracks total allocated pages by a callback on 
> page allocation. However, when a node with enabled persistence is started, 
> some of the pages are already allocated, which leads to an incorrect metric 
> value.



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

[jira] [Commented] (IGNITE-5571) Make sure that cache-less execution works as good as cache-based


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

ASF GitHub Bot commented on IGNITE-5571:


Github user asfgit closed the pull request at:

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


> Make sure that cache-less execution works as good as cache-based
> 
>
> Key: IGNITE-5571
> URL: https://issues.apache.org/jira/browse/IGNITE-5571
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Critical
> Fix For: 2.4
>
>
> Compare the following two methods:
> 1) {{GridQueryProcessor.querySqlFields}} - old good entry point for query 
> execution;
> 2) {{GridQueryProcessor.querySqlFieldsNoCache}} - new method for "cache-less" 
> execution.
> Note how cache context is used in the first method:
> 1) First, it helps determine whether query can be converted to "local"
> 2) Second, it gets query parallelism of current cache, and if it differs from 
> {{1}}, then it turns on {{distributedJoins}}.
> Neither of this happens in the second implementation. Moreover, I had to 
> throw an exception for local queries, as I didn't know how to handle them 
> properly.
> We need to investigate and fix these two deficiencies somehow. Probably some 
> inputs from [~sergi.vladykin] would be required, to understand what is going 
> on.
> Our ultimate goal is to make "cache-less" execution as good as the old one.



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

[jira] [Created] (IGNITE-7491) Documentation: add new data region metrics description

2018-01-22 Thread Andrey Kuznetsov (JIRA)

Andrey Kuznetsov created IGNITE-7491:


 Summary: Documentation: add new data region metrics description
 Key: IGNITE-7491
 URL: https://issues.apache.org/jira/browse/IGNITE-7491
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Andrey Kuznetsov
Assignee: Denis Magda
 Fix For: 2.4


Newly created data region metrics should be documented.

* `getTotalAllocatedSize` -- same as `getTotalAllocatedPages` but in bytes.
* `getPhysicalMemorySize` -- same as `getPhysicalMemoryPages` but in bytes.
* `getCheckpointBufferPages` -- gets checkpoint buffer size in pages.
* `getCheckpointBufferSize` -- gets checkpoint buffer size in bytes.
* `getPageSize` -- gets memory page size.



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

[jira] [Comment Edited] (IGNITE-7459) Web console: do not show result title until query end


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

Pavel Konstantinov edited comment on IGNITE-7459 at 1/23/18 3:31 AM:
-

Found another case:
# click Scan on selected node - node ID8 will be printed in the result table 
before user selects any node and perform scan
# click Cancel - node ID8 still printed in the title of the results table


was (Author: pkonstantinov):
Found another case:
# click Scan on selected node - node ID8 will be printed in the result table 
before user selects any node and perform scan

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Commented] (IGNITE-7459) Web console: do not show result title until query end


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

Pavel Konstantinov commented on IGNITE-7459:


Found another case:
# click Scan on selected node - node ID8 will be printed in the result table 
before user selects any node and perform scan

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Updated] (IGNITE-7492) Implement metrics for Memory Regions in UI tools


 [ 
https://issues.apache.org/jira/browse/IGNITE-7492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-7492:
-
Fix Version/s: 2.5

> Implement metrics for Memory Regions in UI tools
> 
>
> Key: IGNITE-7492
> URL: https://issues.apache.org/jira/browse/IGNITE-7492
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
>
> See IGNITE-6920 for list of metrics.



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

[jira] [Created] (IGNITE-7492) Implement metrics for Memory Regions in UI tools

Alexey Kuznetsov created IGNITE-7492:


 Summary: Implement metrics for Memory Regions in UI tools
 Key: IGNITE-7492
 URL: https://issues.apache.org/jira/browse/IGNITE-7492
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov


See IGNITE-6920 for list of metrics.



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

[jira] [Commented] (IGNITE-2766) Cache instance is closed when client disconnects

2018-01-22 Thread Ilya Kasnacheev (JIRA)


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

Ilya Kasnacheev commented on IGNITE-2766:
-

[~vkulichenko] So I have this commit stashed already (see above), I was 
hesistant to push it thru due to unclear requirements.

You can merge it to master if tests pass.

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F3417%2Fhead

> Cache instance is closed when client disconnects
> 
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> In case client disconnects and reconnects after network timeout (i.e., with a 
> new ID), all cache instances acquired by this client are closed and are not 
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.



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

[jira] [Comment Edited] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.

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

Oleg Ignatenko edited comment on IGNITE-6899 at 1/22/18 4:43 PM:
-

I pulled the recent changes and rerun unit tests in GAGridTestSuite and
modified example (with non-default elitism count) - everything is OK. I also
reviewed recent changes made to javadocs - as far as I can tell most issues
were corrected.

To make sure that nothing critical is missed I plan to run [automated check for
licenses and javadocs on
TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc]
(plan to update this comment with check results).

All of my prior review comments appear to be addressed, including those about
docs at readme.io. Speaking of enum {{SELECTION_METHOD}}, please disregard my
comments from previous review round: upon a closer inspection it looks good
enough as is to me. Back then I also recommended a second round design review -
I asked [~chief] and he promised to take a look.

*update* Automated check at Teamcity reported the following issues with
javadocs: {noformat}ml\genetic\CrossOverTask.java:59: warning - @param argument
"GAConfiguration" is not a parameter name.
ml\genetic\MutateTask.java:60: warning - @param argument "GAConfiguration" is
not a parameter name.
ml\genetic\TruncateSelectionJob.java:53: warning - @param argument
"mutationRate" is not a parameter name.
ml\genetic\parameter\ChromosomeCriteria.java:46: warning - @param argument
"List" is not a parameter name.
ml\genetic\parameter\GAConfiguration.java:293: warning - @param argument
"seletionMethod" is not a parameter name.

examples/ml/genetic/movie/Movie.java:97: warning - @return tag has no arguments.
examples/ml/genetic/movie/MovieFitnessFunction.java:56: warning - @param
argument "genres" is not a parameter name.
examples/ml/genetic/movie/MovieGAExample.java:49: warning - Tag @link:
reference not found: ExampleNodeStartup
examples/ml/genetic/change/OptimizeMakeChangeGAExample.java:52: warning - Tag
@link: reference not found: ExampleNodeStartup
examples/ml/genetic/helloworld/HelloWorldGAExample.java:49: warning - Tag
@link: reference not found: ExampleNodeStartup
{noformat}
(above list seems complete for the matters involving GA Grid, though to make
sure it needs re-running after these are corrected)

was (Author: oignatenko):
I pulled the recent changes and rerun unit tests in GAGridTestSuite and
modified example (with non-default elitism count) - everything is OK. I also
reviewed recent changes made to javadocs - as far as I can tell most issues
were corrected.

*update* First run of automated check reported the following issues with
javadocs: {noformat}ml\genetic\CrossOverTask.java:59: warning - @param argument
"GAConfiguration" is not a parameter name.
ml\genetic\MutateTask.java:60: warning - @param argument "GAConfiguration" is
not a parameter name.
ml\genetic\TruncateSelectionJob.java:53: warning - @param argument
"mutationRate" is not a parameter name.
ml\genetic\parameter\ChromosomeCriteria.java:46: warning - @param argument
"List" is not a parameter name.
ml\genetic\parameter\GAConfiguration.java:293: warning - @param argument
"seletionMethod" is not a parameter name.

examples/ml/genetic/movie/Movie.java:97: warning - @return tag has no arguments.
examples/ml/genetic/movie/MovieFitnessFunction.java:56: warning - @param
argument "genres" is not a parameter name.
examples/ml/genetic/movie/MovieGAExample.java:49: warning - Tag @link:
reference not found: ExampleNodeStartup
examples/ml/genetic/change/OptimizeMakeChangeGAExample.java:52: warning - Tag
@link: reference not found: ExampleNodeStartup
examples/ml/genetic/helloworld/HelloWorldGAExample.java:49: warning - Tag
@link: reference not found: ExampleNodeStartup
{noformat}
(above list may be incomplete, I a re-running the check to make sure that I
didn't miss something else)

> Adding GA Grid to Apache Ignite ML module.
> --
>
> Key: IGNITE-6899
> URL: https://issues.apache.org/jira/browse/IGNITE-6899
> Project: Ignite
> Issue Type: New Feature
> Components:

[jira] [Created] (IGNITE-7490) Doc: clarify what's table name and how to change fields/indexes for QueryEntity/Annotations configs

Denis Magda created IGNITE-7490:
---

 Summary: Doc: clarify what's table name and how to change 
fields/indexes for QueryEntity/Annotations configs
 Key: IGNITE-7490
 URL: https://issues.apache.org/jira/browse/IGNITE-7490
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
Assignee: Denis Magda
 Fix For: 2.4


Users got confused on:
 * what should be a table name if SQL is configured with QueryEntity/Annotations
 * how to add/remove columns if QueryEntity/Annotations were used for initial 
configurations

http://apache-ignite-users.70518.x6.nabble.com/query-on-BinaryObject-index-and-table-td19631.html



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

[jira] [Commented] (IGNITE-7488) fix javadoc and license check failures introduced per IGNITE-7284


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

Oleg Ignatenko commented on IGNITE-7488:


Worth noting that this tag isn't present in [official list of Java 8 javadoc 
tags 
here|https://docs.oracle.com/javase/8/docs/technotes/tools/windows/javadoc.html].
 According to [this message at dev 
list|http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-April/016149.html]
 these weren't supposed to be used outside of JDK (and although the message is 
rather old, I've found nothing indicating that this has somehow changed): 
{quote}These tags... are not proposed as standard javadoc tags and may be 
implemented differently in future Java releases. Since they are implemented as 
custom tags just for the JDK API documentation you can't automatically use them 
in your own code...{quote}

> fix javadoc and license check failures introduced per IGNITE-7284
> -
>
> Key: IGNITE-7488
> URL: https://issues.apache.org/jira/browse/IGNITE-7488
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Stanislav Lukyanov
>Priority: Major
>
> fix javadoc and license check failures introduced per IGNITE-7284. One 
> example is:
> {noformat}
> [15:22:32][Step 7/7] [WARNING] Javadoc Warnings
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:97:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:117:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:137:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:168:
>  warning - @implSpec is an unknown tag.
> [15:22:32][Step 7/7] [WARNING] 
> /data/teamcity/work/bd85361428dcdb1/modules/core/src/main/java/org/apache/ignite/IgniteLogger.java:199:
>  warning - @implSpec is an unknown tag. {noformat}
> and there may be others. Link for Teamcity task to verify that there are no 
> violations: 
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc



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

[jira] [Assigned] (IGNITE-2737) Ignite-Spark documentation is missing some useful informations

2018-01-22 Thread Nikolay Izhikov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov reassigned IGNITE-2737:
---

Assignee: Nikolay Izhikov

> Ignite-Spark documentation is missing some useful informations
> --
>
> Key: IGNITE-2737
> URL: https://issues.apache.org/jira/browse/IGNITE-2737
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation, spark
>Reporter: Luca Rea
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: community
> Fix For: 2.5
>
>
> Hi,
> in my tests I have experienced some configuration issue running spark in 
> local and yarn-client mode, so I want to share them.
> In order to let Ignite work correctly I had to customize spark-defaults.conf 
> adding to "spark.driver.extraClassPath" and "spark.executor.extraClassPath" 
> the string
> {code}
> "/opt/ignite/libs/*:/opt/ignite/libs/optional/ignite-spark/*:/opt/ignite/libs/optional/ignite-log4j/*:/opt/ignite/libs/optional/ignite-yarn/*:/opt/ignite/libs/ignite-spring/*"
> {code}
> (opt/ignite is my IGNITE_HOME) and other IGNITE_ useful variables like 
> "spark.executorEnv.IGNITE_WORK_DIR" in order to let them be loaded by 
> executors.



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

[jira] [Updated] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs


 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7000:
---
Attachment: Cross-Platform Support.md

> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
> Attachments: Cross-Platform Support.md
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * VS Code and Rider
> * Mono is supported (useful for 32 bit and/or older distros): need to set 
> {{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} 
> to build
> * {{ Version="4.4.0" />}} may be required
> * Make sure examples in binary package can be run on Mono and .NET Core on 
> every OS.



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

[jira] [Commented] (IGNITE-6917) SQL: implement COPY command for efficient data loading


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

ASF GitHub Bot commented on IGNITE-6917:


GitHub user gg-shq opened a pull request:

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

IGNITE-6917: SQL: implement COPY command for efficient data loading



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

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

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

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


commit deb7994f0fd4233e3e0b699794b9066af87195c7
Author: gg-shq 
Date:   2018-01-19T12:13:37Z

IGNITE-6917: Intermediate commit

commit e7747a58c2cdacc6987d625a46d1f79a81863cd3
Author: gg-shq 
Date:   2018-01-19T17:21:50Z

IGNITE-6917: Intermediate commit

commit 6f37e6751285a96bdf757b392e1d4113bb47ee48
Author: gg-shq 
Date:   2018-01-19T17:30:22Z

IGNITE-6917: Intermediate commit

commit 49f0324c77d0bb3b4ec87317b1ecbde1bd6f34b1
Author: gg-shq 
Date:   2018-01-22T10:27:34Z

IGNITE-6917: Intermediate commit

commit a5bec61d41d8dc242cfbf11a7cf03c23bbbcd7c3
Author: gg-shq 
Date:   2018-01-22T12:25:04Z

IGNITE-6917: Intermediate commit

commit e18e18696fc92b93b17decf087721c693625ac36
Author: gg-shq 
Date:   2018-01-22T12:35:56Z

IGNITE-6917: Intermediate commit

commit 990c04919e181535e57290ee2516a9603657c160
Author: gg-shq 
Date:   2018-01-22T16:18:18Z

IGNITE-6917: Intermediate commit




> SQL: implement COPY command for efficient data loading
> --
>
> Key: IGNITE-6917
> URL: https://issues.apache.org/jira/browse/IGNITE-6917
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Kirill Shirokov
>Priority: Major
>  Labels: iep-1
>
> Inspired by Postgres [1]
> Common use case - bulk data load through JDBC/ODBC interface. Currently it is 
> only possible to execute single commands one by one. We already can batch 
> them to improve performance, but there is still big room for improvement.
> We should think of a completely new command - {{COPY}}. It will accept a file 
> (or input stream in general case) on the client side, then transfer data to 
> the cluster, and then execute update inside the cluster, e.g. through 
> streamer.
> First of all we need to create quick and dirty prototype to assess potential 
> performance improvement. It speedup is confirmed, we should build base 
> implementation which will accept only files. But at the same time we should 
> understand how it will evolve in future: multiple file formats (probably 
> including Hadoop formarts, e.g. Parquet), escape characters, input streams, 
> etc..
> [1] [https://www.postgresql.org/docs/9.6/static/sql-copy.html]
> h1. Proposed syntax
> Curent implementation:
> {noformat}
> COPY 
> FROM "file.name"
> INTO .
> [(col-name, ...)]
> FORMAT  -- Only CSV format is supported in the current 
> release
> {noformat}
> We may want to gradually add features to this command in future to have 
> something like this:
> {noformat}
> COPY
> FROM 'file.name' [CHARSET ]
> INTO . [CREATE [IF NOT EXISTS]]
> [(REPLACE|IGNORE|ABORT ON [])) EXISTING ROWS]
> [(col-name [] [NULLABLE] [ESCAPES], ...) [MATCH HEADER]]
> FORMAT (csv|tsv|...)
> -- CSV format options:
> [COLSEP='column-separator']
> [ROWSEP='row-separators']
> [QUOTE='quote-char']
> [ESCAPE='escape-char']
> [NULL='null-sequence']
> [ROWS -]
> --or--
> [SKIP ROWS ] [MAX ROWS ]
> [COLS -]
> --or--
> [SKIP COLS ] [MAX COLS ]
> [MATCH HEADER ROW]
> [BATCH ( ROWS |  (KB|MB|GB))]
> [LOCK (TABLE|ROWS)]
> [NOLOGGING] 
> {noformat}
> h1. Implementation decisions and notes
> h2. Parsing
> * We support CSV format described in RFC 4180.
> * Custom row and column separators, quoting characters are currently hardcoded
> * Escape sequences, line comment characters are currently not supported
> * We may want to support fixed-length formats (via format descriptors) in 
> future
> h2. File handling
> * File character set to be supported in future
> * Skipped/imported row number (or first/last line or skip header option), 
> skipped/imported column number (or first/last column): to be supported in 
> future
> * Line start pattern (as in MySQL): no support planned
> * We currently support only client-side import. No server-side file import.
> * We may want to support client-side

[jira] [Assigned] (IGNITE-6711) DataRegionMetrics#totalAllocatedPages is not valid after node restart

2018-01-22 Thread Anton Vinogradov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov reassigned IGNITE-6711:


Assignee: Anton Vinogradov  (was: Andrey Kuznetsov)

> DataRegionMetrics#totalAllocatedPages is not valid after node restart
> -
>
> Key: IGNITE-6711
> URL: https://issues.apache.org/jira/browse/IGNITE-6711
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexey Goncharuk
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: iep-6, newbie
> Fix For: 2.4
>
>
> Currently, data region metric tracks total allocated pages by a callback on 
> page allocation. However, when a node with enabled persistence is started, 
> some of the pages are already allocated, which leads to an incorrect metric 
> value.



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

[jira] [Comment Edited] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.


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

Oleg Ignatenko edited comment on IGNITE-6899 at 1/22/18 4:27 PM:
-

I pulled the recent changes and rerun unit tests in GAGridTestSuite and 
modified example (with non-default elitism count) - everything is OK. I also 
reviewed recent changes made to javadocs - as far as I can tell most issues 
were corrected.

To make sure that nothing critical is missed I plan to run [automated check for 
licenses and javadocs on 
TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc]
 (plan to update this comment with check results).

All of my prior review comments appear to be addressed, including those about 
docs at readme.io. Speaking of enum {{SELECTION_METHOD}}, please disregard my 
comments from previous review round: upon a closer inspection it looks good 
enough as is to me. Back then I also recommended a second round design review - 
I asked [~chief] and he promised to take a look.

-

*update* First run of automated check reported the following issues with 
javadocs: {noformat}ml\genetic\CrossOverTask.java:59: warning - @param argument 
"GAConfiguration" is not a parameter name.
ml\genetic\MutateTask.java:60: warning - @param argument "GAConfiguration" is 
not a parameter name.
ml\genetic\TruncateSelectionJob.java:53: warning - @param argument 
"mutationRate" is not a parameter name.
ml\genetic\parameter\ChromosomeCriteria.java:46: warning - @param argument 
"List" is not a parameter name.
ml\genetic\parameter\GAConfiguration.java:293: warning - @param argument 
"seletionMethod" is not a parameter name.

examples\ml\genetic\helloworld\HelloWorldGAExample.java:49: warning - Tag 
@link: reference not found: ExampleNodeStartup
examples\ml\genetic\movie\Movie.java:97: warning - @return tag has no arguments.
examples\ml\genetic\movie\MovieFitnessFunction.java:56: warning - @param 
argument "genres" is not a parameter name.
examples\ml\genetic\movie\MovieGAExample.java:49: warning - Tag @link: 
reference not found: ExampleNodeStartup
{noformat}
(above list may be incomplete, I a re-running the check to make sure that I 
didn't miss something else)


was (Author: oignatenko):
I pulled the recent changes and rerun unit tests in GAGridTestSuite and 
modified example (with non-default elitism count) - everything is OK. I also 
reviewed recent changes made to javadocs - as far as I can tell most issues 
were corrected.

To make sure that nothing critical is missed I plan to run [automated check for 
licenses and javadocs on 
TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc]
 (plan to update this comment with check results).

All of my prior review comments appear to be addressed, including those about 
docs at readme.io. Speaking of enum {{SELECTION_METHOD}}, please disregard my 
comments from previous review round: upon a closer inspection it looks good 
enough as is to me. Back then I also recommended a second round design review - 
I asked [~chief] and he promised to take a look.

> Adding GA Grid to Apache Ignite ML module.
> --
>
> Key: IGNITE-6899
> URL: https://issues.apache.org/jira/browse/IGNITE-6899
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Turik Campbell
>Priority: Major
> Fix For: 2.5
>
> Attachments: coverage.zip
>
>
> We want to add GA Grid to our ML Module.
> This is the first iteration of this integration. On this step we will simple 
> add GA Grid to the separate package in ML module.
> (i) This is a good package for GA Grid: org.apache.ignite.ml.genetic 
> (i) For GA Grid we need unit tests as well as examples



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

[jira] [Comment Edited] (IGNITE-6899) Adding GA Grid to Apache Ignite ML module.


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

Oleg Ignatenko edited comment on IGNITE-6899 at 1/22/18 4:38 PM:
-

I pulled the recent changes and rerun unit tests in GAGridTestSuite and 
modified example (with non-default elitism count) - everything is OK. I also 
reviewed recent changes made to javadocs - as far as I can tell most issues 
were corrected.

To make sure that nothing critical is missed I plan to run [automated check for 
licenses and javadocs on 
TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc]
 (plan to update this comment with check results).

All of my prior review comments appear to be addressed, including those about 
docs at readme.io. Speaking of enum {{SELECTION_METHOD}}, please disregard my 
comments from previous review round: upon a closer inspection it looks good 
enough as is to me. Back then I also recommended a second round design review - 
I asked [~chief] and he promised to take a look.

-

*update* First run of automated check reported the following issues with 
javadocs: {noformat}ml\genetic\CrossOverTask.java:59: warning - @param argument 
"GAConfiguration" is not a parameter name.
ml\genetic\MutateTask.java:60: warning - @param argument "GAConfiguration" is 
not a parameter name.
ml\genetic\TruncateSelectionJob.java:53: warning - @param argument 
"mutationRate" is not a parameter name.
ml\genetic\parameter\ChromosomeCriteria.java:46: warning - @param argument 
"List" is not a parameter name.
ml\genetic\parameter\GAConfiguration.java:293: warning - @param argument 
"seletionMethod" is not a parameter name.

examples/ml/genetic/movie/Movie.java:97: warning - @return tag has no arguments.
examples/ml/genetic/movie/MovieFitnessFunction.java:56: warning - @param 
argument "genres" is not a parameter name.
examples/ml/genetic/movie/MovieGAExample.java:49: warning - Tag @link: 
reference not found: ExampleNodeStartup
examples/ml/genetic/change/OptimizeMakeChangeGAExample.java:52: warning - Tag 
@link: reference not found: ExampleNodeStartup
examples/ml/genetic/helloworld/HelloWorldGAExample.java:49: warning - Tag 
@link: reference not found: ExampleNodeStartup
{noformat}
(above list may be incomplete, I a re-running the check to make sure that I 
didn't miss something else)


was (Author: oignatenko):
I pulled the recent changes and rerun unit tests in GAGridTestSuite and 
modified example (with non-default elitism count) - everything is OK. I also 
reviewed recent changes made to javadocs - as far as I can tell most issues 
were corrected.

To make sure that nothing critical is missed I plan to run [automated check for 
licenses and javadocs on 
TeamCity|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesJavadoc]
 (plan to update this comment with check results).

All of my prior review comments appear to be addressed, including those about 
docs at readme.io. Speaking of enum {{SELECTION_METHOD}}, please disregard my 
comments from previous review round: upon a closer inspection it looks good 
enough as is to me. Back then I also recommended a second round design review - 
I asked [~chief] and he promised to take a look.

-

*update* First run of automated check reported the following issues with 
javadocs: {noformat}ml\genetic\CrossOverTask.java:59: warning - @param argument 
"GAConfiguration" is not a parameter name.
ml\genetic\MutateTask.java:60: warning - @param argument "GAConfiguration" is 
not a parameter name.
ml\genetic\TruncateSelectionJob.java:53: warning - @param argument 
"mutationRate" is not a parameter name.
ml\genetic\parameter\ChromosomeCriteria.java:46: warning - @param argument 
"List" is not a parameter name.
ml\genetic\parameter\GAConfiguration.java:293: warning - @param argument 
"seletionMethod" is not a parameter name.

examples\ml\genetic\helloworld\HelloWorldGAExample.java:49: warning - Tag 
@link: reference not found: ExampleNodeStartup
examples\ml\genetic\movie\Movie.java:97: warning - @return tag has no arguments.
examples\ml\genetic\movie\MovieFitnessFunction.java:56: warning - @param 
argument "genres" is not a parameter name.
examples\ml\genetic\movie\MovieGAExample.java:49: warning - Tag @link: 
reference not found: ExampleNodeStartup
{noformat}
(above list may be incomplete, I a re-running the check to make sure that I 
didn't miss something else)

> Adding GA Grid to Apache Ignite ML module.
> --
>
> Key: IGNITE-6899
> URL: https://issues.apache.org/jira/browse/IGNITE-6899
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Turik Campbell
>Priority: Major
> Fix For: 2.5
>
>

[jira] [Created] (IGNITE-7483) Queries: transformers are not executed when paging the result

2018-01-22 Thread Sascha Hofer (JIRA)

Sascha Hofer created IGNITE-7483:


 Summary: Queries: transformers are not executed when paging the 
result
 Key: IGNITE-7483
 URL: https://issues.apache.org/jira/browse/IGNITE-7483
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.3
Reporter: Sascha Hofer


It seems that transformers are not executed during pagination which leads to 
{{ClassCastExceptions}} because the result list also contains instances of 
{{GridCacheQueryResponseEntry}}.

To reproduce open {{GridCacheQueryTransformerSelfTest.testGetKeys()}} and set a 
page size of 1 so that

{code:java}
List keys = cache.query(new ScanQuery(), 
transformer).getAll();
{code}

becomes to

{code:java}
List keys = cache.query(new ScanQuery().setPageSize(1), transformer).getAll();
{code}

this leads to following stack trace:
{noformat}
java.lang.ClassCastException: 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryResponseEntry 
cannot be cast to java.lang.Comparable

at java.util.ComparableTimSort.binarySort(ComparableTimSort.java:249)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:207)
at java.util.Arrays.sort(Arrays.java:1312)
at java.util.Arrays.sort(Arrays.java:1506)
at java.util.ArrayList.sort(ArrayList.java:1454)
at java.util.Collections.sort(Collections.java:141)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryTransformerSelfTest.testGetKeys(GridCacheQueryTransformerSelfTest.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
at java.lang.Thread.run(Thread.java:745)
{noformat}



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

[jira] [Closed] (IGNITE-7420) Too thick modal body


 [ 
https://issues.apache.org/jira/browse/IGNITE-7420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov closed IGNITE-7420.
--

> Too thick modal body
> 
>
> Key: IGNITE-7420
> URL: https://issues.apache.org/jira/browse/IGNITE-7420
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
> Attachments: yz0r1o.jpg
>
>
> !yz0r1o.jpg!



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

[jira] [Created] (IGNITE-7484) Documentation for new lin reg trainer.

Yury Babak created IGNITE-7484:
--

 Summary: Documentation for new lin reg trainer.
 Key: IGNITE-7484
 URL: https://issues.apache.org/jira/browse/IGNITE-7484
 Project: Ignite
  Issue Type: Task
  Components: ml
Reporter: Yury Babak






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

[jira] [Commented] (IGNITE-2766) Cache instance is closed when client disconnects


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

ASF GitHub Bot commented on IGNITE-2766:


GitHub user alamar opened a pull request:

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

IGNITE-2766 Opportunistically reopen cache after client reconnect.



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

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

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

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


commit a70620ca6398ba151541b5ff92c7f941eea07527
Author: Ilya Kasnacheev 
Date:   2018-01-22T15:29:36Z

IGNITE-2766 Opportunistically reopen cache after client reconnect.




> Cache instance is closed when client disconnects
> 
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> In case client disconnects and reconnects after network timeout (i.e., with a 
> new ID), all cache instances acquired by this client are closed and are not 
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.



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

[jira] [Created] (IGNITE-7489) Weird FillFactor metric fluctuation.

2018-01-22 Thread Andrew Mashenkov (JIRA)

Andrew Mashenkov created IGNITE-7489:


 Summary: Weird FillFactor metric fluctuation.
 Key: IGNITE-7489
 URL: https://issues.apache.org/jira/browse/IGNITE-7489
 Project: Ignite
  Issue Type: Bug
Reporter: Andrew Mashenkov
 Attachments: FillFactorTest.java

PFA a repro.

There is 2 node grid with no persistence configure. Topology is stable.

Cache is populated with unique keys (no updates) and observe allocated data 
pages metric grows constantly as expected.

Used memory is calculated as PhysicalMemoryPages*PageSize*FillFactor and 
expected it will be constantly grows (or may be with a small error).

But the error look too large, used memory (and FillFactor as well) may 2-10+ 
time differs.

 

E.g. allocated pages, fillFactor, usedMem (bytes):
node-0: 13789 0.851563 48096032
node-1: 14447 0.781250 46230400

In next second:

node-0: 13958 0.039063 2233280
node-1: 14624 0.347656 20824576

 

 



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

[jira] [Updated] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs


 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7000:
---
Description: 
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* VS Code and Rider
* Mono is supported (useful for 32 bit and/or older distros): need to set 
{{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} to 
build
* {{}} may be required
* Make sure examples in binary package can be run on Mono and .NET Core on 
every OS.

  was:
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* VS Code and Rider
* Mono is supported (useful for 32 bit and/or older distros): need to set 
{{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} to 
build
* {{}} may be required


> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * VS Code and Rider
> * Mono is supported (useful for 32 bit and/or older distros): need to set 
> {{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} 
> to build
> * {{ Version="4.4.0" />}} may be required
> * Make sure examples in binary package can be run on Mono and .NET Core on 
> every OS.



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

[jira] [Commented] (IGNITE-7477) Ignite.NET does not work on Java 9


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

Pavel Tupitsyn commented on IGNITE-7477:


Java 9 detection implemented, checked on Windows/Linux/macOS.
Merged to master: {{e052f941c96d8a397d2b419fe41edf585107302f}}.

> Ignite.NET does not work on Java 9
> --
>
> Key: IGNITE-7477
> URL: https://issues.apache.org/jira/browse/IGNITE-7477
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Ignite.NET does not work properly on Java 9 (IGNITE-6730).
> Some additional JVM settings are required:
> {code}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
> {code}



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

[jira] [Commented] (IGNITE-7477) Ignite.NET does not work on Java 9


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

ASF GitHub Bot commented on IGNITE-7477:


Github user asfgit closed the pull request at:

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


> Ignite.NET does not work on Java 9
> --
>
> Key: IGNITE-7477
> URL: https://issues.apache.org/jira/browse/IGNITE-7477
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Ignite.NET does not work properly on Java 9 (IGNITE-6730).
> Some additional JVM settings are required:
> {code}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
> {code}



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

[jira] [Updated] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs


 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7000:
---
Description: 
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* VS Code and Rider
* Mono is supported (useful for 32 bit and/or older distros): need to set 
{{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} to 
build
* {{}} may be required

  was:
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* Service proxies are not supported because {{Remoting}} is not available on 
.NET Core: IGNITE-7281
* VS Code and Rider
* Mono is supported (useful for 32 bit and/or older distros): need to set 
{{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} to 
build
* {{}} may be required


> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * VS Code and Rider
> * Mono is supported (useful for 32 bit and/or older distros): need to set 
> {{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} 
> to build
> * {{ Version="4.4.0" />}} may be required



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

[jira] [Comment Edited] (IGNITE-7477) Ignite.NET does not work on Java 9


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

Pavel Tupitsyn edited comment on IGNITE-7477 at 1/22/18 1:05 PM:
-

Java 9 detection implemented, checked on Windows/Linux/macOS.
Merged to master: {{e052f941c96d8a397d2b419fe41edf585107302f}}.
Cherry-picked to ignite-2.4: {{ce2a30efa4216ab2efc28384a7bc72633f7a4e09}}.


was (Author: ptupitsyn):
Java 9 detection implemented, checked on Windows/Linux/macOS.
Merged to master: {{e052f941c96d8a397d2b419fe41edf585107302f}}.

> Ignite.NET does not work on Java 9
> --
>
> Key: IGNITE-7477
> URL: https://issues.apache.org/jira/browse/IGNITE-7477
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Ignite.NET does not work properly on Java 9 (IGNITE-6730).
> Some additional JVM settings are required:
> {code}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
> {code}



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

[jira] [Resolved] (IGNITE-7477) Ignite.NET does not work on Java 9


 [ 
https://issues.apache.org/jira/browse/IGNITE-7477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn resolved IGNITE-7477.

Resolution: Fixed

> Ignite.NET does not work on Java 9
> --
>
> Key: IGNITE-7477
> URL: https://issues.apache.org/jira/browse/IGNITE-7477
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> Ignite.NET does not work properly on Java 9 (IGNITE-6730).
> Some additional JVM settings are required:
> {code}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
> {code}



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

[jira] [Commented] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs


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

Pavel Tupitsyn commented on IGNITE-7000:


Page created: 
https://apacheignite-net.readme.io/docs/cross-platform-support-windows-linux-macos

> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * VS Code and Rider
> * Mono is supported (useful for 32 bit and/or older distros): need to set 
> {{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} 
> to build
> * {{ Version="4.4.0" />}} may be required
> * Make sure examples in binary package can be run on Mono and .NET Core on 
> every OS.



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

[jira] [Updated] (IGNITE-7484) Documentation for new lin reg trainer.


 [ 
https://issues.apache.org/jira/browse/IGNITE-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-7484:

Labels:   (was: documentaion)

> Documentation for new lin reg trainer.
> --
>
> Key: IGNITE-7484
> URL: https://issues.apache.org/jira/browse/IGNITE-7484
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>Priority: Major
>
> We need to add documentation for changes in IGNITE-5217



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

[jira] [Updated] (IGNITE-7484) Documentation for new lin reg trainer.


 [ 
https://issues.apache.org/jira/browse/IGNITE-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-7484:

Component/s: documentation

> Documentation for new lin reg trainer.
> --
>
> Key: IGNITE-7484
> URL: https://issues.apache.org/jira/browse/IGNITE-7484
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>Priority: Major
>
> We need to add documentation for changes in IGNITE-5217



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

[jira] [Commented] (IGNITE-7484) Documentation for new lin reg trainer.


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

Denis Magda commented on IGNITE-7484:
-

Guys, please use "documentation" as a component and not as a label. More 
details are here:

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document

> Documentation for new lin reg trainer.
> --
>
> Key: IGNITE-7484
> URL: https://issues.apache.org/jira/browse/IGNITE-7484
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Anton Dmitriev
>Priority: Major
>
> We need to add documentation for changes in IGNITE-5217



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

[jira] [Updated] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture


 [ 
https://issues.apache.org/jira/browse/IGNITE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-7419:

Environment: (was: Explain how swap is supported and works in Ignite. 
Provide a rationale on Ignite persistence vs swap.

In addition, looks people don't catch what happens when memory region goes 
beyond the maximum size. Revisit the persistence configuration:

http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046)

> Document swap usage in Ignite 2.x memory architecture
> -
>
> Key: IGNITE-7419
> URL: https://issues.apache.org/jira/browse/IGNITE-7419
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>




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

[jira] [Commented] (IGNITE-7345) Spark Data Frames and Ignite Documentation


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

Denis Magda commented on IGNITE-7345:
-

[~NIzhikov] , thanks a lot! I'll review the doc in the nearest time.

> Spark Data Frames and Ignite Documentation
> --
>
> Key: IGNITE-7345
> URL: https://issues.apache.org/jira/browse/IGNITE-7345
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Spark Data frames integration [1] needs to be documented in this [2] domain.
> [1] 
> http://apache-ignite-developers.2346864.n4.nabble.com/Spark-data-frames-integration-merged-td25817.html
> [2] https://apacheignite-fs.readme.io/docs



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

[jira] [Assigned] (IGNITE-7345) Spark Data Frames and Ignite Documentation


 [ 
https://issues.apache.org/jira/browse/IGNITE-7345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-7345:
---

Assignee: Denis Magda  (was: Nikolay Izhikov)

> Spark Data Frames and Ignite Documentation
> --
>
> Key: IGNITE-7345
> URL: https://issues.apache.org/jira/browse/IGNITE-7345
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Spark Data frames integration [1] needs to be documented in this [2] domain.
> [1] 
> http://apache-ignite-developers.2346864.n4.nabble.com/Spark-data-frames-integration-merged-td25817.html
> [2] https://apacheignite-fs.readme.io/docs



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

[jira] [Updated] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture


 [ 
https://issues.apache.org/jira/browse/IGNITE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-7419:

Description: 
Explain how swap is supported and works in Ignite. Provide a rationale on 
Ignite persistence vs swap.

In addition, looks people don't catch what happens when memory region goes 
beyond the maximum size. Revisit the persistence configuration:

[http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046]

> Document swap usage in Ignite 2.x memory architecture
> -
>
> Key: IGNITE-7419
> URL: https://issues.apache.org/jira/browse/IGNITE-7419
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> Explain how swap is supported and works in Ignite. Provide a rationale on 
> Ignite persistence vs swap.
> In addition, looks people don't catch what happens when memory region goes 
> beyond the maximum size. Revisit the persistence configuration:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046]



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

[jira] [Commented] (IGNITE-7484) Documentation for new lin reg trainer.