[jira] [Closed] (IGNITE-4472) Web Console: Implement usage tracing

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-4472.
--
Assignee: Alexey Kuznetsov  (was: Dmitriy Shabalin)

> Web Console: Implement usage tracing
> 
>
> Key: IGNITE-4472
> URL: https://issues.apache.org/jira/browse/IGNITE-4472
> Project: Ignite
>  Issue Type: Task
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>
> We need to track some kind of "activity scores" for users.
> Activities:
> # Configuration
> # SQL
> # Demo
> And show that score on admin panel.
> May be this could be implemented by some library.



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

[jira] [Commented] (IGNITE-4772) CPP: Add documentation for LoadCache feature

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4772:
-

[~isapego], good start, thanks! I did minor edits though.

Could you improve the doc a little bit this way:
* Let's add read-through, write-through and write-behind sections using Java 
versions as a template 
(https://apacheignite.readme.io/docs/persistent-store#section-read-through-and-write-through).
 However, I would made C++ version even better by adding a code snippet showing 
how you define a cache configuration (C++ and Spring XML) and specify 
"write-through" and "read-through" there.
* Please add a code snippet to "Cache Loading" section which will show how we 
get a reference to a cache and initiate the preloading to it.

> CPP: Add documentation for LoadCache feature
> 
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: C++, DML, cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client 
> (IGNITE-4670) and needs proper documentation on 
> [readme.io|https://apacheignite-cpp.readme.io/docs]



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

[jira] [Closed] (IGNITE-4620) CPP: Add documentation for DML

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-4620.
---

> CPP: Add documentation for DML
> --
>
> Key: IGNITE-4620
> URL: https://issues.apache.org/jira/browse/IGNITE-4620
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 1.9
>
>
> We need to add documentation for DML support once its implemented in C++ 
> client.



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

[jira] [Updated] (IGNITE-4248) Slf4jLogger ignores IGNITE_QUIET system property

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4248:
-
Fix Version/s: (was: 2.0)
   1.9

> Slf4jLogger ignores IGNITE_QUIET system property
> 
>
> Key: IGNITE-4248
> URL: https://issues.apache.org/jira/browse/IGNITE-4248
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
> Fix For: 1.9
>
>
> {{Slf4jLogger}} writes in quiet mode into {{System.out}} regardless of the 
> value of {{IGNITE_QUEIT}} system property.
> Also {{JclLogger}} and {{HadoopIgfsJclLogger}} ignore this property and 
> should be fixed.



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

[jira] [Updated] (IGNITE-4167) Add an option to avoid printing out sensitive data into logs

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-4167:

Fix Version/s: 1.9

> Add an option to avoid printing out sensitive data into logs
> 
>
> Key: IGNITE-4167
> URL: https://issues.apache.org/jira/browse/IGNITE-4167
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Denis Kholodov
>Assignee: Alexandr Kuramshin
> Fix For: 1.9
>
>
>
> We are seeing sensitive cache data being output in ignite debug logging. I've 
> tracked it down to at least two places:
> 1. GridToStringBuilder uses reflection to print all fields in cache objects 
> that are not annotated with @GridToStringExclude
> 2. GridCacheMapEntry does a direct toString() call on the value objects in a 
> debug log
> As a fabric platform, we won't always have control over the object classes 
> being added to/retrieved from the cache.
> We must always assume that all keys and values are sensitive and should not 
> be outputted in logs except in local debugging situations. To this end, we 
> need a configuration option (turned OFF by default) that allows keys/values 
> to be written to log messages.
>  



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

[jira] [Commented] (IGNITE-4574) Introduce user value types to H2 w/custom conversion logic

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-4574:
---

Sergey, can you please add a usage examples to the description? I am struggling 
to understand what this feature means.

> Introduce user value types to H2 w/custom conversion logic
> --
>
> Key: IGNITE-4574
> URL: https://issues.apache.org/jira/browse/IGNITE-4574
> Project: Ignite
>  Issue Type: Sub-task
>  Components: SQL
>Reporter: Alexander Paschenko
>Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-4772) CPP: Add documentation for LoadCache feature

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4772:

Labels: C++ DML cpp documentation  (was: DML cpp documentation)

> CPP: Add documentation for LoadCache feature
> 
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: C++, DML, cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client 
> (IGNITE-4670) and needs proper documentation on 
> [readme.io|https://apacheignite-cpp.readme.io/docs]



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

[jira] [Updated] (IGNITE-4772) CPP: Add documentation for LoadCache feature

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4772:

Labels: DML cpp documentation  (was: cpp documentation)

> CPP: Add documentation for LoadCache feature
> 
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: DML, cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client 
> (IGNITE-4670) and needs proper documentation on 
> [readme.io|https://apacheignite-cpp.readme.io/docs]



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

[jira] [Comment Edited] (IGNITE-4617) CPP: Implement Field-access methods for binary objects

[Igor Sapego (JIRA)]

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

Igor Sapego edited comment on IGNITE-4617 at 3/2/17 7:12 PM:
-

Ready for review.

[~ptupitsyn], [~vozerov] please, take a look. I've made some changes that 
affect Java and .NET and I need your opinion as you are much more experienced 
in these parts than me.


was (Author: isapego):
Ready for review.

[~ptupitsyn], [~vozerov] please, take a look guys. I've made some changes that 
affect Java and .NET and I need your opinion as you are much more experienced 
in these parts than me.

> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> Currently we have very limited implementation of binary objects that does not 
>  provide access to fields of the binary object. At least such methods as 
> {{HasField}} and {{GetField}} should be implemented.



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

[jira] [Updated] (IGNITE-4772) CPP: Add documentation for LoadCache feature

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4772:

Description: {{LoadCache}} feature has been implemented recently for C++ 
client (IGNITE-4670) and needs proper documentation on 
[readme.io|https://apacheignite-cpp.readme.io/docs]  (was: {{LoadCache}} 
feature has been implemented recently for C++ client (IGNITE-4670) and needs 
proper documentation on the [readme.io|https://apacheignite-cpp.readme.io/docs])

> CPP: Add documentation for LoadCache feature
> 
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client 
> (IGNITE-4670) and needs proper documentation on 
> [readme.io|https://apacheignite-cpp.readme.io/docs]



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

[jira] [Updated] (IGNITE-4772) CPP: Add documentation for LoadCache feature

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4772:

Description: {{LoadCache}} feature has been implemented recently for C++ 
client (IGNITE-4670) and needs proper documentation on the 
[readme.io|https://apacheignite-cpp.readme.io/docs]  (was: {{LoadCache}} 
feature has been implemented recently for C++ client (IGNITE-4670) and needs 
proper documentation on the readme.io)

> CPP: Add documentation for LoadCache feature
> 
>
> Key: IGNITE-4772
> URL: https://issues.apache.org/jira/browse/IGNITE-4772
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp, documentation
> Fix For: 1.9
>
>
> {{LoadCache}} feature has been implemented recently for C++ client 
> (IGNITE-4670) and needs proper documentation on the 
> [readme.io|https://apacheignite-cpp.readme.io/docs]



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

[jira] [Created] (IGNITE-4772) CPP: Add documentation for LoadCache feature

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-4772:
---

 Summary: CPP: Add documentation for LoadCache feature
 Key: IGNITE-4772
 URL: https://issues.apache.org/jira/browse/IGNITE-4772
 Project: Ignite
  Issue Type: Task
  Components: documentation, platforms
Affects Versions: 1.8
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.9


{{LoadCache}} feature has been implemented recently for C++ client 
(IGNITE-4670) and needs proper documentation on the readme.io



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

[jira] [Commented] (IGNITE-4617) CPP: Implement Field-access methods for binary objects

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-4617:
-

Implemented proposed approach for C++, .NET and Java.

> CPP: Implement Field-access methods for binary objects
> --
>
> Key: IGNITE-4617
> URL: https://issues.apache.org/jira/browse/IGNITE-4617
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> Currently we have very limited implementation of binary objects that does not 
>  provide access to fields of the binary object. At least such methods as 
> {{HasField}} and {{GetField}} should be implemented.



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

[jira] [Commented] (IGNITE-4758) Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple memory policies

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-4758:
-

Implemented allocating dedicated MemoryPolicy for internal caches, added tests 
for all configuration validation cases available at the moment.

> Introduce MemoryPolicy configuration and adapt PageMemory concept to multiple 
> memory policies
> -
>
> Key: IGNITE-4758
> URL: https://issues.apache.org/jira/browse/IGNITE-4758
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>   Original Estimate: 336h
>  Time Spent: 24h
>  Remaining Estimate: 312h
>
> h2. Acceptance Criteria
> # For each named *MemoryPolicy* described in configuration new named 
> *PageMemory* is created.
> # Each cache on startup is assigned to corresponding *PageMemory* instance 
> which is stored in context of the cache.
> # A default *PageMemory* is used to store content of caches with no 
> *MemoryPolicy* configured.



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

[jira] [Updated] (IGNITE-603) [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov updated IGNITE-603:
---
Description: 
Test have to be uncommented and fixed or the commented code have to be removed.

See comments at GG-3804.

Update at 2/3/17.

API has changed. So if we add initialization of "ignite" field to 
GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
uncomments tests you can get result like in attached file.

testSize2IsolatedMode and testSize2PrivateMode tests don't fail.


  was:
Test have to be uncommented and fixed or the commented code have to be removed.

See comments at GG-3804.

Update at 2/3/17.

API has changed. So if we add initialization of "ignite" field to 
GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
uncomments tests you can get result like in attached file.




> [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests
> -
>
> Key: IGNITE-603
> URL: https://issues.apache.org/jira/browse/IGNITE-603
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Alexander Menshikov
>  Labels: Muted_test
> Attachments: testSize2ContinuousMode.txt, testSize2IsolatedMode.txt, 
> testSize2PrivateMode.txt, testSize2SharedMode.txt
>
>
> Test have to be uncommented and fixed or the commented code have to be 
> removed.
> See comments at GG-3804.
> Update at 2/3/17.
> API has changed. So if we add initialization of "ignite" field to 
> GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
> uncomments tests you can get result like in attached file.
> testSize2IsolatedMode and testSize2PrivateMode tests don't fail.



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

[jira] [Updated] (IGNITE-603) [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov updated IGNITE-603:
---
Attachment: testSize2IsolatedMode.txt
testSize2PrivateMode.txt
testSize2ContinuousMode.txt

> [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests
> -
>
> Key: IGNITE-603
> URL: https://issues.apache.org/jira/browse/IGNITE-603
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Alexander Menshikov
>  Labels: Muted_test
> Attachments: testSize2ContinuousMode.txt, testSize2IsolatedMode.txt, 
> testSize2PrivateMode.txt, testSize2SharedMode.txt
>
>
> Test have to be uncommented and fixed or the commented code have to be 
> removed.
> See comments at GG-3804.
> Update at 2/3/17.
> API has changed. So if we add initialization of "ignite" field to 
> GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
> uncomments tests you can get result like in attached file.



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

[jira] [Updated] (IGNITE-603) [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov updated IGNITE-603:
---
Attachment: testSize2SharedMode.txt

> [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests
> -
>
> Key: IGNITE-603
> URL: https://issues.apache.org/jira/browse/IGNITE-603
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Alexander Menshikov
>  Labels: Muted_test
> Attachments: testSize2SharedMode.txt
>
>
> Test have to be uncommented and fixed or the commented code have to be 
> removed.
> See comments at GG-3804.
> Update at 2/3/17.
> API has changed. So if we add initialization of "ignite" field to 
> GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
> uncomments tests you can get result like in attached file.



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

[jira] [Updated] (IGNITE-603) [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov updated IGNITE-603:
---
Description: 
Test have to be uncommented and fixed or the commented code have to be removed.

See comments at GG-3804.

Update at 2/3/17.

API has changed. So if we add initialization of "ignite" field to 
GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
uncomments tests you can get result like in attached file.



  was:
Test have to be uncommented and fixed or the commented code have to be removed.

See comments at GG-3804.


> [Test] GridP2PMissedResourceCacheSizeSelfTest has commented tests
> -
>
> Key: IGNITE-603
> URL: https://issues.apache.org/jira/browse/IGNITE-603
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>Assignee: Alexander Menshikov
>  Labels: Muted_test
>
> Test have to be uncommented and fixed or the commented code have to be 
> removed.
> See comments at GG-3804.
> Update at 2/3/17.
> API has changed. So if we add initialization of "ignite" field to 
> GridP2PEventFilterExternalPath1 and GridP2PEventFilterExternalPath2 and 
> uncomments tests you can get result like in attached file.



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

[jira] [Commented] (IGNITE-3939) Compact long zero values binary representation

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-3939:
--

[Tests 
results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1587%2Fhead]

> Compact long zero values binary representation
> --
>
> Key: IGNITE-3939
> URL: https://issues.apache.org/jira/browse/IGNITE-3939
> Project: Ignite
>  Issue Type: Improvement
>  Components: binary
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> We can use separate type for Long zero values and exclude 8-byte value from 
> binary representation. This will reduce memory footprint and network load.
> Compatibility with previous versions MUST be preserved.



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

[jira] [Commented] (IGNITE-3386) Reentrant lock is lost when lock owner leaves topology

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-3386:
---

I already added it, you could check GridCacheWorkAfterRecreateLockTest

> Reentrant lock is lost when lock owner leaves topology
> --
>
> Key: IGNITE-3386
> URL: https://issues.apache.org/jira/browse/IGNITE-3386
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Evgenii Zhuravlev
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
> Attachments: LockIssueVer2.java
>
>
> If to create a lock with the following configuration 
> {{IgniteLock lock = ignite.reentrantLock("lock", true, true, true);}}
> and perform the following steps below
> 1) run the first node using {{LockIssue}} that is attached;
> 2) run the second node using {{LockIssue}};
> 3) stop the first node.
> you will get the following exception on the second node side (the lock 
> information will be lost and the second node won't recreate it ignore 
> "create=true" flag):
> {code}
> SEVERE:  Failed to compare and set: 
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync$1@67aea87d
> class org.apache.ignite.IgniteCheckedException: Failed to find reentrant lock 
> with given name: test
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:525)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:518)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils$23.call(GridCacheUtils.java:1648)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:891)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.compareAndSetGlobalState(GridCacheLockImpl.java:517)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:400)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:437)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:861)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.lock(GridCacheLockImpl.java:432)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1201)
>   at 
> com.bfm.amc.loaders.server.StartIgniteServer.main(StartIgniteServer.java:15)
> {code}
> However the issue is not 100% reproduced but it should be clear from the logs 
> what happens.



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

[jira] [Comment Edited] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur edited comment on IGNITE-4770 at 3/2/17 2:11 PM:


[~avinogradov],

Master and ignite-2.0 branches have the same problem.
If this fix is good, makes sense to copy it in other branches.


was (Author: daradurvs):
[~avinogradov],

Master and ignite-2.0 branches have the same problem.
If this fix good, makes sense to copy it in other branches.

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Comment Edited] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur edited comment on IGNITE-4770 at 3/2/17 2:10 PM:


[~avinogradov],

Master and ignite-2.0 branches have the same problem.
If this fix good, makes sense to copy it in other branches.


was (Author: daradurvs):
[~avinogradov],

Master and ignite-2.0 have same problem.
If this fix good, makes sense to copy it to another branches.

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Commented] (IGNITE-3939) Compact long zero values binary representation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3939:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3939 Compact long zero values binary representation



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

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

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

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


commit c893da70a9757b16b0799adc8eaa29fa1b03d06e
Author: tledkov-gridgain 
Date:   2016-12-21T11:54:33Z

IGNITE-4399: IGFS: Merged IgfsSecondaryFileSystem and 
IgfsSecondaryFileSystemV2 interfaces. This closes #1346.

commit c5882a85f4e3a1f61723ac54fd92f087684df6da
Author: devozerov 
Date:   2016-12-26T11:15:42Z

Merge branch 'master' into ignite-2.0

commit 7e73d0223a3f09cbe0b7094a2c04bdf9d63ca9be
Author: devozerov 
Date:   2016-12-28T09:54:47Z

Merge branch 'master' into ignite-2.0

commit 7d82d6a06b5e9f1f8cd2909b865e37d46b8da03f
Author: devozerov 
Date:   2016-12-28T09:58:11Z

IGNITE-3875: Introduced separate thread pool for data streamer. This closes 
#1173. This closes #1383.

commit a61b0eaff1817d84c0659e8a7e095f29e22800e1
Author: tledkov-gridgain 
Date:   2016-12-28T11:09:38Z

IGNITE-4405: Hadoop: implemented "readLine" method for HadoopDataInStream 
and HadoopDirectDataInput classes. This closes #1358.

commit 2df39a80d80e2575be61a902ccd48615796fcde9
Author: tledkov-gridgain 
Date:   2016-12-28T13:47:24Z

IGNITE-3961: IGFS: Added IgfsSecondaryFileSystem.affintiy() method. This 
closes #1114. This closes #1252.

commit 2e691d80ea4870c3e7b5b127792b66c920f72c39
Author: tledkov-gridgain 
Date:   2016-12-29T08:00:01Z

IGNITE-4462: IGFS: removed grid name from HadoopIgfsEndpoint. This closes 
#1368.

commit a9b1fc2b3840d47d7c978d9296e8ae6bdeb10be5
Author: tledkov-gridgain 
Date:   2016-12-29T08:07:22Z

IGNITE-4459: Hadoop: weighted planned is default one from now on. This 
closes #1391.

commit 1f743465d6875ef48b1835d03a78a0dbaf339bf6
Author: tledkov-gridgain 
Date:   2016-12-29T08:14:10Z

IGNITE-4458: Hadoop: "striped" shuffle mode is default from now on. This 
closes #1390.

commit 6090ebdfcd0ea3840b0d32cb10197b43615e1e89
Author: devozerov 
Date:   2017-01-05T09:23:06Z

Merge branch 'master' into ignite-2.0

commit 77ca2e636c73e464f833f227c4894df0785ae9e2
Author: devozerov 
Date:   2017-01-16T13:07:49Z

Merge branch 'master' into ignite-2.0

commit d14e0727b3dd61ab5ec2957133d77dbc25e9ba68
Author: tledkov-gridgain 
Date:   2017-01-16T13:36:25Z

IGNITE-4428: Hadoop: moved HadoopMapReducePlanner and dependent classes to 
public space. This closes #1389. This closes #1394.

commit f1365421c299b754a10edf8b6f156aeeb5ff0ce1
Author: tledkov-gridgain 
Date:   2017-01-16T13:57:27Z

IGNITE-4503: Hadoop: added boundary checks to HadoopDirectDataInput. This 
closes # 1416.

commit e08b6ff48916edfab2dbd5d62092be5a1f819a2f
Author: Pavel Tupitsyn 
Date:   2017-01-19T10:34:59Z

Merge branch 'master' into ignite-2.0

commit 43adf8a3f09c6b29fe3e70f62dbc58251d8d7cb9
Author: Ivan Veselovskiy 
Date:   2017-01-19T11:34:23Z

IGNITE-4219: Hadoop: fixed serialization of long strings. This closes #1409.

commit 454b9769e72775c5f6b44a36f0eef84bcce13bd7
Author: devozerov 
Date:   2017-01-19T11:34:43Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 4cd332b781cf700b99402eed2363f988f6403602
Author: Sergey Chugunov 
Date:   2017-01-19T12:05:09Z

IGNITE-4157 Use  discovery custom messages instead of marshaller cache - 
Fixes #1271.

Signed-off-by: Alexey Goncharuk 

commit d0a6c57aa26bca64ef68370c0ebdb5ce45bcc765
Author: Pavel Tupitsyn 
Date:   2017-01-19T14:10:41Z

IGNITE-4441 Define plugin API in .NET

This closes #1362

commit 34a97833905a33bdb31b8e4580a576c2142313a7
Author: Alexey Goncharuk 
Date:   2017-01-19T15:04:23Z

IGNITE-4157 - Added mapping update listener stub

commit e8377167b7b8dd020a93d92c743e4541dcd000ed
Author: Pavel Tupitsyn 
Date:   2017-01-20T10:00:40Z

Merge branch 'master' into ignite-2.0

commit 

[jira] [Commented] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-4770:


[~avinogradov],

Master and ignite-2.0 have same problem.
If this fix good, makes sense to copy it to another branches.

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Commented] (IGNITE-4577) Ensure that certain interface addresses can be excluded form node attributes

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-4577:
---

Implemented a new idea with using isReachable for sorting addresses. Review 
link: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-110

> Ensure that certain interface addresses can be excluded form node attributes
> 
>
> Key: IGNITE-4577
> URL: https://issues.apache.org/jira/browse/IGNITE-4577
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.0
>
>
> *Problem*
> Consider a case when node has some network interface which is not accessible 
> from the outside (e.g. in Docker container). Ignite adds this address to 
> attributes, which are shared with other nodes. Now if remote want to 
> communicate with local node chances that he will try to establish connection 
> with invalid address. 
> In the worst case connection will be impossible. We use {{AddressResolver}} 
> to handle this situation.
> However, it appears that {{AddressResolver}} cannot prevent certain address 
> to appear in address list. As a result users may experience communication 
> delays as we establish peer-to-peer connection in one thread, iterating over 
> all available addresses.
> *Proposed solution*
> We need to examine what happens when address resolver is set. May be it is 
> necessary to rethink how we handle returned object. E.g. {{null}} or empty 
> collection might mean that this address should not be included into the list 
> of address. However, it may break existing applications, so chances that 
> other solution is needed.



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

[jira] [Commented] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4770:


Github user daradurvs closed the pull request at:

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


> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Updated] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-4770:
---
Component/s: build

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Commented] (IGNITE-3386) Reentrant lock is lost when lock owner leaves topology

[Vladisav Jelisavcic (JIRA)]

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

Vladisav Jelisavcic commented on IGNITE-3386:
-

Great! Another remark - what happens with nodes awaiting on lock conditions 
once the lock is recreated? Will they remain blocked? Can you make a test for 
this also?

> Reentrant lock is lost when lock owner leaves topology
> --
>
> Key: IGNITE-3386
> URL: https://issues.apache.org/jira/browse/IGNITE-3386
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Evgenii Zhuravlev
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
> Attachments: LockIssueVer2.java
>
>
> If to create a lock with the following configuration 
> {{IgniteLock lock = ignite.reentrantLock("lock", true, true, true);}}
> and perform the following steps below
> 1) run the first node using {{LockIssue}} that is attached;
> 2) run the second node using {{LockIssue}};
> 3) stop the first node.
> you will get the following exception on the second node side (the lock 
> information will be lost and the second node won't recreate it ignore 
> "create=true" flag):
> {code}
> SEVERE:  Failed to compare and set: 
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync$1@67aea87d
> class org.apache.ignite.IgniteCheckedException: Failed to find reentrant lock 
> with given name: test
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:525)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:518)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils$23.call(GridCacheUtils.java:1648)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:891)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.compareAndSetGlobalState(GridCacheLockImpl.java:517)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:400)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:437)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:861)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.lock(GridCacheLockImpl.java:432)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1201)
>   at 
> com.bfm.amc.loaders.server.StartIgniteServer.main(StartIgniteServer.java:15)
> {code}
> However the issue is not 100% reproduced but it should be clear from the logs 
> what happens.



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

[jira] [Assigned] (IGNITE-4683) Need to avoid extra-copy to byte array when marshalling to cache object (e.g. return ByteBuffer)

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov reassigned IGNITE-4683:


Assignee: Igor Seliverstov  (was: Yakov Zhdanov)

> Need to avoid extra-copy to byte array when marshalling to cache object (e.g. 
> return ByteBuffer)
> 
>
> Key: IGNITE-4683
> URL: https://issues.apache.org/jira/browse/IGNITE-4683
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 2.0
>
>




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

[jira] [Assigned] (IGNITE-4681) Apply new future adapter

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov reassigned IGNITE-4681:


Assignee: Igor Seliverstov  (was: Yakov Zhdanov)

> Apply new future adapter
> 
>
> Key: IGNITE-4681
> URL: https://issues.apache.org/jira/browse/IGNITE-4681
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 2.0
>
> Attachments: GridFutAdapter over jdk8.java
>
>
> Attached is reference future adapter implementation. It is proven to consume 
> less memory and it does not require explicit locking on listen(). We need to 
> apply it.
> Known threats:
> # if future is completed normally, but with Throwable as result, get() throws 
> exception. This can be fixed with internal wrapper class
> # listener notification order changes - this is known to cause problems 
> org.apache.ignite.internal.processors.rest.ClientMemcachedProtocolSelfTest#testGetBulk
>  which is minor but still.



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

[jira] [Commented] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4770:
--

Merged to ignite-1.9 branch. Thanks for contribution.

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Resolved] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-4770.
--
   Resolution: Fixed
Fix Version/s: (was: 2.0)
   1.9

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 1.9
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Commented] (IGNITE-3386) Reentrant lock is lost when lock owner leaves topology

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-3386:
---

Vladislav, thanks for comments in PR, I added some minor corrections. Also, I 
think it's a good idea to log when new state for lock is created.

> Reentrant lock is lost when lock owner leaves topology
> --
>
> Key: IGNITE-3386
> URL: https://issues.apache.org/jira/browse/IGNITE-3386
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Evgenii Zhuravlev
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
> Attachments: LockIssueVer2.java
>
>
> If to create a lock with the following configuration 
> {{IgniteLock lock = ignite.reentrantLock("lock", true, true, true);}}
> and perform the following steps below
> 1) run the first node using {{LockIssue}} that is attached;
> 2) run the second node using {{LockIssue}};
> 3) stop the first node.
> you will get the following exception on the second node side (the lock 
> information will be lost and the second node won't recreate it ignore 
> "create=true" flag):
> {code}
> SEVERE:  Failed to compare and set: 
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync$1@67aea87d
> class org.apache.ignite.IgniteCheckedException: Failed to find reentrant lock 
> with given name: test
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:525)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:518)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils$23.call(GridCacheUtils.java:1648)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:891)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.compareAndSetGlobalState(GridCacheLockImpl.java:517)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:400)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:437)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:861)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.lock(GridCacheLockImpl.java:432)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1201)
>   at 
> com.bfm.amc.loaders.server.StartIgniteServer.main(StartIgniteServer.java:15)
> {code}
> However the issue is not 100% reproduced but it should be clear from the logs 
> what happens.



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

[jira] [Assigned] (IGNITE-4771) Building error - Apache Ignite 1.9.0 RC1

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur reassigned IGNITE-4771:
--

Assignee: (was: Vyacheslav Daradur)

> Building error - Apache Ignite 1.9.0 RC1
> 
>
> Key: IGNITE-4771
> URL: https://issues.apache.org/jira/browse/IGNITE-4771
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Priority: Blocker
>  Labels: build
>
> Valentin Kulichenko:
> Building with 'mvn clean package -DskipTests' under JDK8 fails with the
> error below. JDK7 is fine, though.
> {CODE}
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 12.626 s
> [INFO] Finished at: 2017-03-01T14:05:08-08:00
> [INFO] Final Memory: 80M/654M
> [INFO] 
> 
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> [ERROR]
> [ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_
> 92.jdk/Contents/Home/jre/../bin/javadoc @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/Users/vkulichenko/Downloads/apache-ignite-1.9.0-src/modules/tools/target/apidocs'
> dir.
> [ERROR] -> [Help 1]
> {CODE}
> dev-list: 
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-9-0-RC1-td14985.html



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

[jira] [Commented] (IGNITE-4765) Different partition mapping for caches that use Fair Affinity Function

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-4765:
-

I think that in current implementation it is not a bug. It is ok that caches 
that was started on different topology versions will have different assignments 
because they have different input for assignment calculation. But this can lead 
to broken data co-location (from user point of view). 

Perharps it can be fixed in the following way: All co-located caches should use 
the same instance of affinity function. In this case we can calculate 
assignments only once for all caches (at this moment assignment will be 
calculated for each cache separately). Newly created cache should use already 
calculated assignment for major topology version.


> Different partition mapping for caches that use Fair Affinity Function
> --
>
> Key: IGNITE-4765
> URL: https://issues.apache.org/jira/browse/IGNITE-4765
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alper Tekinalp
>
> Caches created on different topology versions with fair affinity funtion may 
> have different partition mapping. The cause of this problem is fair affinity 
> function calculates partition mappings based on previous assignments. When 
> rebalancing partitions previous assignments for a cache is known and new 
> assignment calculated based on that. But when you create a new cache there is 
> no previous assignments and the calculation is different. 
> Reproduction steps:
> - Start node1
> - Start cache1
> - Start node2
> - Partitions for cache1 will be rebalanced
> - Start cache2
> - Check partition mapping for both cache1 and cache2



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

[jira] [Commented] (IGNITE-3386) Reentrant lock is lost when lock owner leaves topology

[Vladisav Jelisavcic (JIRA)]

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

Vladisav Jelisavcic commented on IGNITE-3386:
-

Good job, thank you for the contribution, sorry for delayed response. I made 
some minor comments in PR. 
What happens if failoverSafe == false? I'm thinking, if user opted for lock 
that explicitly throws exceptions if something goes wrong, do we need to 
somehow inform him that new state has been created? What do you think?

> Reentrant lock is lost when lock owner leaves topology
> --
>
> Key: IGNITE-3386
> URL: https://issues.apache.org/jira/browse/IGNITE-3386
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Evgenii Zhuravlev
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
> Attachments: LockIssueVer2.java
>
>
> If to create a lock with the following configuration 
> {{IgniteLock lock = ignite.reentrantLock("lock", true, true, true);}}
> and perform the following steps below
> 1) run the first node using {{LockIssue}} that is attached;
> 2) run the second node using {{LockIssue}};
> 3) stop the first node.
> you will get the following exception on the second node side (the lock 
> information will be lost and the second node won't recreate it ignore 
> "create=true" flag):
> {code}
> SEVERE:  Failed to compare and set: 
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync$1@67aea87d
> class org.apache.ignite.IgniteCheckedException: Failed to find reentrant lock 
> with given name: test
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:525)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync$1.call(GridCacheLockImpl.java:518)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils$23.call(GridCacheUtils.java:1648)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:891)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.compareAndSetGlobalState(GridCacheLockImpl.java:517)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:400)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryAcquire(GridCacheLockImpl.java:437)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:861)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.lock(GridCacheLockImpl.java:432)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1201)
>   at 
> com.bfm.amc.loaders.server.StartIgniteServer.main(StartIgniteServer.java:15)
> {code}
> However the issue is not 100% reproduced but it should be clear from the logs 
> what happens.



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

[jira] [Commented] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4770:


GitHub user daradurvs opened a pull request:

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

IGNITE-4770



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

$ git pull https://github.com/daradurvs/ignite ignite-4770

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

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


commit ce3b7dab3aeeeca9e5f0357ab80309ecf75999ab
Author: Vyacheslav Daradur 
Date:   2017-03-02T12:24:32Z

ignite-4770: workaround solution




> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Updated] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4770:
-
Description: 
Problem:
parent/pom.xml:455 contains following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this script generates "Follow us" at the bottom of the 
incubator-ignite/target/javadoc/core/index.html. 

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}

addition of "--allow-script-in-comments"
cause compilation issues on any JDK8 before 1.8.0_121-b13
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - invalid flag:
--allow-script-in-comments
{noformat}

Solution:
Need to keep button at the bottom of the page, but fix compilation errors.

  was:
Problem:
parent/pom.xml:455 contains following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this script generates "Follow us" at the bottom of the 
incubator-ignite/target/javadoc/core/index.html. 

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}

Solution:
Need to keep button at the bottom of the page, but fix compilation errors.


> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> addition of "--allow-script-in-comments"
> cause compilation issues on any JDK8 before 1.8.0_121-b13
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Resolved] (IGNITE-4771) Building error - Apache Ignite 1.9.0 RC1

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur resolved IGNITE-4771.

Resolution: Duplicate

> Building error - Apache Ignite 1.9.0 RC1
> 
>
> Key: IGNITE-4771
> URL: https://issues.apache.org/jira/browse/IGNITE-4771
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Blocker
>  Labels: build
>
> Valentin Kulichenko:
> Building with 'mvn clean package -DskipTests' under JDK8 fails with the
> error below. JDK7 is fine, though.
> {CODE}
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 12.626 s
> [INFO] Finished at: 2017-03-01T14:05:08-08:00
> [INFO] Final Memory: 80M/654M
> [INFO] 
> 
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
> MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - invalid flag:
> --allow-script-in-comments
> [ERROR]
> [ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_
> 92.jdk/Contents/Home/jre/../bin/javadoc @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/Users/vkulichenko/Downloads/apache-ignite-1.9.0-src/modules/tools/target/apidocs'
> dir.
> [ERROR] -> [Help 1]
> {CODE}
> dev-list: 
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-9-0-RC1-td14985.html



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

[jira] [Assigned] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur reassigned IGNITE-4770:
--

Assignee: Vyacheslav Daradur

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Created] (IGNITE-4771) Building error - Apache Ignite 1.9.0 RC1

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-4771:
--

 Summary: Building error - Apache Ignite 1.9.0 RC1
 Key: IGNITE-4771
 URL: https://issues.apache.org/jira/browse/IGNITE-4771
 Project: Ignite
  Issue Type: Bug
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
Priority: Blocker


Valentin Kulichenko:
Building with 'mvn clean package -DskipTests' under JDK8 fails with the
error below. JDK7 is fine, though.
{CODE}
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 12.626 s
[INFO] Finished at: 2017-03-01T14:05:08-08:00
[INFO] Final Memory: 80M/654M
[INFO] 

[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-javadoc-plugin:2.10.1:jar (module-javadoc) on project ignite-tools:
MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - invalid flag:
--allow-script-in-comments
[ERROR]
[ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_
92.jdk/Contents/Home/jre/../bin/javadoc @options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/vkulichenko/Downloads/apache-ignite-1.9.0-src/modules/tools/target/apidocs'
dir.
[ERROR] -> [Help 1]
{CODE}

dev-list: 
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-9-0-RC1-td14985.html



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

[jira] [Updated] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4770:
-
Description: 
Problem:
parent/pom.xml:455 contained following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this script generates "Follow us" at the bottom of the 
incubator-ignite/target/javadoc/core/index.html. 

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}

Solution:
Need to keep button at the bottom of the page, but fix compilation errors.

  was:
 parent/pom.xml:455 contained following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}


> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
> Fix For: 2.0
>
>
> Problem:
> parent/pom.xml:455 contained following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Updated] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4770:
-
Description: 
Problem:
parent/pom.xml:455 contains following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this script generates "Follow us" at the bottom of the 
incubator-ignite/target/javadoc/core/index.html. 

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}

Solution:
Need to keep button at the bottom of the page, but fix compilation errors.

  was:
Problem:
parent/pom.xml:455 contained following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this script generates "Follow us" at the bottom of the 
incubator-ignite/target/javadoc/core/index.html. 

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}

Solution:
Need to keep button at the bottom of the page, but fix compilation errors.


> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
> Fix For: 2.0
>
>
> Problem:
> parent/pom.xml:455 contains following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this script generates "Follow us" at the bottom of the 
> incubator-ignite/target/javadoc/core/index.html. 
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}
> Solution:
> Need to keep button at the bottom of the page, but fix compilation errors.



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

[jira] [Updated] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4770:
-
Fix Version/s: 2.0

> Script inside javadoc bottom cause compilation error at 1.8.0_121-b13
> -
>
> Key: IGNITE-4770
> URL: https://issues.apache.org/jira/browse/IGNITE-4770
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
> Fix For: 2.0
>
>
>  parent/pom.xml:455 contained following:
> {noformat}
> !function(d,s,id){var 
> js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
>  'script', 'twitter-wjs');
> {noformat}
> this cause compilation error during
> {noformat}
> mvn clean package -DskipTests
> {noformat}
> error
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
> project ignite-tools: MavenReportException: Error while creating archive:
> [ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
> JavaScript.
> [ERROR] Use --allow-script-in-comments to allow use of JavaScript.
> {noformat}



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

[jira] [Created] (IGNITE-4770) Script inside javadoc bottom cause compilation error at 1.8.0_121-b13

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-4770:


 Summary: Script inside javadoc bottom cause compilation error at 
1.8.0_121-b13
 Key: IGNITE-4770
 URL: https://issues.apache.org/jira/browse/IGNITE-4770
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Vinogradov


 parent/pom.xml:455 contained following:

{noformat}
!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
{noformat}

this cause compilation error during
{noformat}
mvn clean package -DskipTests
{noformat}

error
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar (module-javadoc) on 
project ignite-tools: MavenReportException: Error while creating archive:
[ERROR] Exit code: 1 - javadoc: error - Argument for -bottom contains 
JavaScript.
[ERROR] Use --allow-script-in-comments to allow use of JavaScript.
{noformat}



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

[jira] [Commented] (IGNITE-4633) Initiate DDL operation through custom discovery message

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4633:
-

3) There is no need for {{GridDdlCommand}} interface. Let's remove it and move 
3 existing method to DDL processor. This way we will follow our standard 
approach when callbacks are placed directly inside relevant processor:
{code}
class DdlStatementsProcessor {
Collection filterNodes(String cacheName, 
AffinityTopologyVersion topVer);
void onCreateIndexInit(CreateIndexArguments args);
void onCreateIndexAck(CreateIndexArguments args);
}
{code}

> Initiate DDL operation through custom discovery message
> ---
>
> Key: IGNITE-4633
> URL: https://issues.apache.org/jira/browse/IGNITE-4633
> Project: Ignite
>  Issue Type: Sub-task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Design considerations:
> 1) Create generic DDL custom discovery message pair - {{INIT}} and {{ACK}} 
> messages - which will hold concrete DDL commands.
> 2) Originator must generate unique message ID to be able to track it later.
> 3) Coordinator calculates all participants through affinity API and adds them 
> to message.
> 4) {{INIT}} message goes through the ring and:performs some fast preliminary 
> checks if necessary and collects error; in particular it may verify whether 
> schema change is valid to allow for fail-fast client notification.;
> 5) If at least one error occurs during {{INIT}} stage, originator may throw 
> exception to the user.
> 6) {{ACK}} message schedules asynchronous execution of the command.



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

[jira] [Created] (IGNITE-4769) Handle possibly duplicated discovery messages

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4769:
---

 Summary: Handle possibly duplicated discovery messages
 Key: IGNITE-4769
 URL: https://issues.apache.org/jira/browse/IGNITE-4769
 Project: Ignite
  Issue Type: Sub-task
  Components: SQL
Reporter: Vladimir Ozerov
 Fix For: 2.0


*Problem*
It is known that discovery message notifications could be invoked more than 
once in case of unsuccessful concurrent topology changes. We need to protect 
DDL logic from it somehow.

*Proposed solution*
1) Add bounded set holding unique operation IDs.
2) Ignore init/ack message when ID already exists in history set.
3) Control maximum history size through system property.



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

[jira] [Assigned] (IGNITE-3837) ODBC: Escape sequences: Support CONVERT function.

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov reassigned IGNITE-3837:
--

Assignee: Sergey Kalashnikov

> ODBC: Escape sequences: Support CONVERT function.
> -
>
> Key: IGNITE-3837
> URL: https://issues.apache.org/jira/browse/IGNITE-3837
> Project: Ignite
>  Issue Type: Sub-task
>  Components: odbc
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Sergey Kalashnikov
>  Labels: odbc
> Fix For: 1.9
>
>
> Need to implement parsing of the CONVERT function: 
> https://msdn.microsoft.com/en-us/library/ms715381(v=vs.85).aspx.
> Note the type conversion (e.g. {{SQL_VARCHAR}} -> {{VARCHAR}})



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

[jira] [Commented] (IGNITE-4633) Initiate DDL operation through custom discovery message

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4633:
-

Preliminary review comments:
1) Why do we need separate topic for DDL operations? Can we use existing 
{{QUERY}} topic?
2) Let's revert all changes to {{GridH2IndexingMessageFactory}} and move DDL 
messages to core.

> Initiate DDL operation through custom discovery message
> ---
>
> Key: IGNITE-4633
> URL: https://issues.apache.org/jira/browse/IGNITE-4633
> Project: Ignite
>  Issue Type: Sub-task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>
> Design considerations:
> 1) Create generic DDL custom discovery message pair - {{INIT}} and {{ACK}} 
> messages - which will hold concrete DDL commands.
> 2) Originator must generate unique message ID to be able to track it later.
> 3) Coordinator calculates all participants through affinity API and adds them 
> to message.
> 4) {{INIT}} message goes through the ring and:performs some fast preliminary 
> checks if necessary and collects error; in particular it may verify whether 
> schema change is valid to allow for fail-fast client notification.;
> 5) If at least one error occurs during {{INIT}} stage, originator may throw 
> exception to the user.
> 6) {{ACK}} message schedules asynchronous execution of the command.



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

[jira] [Assigned] (IGNITE-4614) .NET: Binary schema is not reset in BinaryReader

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-4614:


Assignee: Pavel Tupitsyn

> .NET: Binary schema is not reset in BinaryReader
> 
>
> Key: IGNITE-4614
> URL: https://issues.apache.org/jira/browse/IGNITE-4614
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
>
> {{BinaryReader}} does not reset {{_frame.Schema}} and {{_frame.SchemaMap}}. 
> This can cause bugs with certain object nesting layouts. 
> Make sure to write a test that reproduces this issue first.



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

[jira] [Assigned] (IGNITE-4344) Client node allocates off heap memories for caches

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov reassigned IGNITE-4344:


Assignee: Semen Boikov

> Client node allocates off heap memories for caches
> --
>
> Key: IGNITE-4344
> URL: https://issues.apache.org/jira/browse/IGNITE-4344
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6, 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Semen Boikov
> Fix For: 1.9
>
> Attachments: OffHeapClientTest.patch
>
>
> Client node should not allocate memories. Test attached.



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

[jira] [Created] (IGNITE-4768) Tx cache protocol change: notify client node from backups

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-4768:


 Summary: Tx cache protocol change: notify client node from backups
 Key: IGNITE-4768
 URL: https://issues.apache.org/jira/browse/IGNITE-4768
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
 Fix For: 2.0


Currently on prepare and finish steps backups first reply to primary and then 
primary replies to client, need check if it is possible to notify client 
directly from backups.



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

[jira] [Updated] (IGNITE-4753) DOAP: Node.JS => Node.js

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4753:
-
Fix Version/s: (was: 2.0)
   1.9

> DOAP: Node.JS => Node.js
> 
>
> Key: IGNITE-4753
> URL: https://issues.apache.org/jira/browse/IGNITE-4753
> Project: Ignite
>  Issue Type: Task
>Reporter: Sebb
>Priority: Trivial
> Fix For: 1.9
>
>
> The other project DOAPs use Node.js rather than Node.JS.
> Please could you change the Ignite DOAP accordingly?
> Thanks



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

[jira] [Commented] (IGNITE-2310) Lock cache partition for affinityRun/affinityCall execution

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2310:


Github user tledkov-gridgain closed the pull request at:

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


> Lock cache partition for affinityRun/affinityCall execution
> ---
>
> Key: IGNITE-2310
> URL: https://issues.apache.org/jira/browse/IGNITE-2310
> Project: Ignite
>  Issue Type: New Feature
>  Components: cache
>Reporter: Valentin Kulichenko
>Assignee: Taras Ledkov
>Priority: Critical
>  Labels: community
> Fix For: 1.8
>
>
> Partition of a key passed to {{affinityRun}} must be located on the affinity 
> node when a compute job is being sent to the node. The partition has to be 
> locked on the cache until the compute job is being executed. This will let to 
> execute queries safely (Scan or local SQL) over the data that is located 
> locally in the locked partition.
> In addition Ignite Compute API has to be extended by adding {{affinityCall}} 
> and {{affinityRun}} methods that accept list of caches which partitions have 
> to be locked at the time a compute task is being executed.
> Test cases to validate the functionality:
> 1) local SQL query over data located in a concrete partition in multple 
> caches.
> - create cache Organisation cache and create Persons cache.
> - collocate Persons by 'organisationID';
> - send {{affinityRun}} using 'organisationID' as an affinity key and passing 
> Organisation and Persons caches' names to the method to be sure that the 
> partition will be locked on caches;
> - execute local SQL query "SELECT * FROM Persons as p, Organisation as o 
> WHERE p.orgId=o.id' on a changing topology. The result set must be complete, 
> the partition over which the query will be executed mustn't be moved to the 
> other node. Due to affinity collocation the partition number will be the same 
> for all Persons that belong to particular 'organisationID'
> 2) Scan Query over particular partition that is locked when {{affinityCall}} 
> is executed.  
> UPD (YZ May, 31)
> # If closure arrives to node but partition is not there it should be silently 
> failed over to current owner.
> # I don't think user should provide list of caches. How about reserving only 
> one partition, but evict partitions after all partitions in all caches (with 
> same affinity function) on this node are locked for eviction. [~sboikov], can 
> you please comment? It seems this should work faster for closures and will 
> hardly affect rebalancing stuff.
> # I would add method {{affinityCall(int partId, String cacheName, 
> IgniteCallable)}} and same for Runnable. This will allow me not to mess with 
> affinity key in case I know partition before.
> UPD (SB, June, 01)
> Yakov, I think it is possible to implement this 'locking for evictions' 
> approach, but personally I better like partitions reservation:
> - approach with reservation already implemented and works fine in sql queries
> - partition reservation is just CAS operation, if we need do ~10 reservation 
> I think this will be negligible comparing to  job execution time
> - now caches are rebalanced completely independently and changing this be 
> complicated refactoring
> - I see some difficulties how to understand that caches have same affinity. 
> If user uses custom function should he implement 'equals'? For standard 
> affinity functions user can set backup filter, what do in this case? should 
> user implement 'equals' for filter? Even if affinity functions are the same 
> cache configuration can have node filter, so affinity mapping will be 
> different. 



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

[jira] [Assigned] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin reassigned IGNITE-4767:
--

Assignee: Alexandr Kuramshin

> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Alexandr Kuramshin
> Fix For: 2.0
>
>
> There is too much code places like:
> {noformat}
> try {
>   return txFuture.get();
> }
> catch (IgniteCheckedException e) {
>   tx.rollbackAsync();
>   throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
>   return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
>   try {
>   tx.rollbackAsync();
>   }
>   catch (Throwable inner) {
>   e.addSuppressed(inner);
>   }
>   throw e;
> }
> {noformat}



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

[jira] [Commented] (IGNITE-4577) Ensure that certain interface addresses can be excluded form node attributes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4577:


Github user ezhuravl closed the pull request at:

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


> Ensure that certain interface addresses can be excluded form node attributes
> 
>
> Key: IGNITE-4577
> URL: https://issues.apache.org/jira/browse/IGNITE-4577
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Evgenii Zhuravlev
> Fix For: 2.0
>
>
> *Problem*
> Consider a case when node has some network interface which is not accessible 
> from the outside (e.g. in Docker container). Ignite adds this address to 
> attributes, which are shared with other nodes. Now if remote want to 
> communicate with local node chances that he will try to establish connection 
> with invalid address. 
> In the worst case connection will be impossible. We use {{AddressResolver}} 
> to handle this situation.
> However, it appears that {{AddressResolver}} cannot prevent certain address 
> to appear in address list. As a result users may experience communication 
> delays as we establish peer-to-peer connection in one thread, iterating over 
> all available addresses.
> *Proposed solution*
> We need to examine what happens when address resolver is set. May be it is 
> necessary to rethink how we handle returned object. E.g. {{null}} or empty 
> collection might mean that this address should not be included into the list 
> of address. However, it may break existing applications, so chances that 
> other solution is needed.



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

[jira] [Closed] (IGNITE-4659) Migrate to webpack@2

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-4659.
--
Assignee: (was: Andrey Novikov)

> Migrate to webpack@2
> 
>
> Key: IGNITE-4659
> URL: https://issues.apache.org/jira/browse/IGNITE-4659
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Dmitriy Shabalin
>




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

[jira] [Assigned] (IGNITE-4659) Migrate to webpack@2

[Andrey Novikov (JIRA)]

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

Andrey Novikov reassigned IGNITE-4659:
--

Assignee: Andrey Novikov  (was: Vasiliy Sisko)

> Migrate to webpack@2
> 
>
> Key: IGNITE-4659
> URL: https://issues.apache.org/jira/browse/IGNITE-4659
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
>




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

[jira] [Assigned] (IGNITE-1393) [Test] AssertionError when stop node executing transaction - GridCacheStopSelfTest

[Ryabov Dmitrii (JIRA)]

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

Ryabov Dmitrii reassigned IGNITE-1393:
--

Assignee: Ryabov Dmitrii

> [Test] AssertionError when stop node executing transaction - 
> GridCacheStopSelfTest 
> ---
>
> Key: IGNITE-1393
> URL: https://issues.apache.org/jira/browse/IGNITE-1393
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Ryabov Dmitrii
>  Labels: Muted_test
>
> I fixed GridCacheStopSelfTest which was disabled for long time, now it fails 
> because of asserts:
> {noformat}
> [10:53:02,362][ERROR][async-runner-1][GridNearTxLocal] Heuristic transaction 
> failure.
> class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Failed to locally write to cache (all transaction entries will be 
> invalidated, however there was a window when entries for this transaction 
> were visible to others): GridNearTxLocal [nearLocallyMapped=false, 
> colocatedLocallyMapped=true, hasRemoteLocks=false, 
> mappings=[009f5238-db3d-426f-b787-9a4a156e8000], super=GridDhtTxLocalAdapter 
> [dhtThreadId=101, needsCompletedVers=false, nearNodes=[], dhtNodes=[], 
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1]=IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], cacheId=1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=22, hasValBytes=true], 
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl [val=22, 
> hasValBytes=true]], prevVal=[op=CREATE, val=UserCacheObjectImpl [val=22, 
> hasValBytes=true]], entryProcessorsCol=null, entryProcessorCalcVal=null, 
> ttl=-1, conflictExpireTime=-1, conflictVer=null, explicitVer=null, 
> dhtVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1, 
> globalTime=1441781582327, order=1441781581691], filters=[], 
> filtersPassed=false, filtersSet=true, entry=GridDhtColocatedCacheEntry 
> [super=GridDhtCacheEntry [rdrs=[], locPart=GridDhtLocalPartition [id=22, 
> mapPubSize=1, rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0], 
> state=OWNING, reservations=0, empty=false, createTime=09/09/2015 10:53:02, 
> mapPubSize=1], super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=22, hasValBytes=true], val=CacheObjectImpl 
> [val=22, hasValBytes=true], startVer=1441781581658, ver=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582327, 
> order=1441781581691], hash=2018242870, extras=null, flags=2, 
> prepared=false, locked=true, nodeId=009f5238-db3d-426f-b787-9a4a156e8000, 
> locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0, 
> xidVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1, 
> globalTime=1441781582217, order=1441781581591]]}, completedBase=null, 
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217, 
> order=1441781581591], writeVer=GridCacheVersion [topVer=53261582, 
> nodeOrderDrId=1, globalTime=1441781582327, order=1441781581691], 
> implicit=false, implicitSingle=false, loc=true, threadId=101, 
> startTime=1441781582212, nodeId=009f5238-db3d-426f-b787-9a4a156e8000, 
> startVer=GridCacheVersion [topVer=53261582, nodeOrderDrId=1, 
> globalTime=1441781582218, order=1441781581611], endVer=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582336, 
> order=1441781581738], isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, 
> timeout=0, sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion 
> [topVer=53261582, nodeOrderDrId=1, globalTime=1441781582217, 
> order=1441781581591], finalizing=NONE, preparing=false, state=COMMITTED, 
> timedOut=false, topVer=AffinityTopologyVersion [topVer=1, minorTopVer=0], 
> duration=138ms, onePhaseCommit=true], size=1]]]
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:1036)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.finish(GridNearTxLocal.java:654)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:749)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$3.apply(GridNearTxLocal.java:741)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.commitAsync(GridNearTxLocal.java:741)
>   at 
> 

[jira] [Created] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-4767:
--

 Summary: rollback exception hides the origin exception (e.g. 
commit)
 Key: IGNITE-4767
 URL: https://issues.apache.org/jira/browse/IGNITE-4767
 Project: Ignite
  Issue Type: Bug
  Components: cache, general
Affects Versions: 1.8
Reporter: Alexandr Kuramshin
 Fix For: 2.0


There is too much code places like:
{noformat}
try {
return txFuture.get();
}
catch (IgniteCheckedException e) {
tx.rollbackAsync();

throw e;
}
{noformat}
where an error upon rollback hides the actual exception {{e}}.

This should be implemented in the way like try-with-resources does:
{noformat}
try {
return txFuture.get();
}
catch (IgniteCheckedException e1) {
try {
tx.rollbackAsync();
}
catch (Throwable inner) {
e.addSuppressed(inner);
}

throw e;
}
{noformat}




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

[jira] [Updated] (IGNITE-4766) Relax worker thread wakeup logic in StipedExecutor

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4766:

Affects Version/s: (was: 1.0)
   1.9

> Relax worker thread wakeup logic in StipedExecutor
> --
>
> Key: IGNITE-4766
> URL: https://issues.apache.org/jira/browse/IGNITE-4766
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.9
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> *Problem*
> Worker threads in {{StripedExecutor}} have {{parked}} state flag. When set to 
> {{true}} NIO threads will call {{LockSupport.unpark}} after submitting new 
> task to a queue.
> The problem is that this flag is only changed by worker thread. Thus, if NIO 
> worker submitted a new task and called {{unpark}}, worker will clean up 
> {{parked}} state only after real wake up what may take microseconds. All 
> subsequent submits from NIO thread occurred during this time will also invoke 
> {{unpark}} thus generating high contention on the underlying OS primitives. 
> Namely, condition variables which ultimately delegates to {{futex}} on Linux.
> *Solution*
> NIO threads must be able to clear {{parked}} state as well. Some CAS magic 
> will be required there. This way we will minimize number of {{unapark}} calls.



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

[jira] [Created] (IGNITE-4766) Relax worker thread wakeup logic in StipedExecutor

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4766:
---

 Summary: Relax worker thread wakeup logic in StipedExecutor
 Key: IGNITE-4766
 URL: https://issues.apache.org/jira/browse/IGNITE-4766
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.0
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


*Problem*
Worker threads in {{StripedExecutor}} have {{parked}} state flag. When set to 
{{true}} NIO threads will call {{LockSupport.unpark}} after submitting new task 
to a queue.

The problem is that this flag is only changed by worker thread. Thus, if NIO 
worker submitted a new task and called {{unpark}}, worker will clean up 
{{parked}} state only after real wake up what may take microseconds. All 
subsequent submits from NIO thread occurred during this time will also invoke 
{{unpark}} thus generating high contention on the underlying OS primitives. 
Namely, condition variables which ultimately delegates to {{futex}} on Linux.

*Solution*
NIO threads must be able to clear {{parked}} state as well. Some CAS magic will 
be required there. This way we will minimize number of {{unapark}} calls.



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