[jira] [Updated] (IGNITE-3438) Caches: Add more info and examples to "Escape table and filed names" tooltip
[ https://issues.apache.org/jira/browse/IGNITE-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-3438: --- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Caches: Add more info and examples to "Escape table and filed names" tooltip > > > Key: IGNITE-3438 > URL: https://issues.apache.org/jira/browse/IGNITE-3438 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3629) Web Console: Implement test for backend API routes
[ https://issues.apache.org/jira/browse/IGNITE-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512068#comment-15512068 ] Andrey Novikov commented on IGNITE-3629: Reviewed. Maxim, please add ObjectId for test documents and create it before test run. > Web Console: Implement test for backend API routes > -- > > Key: IGNITE-3629 > URL: https://issues.apache.org/jira/browse/IGNITE-3629 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Maxim Afanasiev >Assignee: Maxim Afanasiev > > Need to implement integration tests for all backend routes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3438) Caches: Add more info and examples to "Escape table and filed names" tooltip
[ https://issues.apache.org/jira/browse/IGNITE-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512069#comment-15512069 ] Pavel Konstantinov commented on IGNITE-3438: Not bad in my opinion, but what do you think? > Caches: Add more info and examples to "Escape table and filed names" tooltip > > > Key: IGNITE-3438 > URL: https://issues.apache.org/jira/browse/IGNITE-3438 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-3437) Caches: Start size - rename to Onheap start size and add more info into tooltip
[ https://issues.apache.org/jira/browse/IGNITE-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reopened IGNITE-3437: Assignee: Vasiliy Sisko (was: Pavel Konstantinov) Neither label or tooltip doesn't contain the word "on-heap". Is this correct? > Caches: Start size - rename to Onheap start size and add more info into > tooltip > --- > > Key: IGNITE-3437 > URL: https://issues.apache.org/jira/browse/IGNITE-3437 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko > Fix For: 1.8 > > > And moe under "Mode" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3241) Rework Hibernate properties table as pair of fields.
[ https://issues.apache.org/jira/browse/IGNITE-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-3241. -- Assignee: (was: Andrey Novikov) > Rework Hibernate properties table as pair of fields. > > > Key: IGNITE-3241 > URL: https://issues.apache.org/jira/browse/IGNITE-3241 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > > Implement row editor as pair of fields how for Cluster - User attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3896) Cache POJO store with Percona and the MariaDB shoud correctry select dialect
[ https://issues.apache.org/jira/browse/IGNITE-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509570#comment-15509570 ] Vasiliy Sisko edited comment on IGNITE-3896 at 9/22/16 3:52 AM: Implemented dialect detection for MariaDB. Fixed generation of Generic DB dialect. was (Author: vsisko): Implemented rename of index field on change of field name. > Cache POJO store with Percona and the MariaDB shoud correctry select dialect > > > Key: IGNITE-3896 > URL: https://issues.apache.org/jira/browse/IGNITE-3896 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1842) Add dropdown list of existing fields for setting it in index
[ https://issues.apache.org/jira/browse/IGNITE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512006#comment-15512006 ] Vasiliy Sisko commented on IGNITE-1842: --- Implemented rename of index field on change of field name. > Add dropdown list of existing fields for setting it in index > > > Key: IGNITE-1842 > URL: https://issues.apache.org/jira/browse/IGNITE-1842 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: 1.8 > > > If user already set field list will be useful to select existing field from > dropdown list for index. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3892) BinaryWriterExImpl.doWriteClass is incorrect
[
https://issues.apache.org/jira/browse/IGNITE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-3892.
---
> BinaryWriterExImpl.doWriteClass is incorrect
>
>
> Key: IGNITE-3892
> URL: https://issues.apache.org/jira/browse/IGNITE-3892
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> Here is the problematic code:
> {code}
> if (desc.registered())
> out.unsafeWriteInt(desc.typeId());
> else {
> out.unsafeWriteInt(GridBinaryMarshaller.UNREGISTERED_TYPE_ID);
> doWriteString(val.getClass().getName());
> }
> {code}
> If class is not registered, {{val.getClass().getName()}} is written. But
> {{val}} is already a {{Class}} instance, so it should be {{val.getName()}}.
> Need to create a test and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3892) BinaryWriterExImpl.doWriteClass is incorrect
[
https://issues.apache.org/jira/browse/IGNITE-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko reassigned IGNITE-3892:
---
Assignee: Valentin Kulichenko
> BinaryWriterExImpl.doWriteClass is incorrect
>
>
> Key: IGNITE-3892
> URL: https://issues.apache.org/jira/browse/IGNITE-3892
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 1.8
>
>
> Here is the problematic code:
> {code}
> if (desc.registered())
> out.unsafeWriteInt(desc.typeId());
> else {
> out.unsafeWriteInt(GridBinaryMarshaller.UNREGISTERED_TYPE_ID);
> doWriteString(val.getClass().getName());
> }
> {code}
> If class is not registered, {{val.getClass().getName()}} is written. But
> {{val}} is already a {{Class}} instance, so it should be {{val.getName()}}.
> Need to create a test and fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3952) IgniteSpringBean.reentrantLock() method incorrectly flips create and fair flags when calling kernel delegate.
[
https://issues.apache.org/jira/browse/IGNITE-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Kaganovich resolved IGNITE-3952.
---
Resolution: Duplicate
duplicate submission - closing
> IgniteSpringBean.reentrantLock() method incorrectly flips create and fair
> flags when calling kernel delegate.
> -
>
> Key: IGNITE-3952
> URL: https://issues.apache.org/jira/browse/IGNITE-3952
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 1.7
>Reporter: Edward Kaganovich
> Labels: easyfix
>
> {code:title=IgniteSpringBean.java|borderStyle=solid}{code}
> @Nullable @Override public IgniteLock reentrantLock(String name,
> boolean failoverSafe,{color:green}boolean fair, boolean create
> {color}) {
>checkIgnite();
>return g.reentrantLock(name, failoverSafe, {color:red}create,
> fair{color});
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3952) IgniteSpringBean.reentrantLock() method incorrectly flips create and fair flags when calling kernel delegate.
Edward Kaganovich created IGNITE-3952:
-
Summary: IgniteSpringBean.reentrantLock() method incorrectly flips
create and fair flags when calling kernel delegate.
Key: IGNITE-3952
URL: https://issues.apache.org/jira/browse/IGNITE-3952
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 1.7
Reporter: Edward Kaganovich
{code:title=IgniteSpringBean.java|borderStyle=solid}{code}
@Nullable @Override public IgniteLock reentrantLock(String name,
boolean failoverSafe,{color:green}boolean fair, boolean create {color})
{
checkIgnite();
return g.reentrantLock(name, failoverSafe, {color:red}create,
fair{color});
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3951) IgniteSpringBean.reentrantLock() method incorrectly flips create and fair flags when calling kernel delegate.
Edward Kaganovich created IGNITE-3951:
-
Summary: IgniteSpringBean.reentrantLock() method incorrectly flips
create and fair flags when calling kernel delegate.
Key: IGNITE-3951
URL: https://issues.apache.org/jira/browse/IGNITE-3951
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 1.7
Reporter: Edward Kaganovich
{code:title=IgniteSpringBean.java|borderStyle=solid}{code}
@Nullable @Override public IgniteLock reentrantLock(String name,
boolean failoverSafe,{color:green}boolean fair, boolean create {color})
{
checkIgnite();
return g.reentrantLock(name, failoverSafe, {color:red}create,
fair{color});
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3635) StackOeverflowError in BinaryObject.toString()
[
https://issues.apache.org/jira/browse/IGNITE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko resolved IGNITE-3635.
-
> StackOeverflowError in BinaryObject.toString()
> --
>
> Key: IGNITE-3635
> URL: https://issues.apache.org/jira/browse/IGNITE-3635
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
> Attachments: Test.java
>
>
> If the object field is a collection or map and one the elements in the
> collection is that object (circular reference), stack overflow happens in
> {{toString}} method. This happens because handles which are tracked when
> {{toString}} is called, are lost when {{Collection.toString()}} is called. We
> should add special handling for collections and maps and print the out
> manually, without delegating to their {{toString()}} method.
> Test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3635) StackOeverflowError in BinaryObject.toString()
[
https://issues.apache.org/jira/browse/IGNITE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko closed IGNITE-3635.
---
> StackOeverflowError in BinaryObject.toString()
> --
>
> Key: IGNITE-3635
> URL: https://issues.apache.org/jira/browse/IGNITE-3635
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
> Attachments: Test.java
>
>
> If the object field is a collection or map and one the elements in the
> collection is that object (circular reference), stack overflow happens in
> {{toString}} method. This happens because handles which are tracked when
> {{toString}} is called, are lost when {{Collection.toString()}} is called. We
> should add special handling for collections and maps and print the out
> manually, without delegating to their {{toString()}} method.
> Test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3635) StackOeverflowError in BinaryObject.toString()
[
https://issues.apache.org/jira/browse/IGNITE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511246#comment-15511246
]
Valentin Kulichenko commented on IGNITE-3635:
-
Fix for {{IgniteUuid}} looks good to me. In case other similar cases exist,
let's address them separately.
> StackOeverflowError in BinaryObject.toString()
> --
>
> Key: IGNITE-3635
> URL: https://issues.apache.org/jira/browse/IGNITE-3635
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
> Attachments: Test.java
>
>
> If the object field is a collection or map and one the elements in the
> collection is that object (circular reference), stack overflow happens in
> {{toString}} method. This happens because handles which are tracked when
> {{toString}} is called, are lost when {{Collection.toString()}} is called. We
> should add special handling for collections and maps and print the out
> manually, without delegating to their {{toString()}} method.
> Test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3943) Hadoop: change scripts.
[
https://issues.apache.org/jira/browse/IGNITE-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511020#comment-15511020
]
Ivan Veselovsky commented on IGNITE-3943:
-
https://github.com/apache/ignite/pull/1098 .
2 items remain:
1) looks like need a U.isTest() method to provide special handling for
unit-tests somewhere.
2) Windows script (*.bat) should be checked.
> Hadoop: change scripts.
> ---
>
> Key: IGNITE-3943
> URL: https://issues.apache.org/jira/browse/IGNITE-3943
> Project: Ignite
> Issue Type: Sub-task
> Components: hadoop
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Ivan Veselovsky
> Fix For: 1.8
>
>
> 1) Remove and do not use {{HadoopClasspathMain}}.
> 2) Do not include {{hadoop-impl}} module into node class path.
> 3) {{HadoopClasspathUtils.classpathForClassLoader}} must include
> {{hadoop-impl}} in class path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3699) CreatedExpiryPolicy doesn't work if entry is loaded from store
[
https://issues.apache.org/jira/browse/IGNITE-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510991#comment-15510991
]
Hagmonk commented on IGNITE-3699:
-
I came here and created a JIRA account just to say that this patch applies
cleanly, and resolves the issue for me. It was going to be a serious problem if
my CacheStore backed cache could not be managed with an expiry policy! I tested
the patch using a CreatedExpiryPolicy and ModifiedExpiryPolicy. I applied the
patch against bcbe8cc4492449957ff983976f8f16e090c0b239.
> CreatedExpiryPolicy doesn't work if entry is loaded from store
> --
>
> Key: IGNITE-3699
> URL: https://issues.apache.org/jira/browse/IGNITE-3699
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
> Attachments: LoadWithExpiryTest.java
>
>
> According to JCache spec, {{ExpiryPolicy.getExpiryForCreation()}} must be
> triggered on {{get()}} operation if the entry is loaded from the store.
> Currently this is not happening.
> Test reproducing the issue is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3876) ODBC: Check all output parameters for nulls before assignment.
[ https://issues.apache.org/jira/browse/IGNITE-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510633#comment-15510633 ] ASF GitHub Bot commented on IGNITE-3876: GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1099 IGNITE-3876: Added null-pointer checks and tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3876 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1099.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 #1099 commit aecdbc0c87095acc9947e7826e33f55a0b15fe07 Author: isapego Date: 2016-09-20T17:42:11Z IGNITE-3876: Added robustness tests. commit e3a85ab59a60a93682ba87d16211d7a5fe1e38d7 Author: isapego Date: 2016-09-21T17:36:00Z IGNITE-3876: More tests and fixes. > ODBC: Check all output parameters for nulls before assignment. > --- > > Key: IGNITE-3876 > URL: https://issues.apache.org/jira/browse/IGNITE-3876 > Project: Ignite > Issue Type: Task > Components: odbc >Affects Versions: 1.7 >Reporter: Igor Sapego >Assignee: Igor Sapego > Labels: odbc > Fix For: 1.8 > > > Currently, we suppose that all the output pointer parameters are not null and > point to the valid data. Practice shows that a lot of users call ODBC > functions with NULL parameters if they don't need some of the output values. > Review the API and add all necessary null-checks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3210) Make modules\web-console\DEVNOTES.txt a bit clear
[ https://issues.apache.org/jira/browse/IGNITE-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reassigned IGNITE-3210: -- Assignee: Alexey Kuznetsov (was: Vasilisa Sidorova) Alexey, please, clarify should I build src before make this instruction. If yes, which parameters should I use during building (I couldn't find folder $IGNITE_HOME/modules/web-console/src/main/js). And if YES should it be mentioned in the DEVNOTES? > Make modules\web-console\DEVNOTES.txt a bit clear > - > > Key: IGNITE-3210 > URL: https://issues.apache.org/jira/browse/IGNITE-3210 > Project: Ignite > Issue Type: Improvement > Components: UI >Affects Versions: 1.6 >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Trivial > > We need to add an explanation that user should wait the end(result) of > current step before start next one. > And will be useful to describe how the result of each step looks like. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3950) Deadlock when exchange happens with pending explicit lock
Ilya Lantukh created IGNITE-3950:
Summary: Deadlock when exchange happens with pending explicit lock
Key: IGNITE-3950
URL: https://issues.apache.org/jira/browse/IGNITE-3950
Project: Ignite
Issue Type: Bug
Reporter: Ilya Lantukh
Reproduced by IgniteCacheMultiLockSelfTest#testExplicitLockManyKeysWithClient
(hangs with ~10% probability).
Exchange worker waits for lock to be released:
{noformat}
Thread [name="exchange-worker-#155%dht.IgniteCacheMultiTxLockSelfTest3%",
id=195, state=TIMED_WAITING, blockCnt=0, waitCnt=44]
Lock
[object=o.a.i.i.processors.cache.GridCacheMvccManager$FinishLockFuture@2638011,
ownerName=null, ownerId=-1]
at sun.misc.Unsafe.park(Native Method)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
at
o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:187)
at o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:137)
at
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.waitPartitionRelease(GridDhtPartitionsExchangeFuture.java:835)
at
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:763)
at
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:516)
at
o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1464)
at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{noformat}
while thread that holds lock cannot finish cache operation:
{noformat}
"Thread-9@3645" prio=5 tid=0x11a nid=NA waiting
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Unsafe.java:-1)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:117)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$45.inOp(GridCacheAdapter.java:2849)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$SyncInOp.op(GridCacheAdapter.java:5303)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4351)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAll(GridCacheAdapter.java:2847)
at
org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.putAll(GridCacheProxyImpl.java:838)
at
org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheMultiTxLockSelfTest$1.run(IgniteCacheMultiTxLockSelfTest.java:218)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3950) Deadlock when exchange starts with pending explicit lock
[
https://issues.apache.org/jira/browse/IGNITE-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Lantukh updated IGNITE-3950:
-
Summary: Deadlock when exchange starts with pending explicit lock (was:
Deadlock when exchange happens with pending explicit lock)
> Deadlock when exchange starts with pending explicit lock
>
>
> Key: IGNITE-3950
> URL: https://issues.apache.org/jira/browse/IGNITE-3950
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>
> Reproduced by IgniteCacheMultiLockSelfTest#testExplicitLockManyKeysWithClient
> (hangs with ~10% probability).
> Exchange worker waits for lock to be released:
> {noformat}
> Thread [name="exchange-worker-#155%dht.IgniteCacheMultiTxLockSelfTest3%",
> id=195, state=TIMED_WAITING, blockCnt=0, waitCnt=44]
> Lock
> [object=o.a.i.i.processors.cache.GridCacheMvccManager$FinishLockFuture@2638011,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:187)
> at
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:137)
> at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.waitPartitionRelease(GridDhtPartitionsExchangeFuture.java:835)
> at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:763)
> at
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:516)
> at
> o.a.i.i.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1464)
> at o.a.i.i.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> while thread that holds lock cannot finish cache operation:
> {noformat}
> "Thread-9@3645" prio=5 tid=0x11a nid=NA waiting
> java.lang.Thread.State: WAITING
> at sun.misc.Unsafe.park(Unsafe.java:-1)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:117)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$45.inOp(GridCacheAdapter.java:2849)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$SyncInOp.op(GridCacheAdapter.java:5303)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.syncOp(GridCacheAdapter.java:4351)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAll(GridCacheAdapter.java:2847)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.putAll(GridCacheProxyImpl.java:838)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheMultiTxLockSelfTest$1.run(IgniteCacheMultiTxLockSelfTest.java:218)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3949) Hadoop: change class loading strategy: exclude only classes with direct Hadoop dependencies.
[ https://issues.apache.org/jira/browse/IGNITE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510168#comment-15510168 ] Vladimir Ozerov commented on IGNITE-3949: - PR #1097. > Hadoop: change class loading strategy: exclude only classes with direct > Hadoop dependencies. > > > Key: IGNITE-3949 > URL: https://issues.apache.org/jira/browse/IGNITE-3949 > Project: Ignite > Issue Type: Sub-task > Components: hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2698) CacheKeyConfiguration is used only with BinaryMarshaller
[ https://issues.apache.org/jira/browse/IGNITE-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509786#comment-15509786 ] Andrey Martianov commented on IGNITE-2698: -- I made following changes: 1. Added processing of CacheKeyConfiguration when Jdk/Optimized marshallers are used. 2. Added check at node startup (if Jdk/Optimized marshallers are used) that local cache key configurations are in accordance with remote cache key configurations. 3. Fixed bug: BinaryMarshaller doesn't use CacheKeyConfiguration for classes those aren't explicitly defined in BinaryConfiguration (using BinaryTypeConfiguration). > CacheKeyConfiguration is used only with BinaryMarshaller > > > Key: IGNITE-2698 > URL: https://issues.apache.org/jira/browse/IGNITE-2698 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Andrey Martianov > Fix For: 1.8 > > > Now if CacheKeyConfiguration is specified it is used only with > BinaryMarshaller. Need to take it into account with others marshallers as > well or update documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2698) CacheKeyConfiguration is used only with BinaryMarshaller
[ https://issues.apache.org/jira/browse/IGNITE-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509736#comment-15509736 ] ASF GitHub Bot commented on IGNITE-2698: GitHub user amartianov opened a pull request: https://github.com/apache/ignite/pull/1096 IGNITE-2698: Using CacheKeyConfiguration with Jdk/Optimized marshallers + tests on CacheKeyConfigurations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2698 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1096.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 #1096 commit 2d12b6b301266133634583c7fb313d6df3b5fb23 Author: Andrey Martianov Date: 2016-09-21T12:08:46Z IGNITE-2698: Using CacheKeyConfiguration with Jdk/Optimized marshallers > CacheKeyConfiguration is used only with BinaryMarshaller > > > Key: IGNITE-2698 > URL: https://issues.apache.org/jira/browse/IGNITE-2698 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Semen Boikov >Assignee: Andrey Martianov > Fix For: 1.8 > > > Now if CacheKeyConfiguration is specified it is used only with > BinaryMarshaller. Need to take it into account with others marshallers as > well or update documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1578) Hang on GridShmemCommunicationClient creation in failover tests
[
https://issues.apache.org/jira/browse/IGNITE-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Belyak reassigned IGNITE-1578:
Assignee: Alexander Belyak (was: Yakov Zhdanov)
> Hang on GridShmemCommunicationClient creation in failover tests
> ---
>
> Key: IGNITE-1578
> URL: https://issues.apache.org/jira/browse/IGNITE-1578
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Semen Boikov
>Assignee: Alexander Belyak
> Attachments: Ignite_Tests_Ignite_Cache_Failover_3374.log.zip
>
>
> Observed two hangs of failover suite on TC in GridShmemCommunicationClient
> constructor (both hangs on agent ip_192.168.1.116):
> {noformat}
> [15:29:19] : [org.apache.ignite:ignite-core] Thread
> [name="ignite-#76282%sys-distributed.IgniteCacheTxNearDisabledFairAffinityPutGetRestartTest2%",
> id=107674, state=RUNNABLE, blockCnt=0, waitCnt=289]
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.net.SocketInputStream.socketRead0(Native Method)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.net.SocketInputStream.read(SocketInputStream.java:150)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.net.SocketInputStream.read(SocketInputStream.java:121)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2308)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2321)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2792)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:799)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> java.io.ObjectInputStream.(ObjectInputStream.java:299)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.util.ipc.shmem.IpcSharedMemoryClientEndpoint.(IpcSharedMemoryClientEndpoint.java:134)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.util.nio.GridShmemCommunicationClient.(GridShmemCommunicationClient.java:72)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.spi.communication.tcp.TcpCommunicationSpi.createShmemClient(TcpCommunicationSpi.java:2101)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2057)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:1978)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1914)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1880)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.managers.communication.GridIoManager.send(GridIoManager.java:1066)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.managers.communication.GridIoManager.send(GridIoManager.java:1214)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:652)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.distributed.dht.GridDhtTxFinishFuture.finish(GridDhtTxFinishFuture.java:405)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.distributed.dht.GridDhtTxFinishFuture.finish(GridDhtTxFinishFuture.java:263)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.distributed.dht.GridDhtTxLocal.rollbackAsync(GridDhtTxLocal.java:596)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:708)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:598)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:569)
> [15:29:19] : [org.apache.ignite:ignite-core] at
> o.a.i.i.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:126)
> [15:29:19] :
[jira] [Assigned] (IGNITE-3686) Web Console: Click on error feedback reset value in input.
[ https://issues.apache.org/jira/browse/IGNITE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-3686: Assignee: Dmitriy Shabalin > Web Console: Click on error feedback reset value in input. > -- > > Key: IGNITE-3686 > URL: https://issues.apache.org/jira/browse/IGNITE-3686 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.6 >Reporter: Andrey Novikov >Assignee: Dmitriy Shabalin >Priority: Minor > Fix For: 1.8 > > > Step to reproduce: > 1) Create a new cluster > 2) Open Node Filter section > 3) Choose 'Specified Nodes' option > 4) Enter invalid value in Node IDs field. > 5) Click on error icon. > Value will be reset and editor will be hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3949) Hadoop: change class loading strategy: exclude only classes with direct Hadoop dependencies.
Vladimir Ozerov created IGNITE-3949: --- Summary: Hadoop: change class loading strategy: exclude only classes with direct Hadoop dependencies. Key: IGNITE-3949 URL: https://issues.apache.org/jira/browse/IGNITE-3949 Project: Ignite Issue Type: Sub-task Components: hadoop Affects Versions: 1.7 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3948) TTL manager continues to track evicted entries
Andrey Gura created IGNITE-3948: --- Summary: TTL manager continues to track evicted entries Key: IGNITE-3948 URL: https://issues.apache.org/jira/browse/IGNITE-3948 Project: Ignite Issue Type: Bug Affects Versions: 1.7 Reporter: Andrey Gura Cache uses only heap memory and has eviction and expiry policies. During loading data into cache TTL manager consumes heap memory even if entries were evicted because it still track this entries. It's ok in case of offheap memory or/and swap are enabled but doesn't make sense in case of using only heap memory. See also http://stackoverflow.com/questions/39447690/apache-ignite-cache-eviction-still-in-memory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1199) Spark integration: problem when start spark-shell with --jars
[
https://issues.apache.org/jira/browse/IGNITE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov closed IGNITE-1199.
Fix confirmed
> Spark integration: problem when start spark-shell with --jars
> --
>
> Key: IGNITE-1199
> URL: https://issues.apache.org/jira/browse/IGNITE-1199
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
> Environment: Cent OS
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1. Start spark master, worker and ignite node with default config
> 2. Start spark-shell:
> {noformat}
> $ ./spark-shell --jars
> /home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-spark/ignite-spark-1.3.2.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/cache-api-1.0.0.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-log4j/ignite-log4j-1.3.2.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-log4j/log4j-1.2.17.jar
> --master spark://fosters-218:7077
> log4j:WARN No appenders could be found for logger
> (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Using Spark's default log4j profile:
> org/apache/spark/log4j-defaults.properties
> 15/07/30 02:57:13 INFO SecurityManager: Changing view acls to: gridgain
> 15/07/30 02:57:13 INFO SecurityManager: Changing modify acls to: gridgain
> 15/07/30 02:57:13 INFO SecurityManager: SecurityManager: authentication
> disabled; ui acls disabled; users with view permissions: Set(gridgain); users
> with modify permissions: Set(gridgain)
> 15/07/30 02:57:13 INFO HttpServer: Starting HTTP Server
> 15/07/30 02:57:13 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:13 INFO AbstractConnector: Started
> SocketConnector@0.0.0.0:51608
> 15/07/30 02:57:13 INFO Utils: Successfully started service 'HTTP class
> server' on port 51608.
> Welcome to
> __
> / __/__ ___ _/ /__
> _\ \/ _ \/ _ `/ __/ '_/
>/___/ .__/\_,_/_/ /_/\_\ version 1.3.1
> /_/
> Using Scala version 2.10.4 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_75)
> Type in expressions to have them evaluated.
> Type :help for more information.
> 15/07/30 02:57:16 INFO SparkContext: Running Spark version 1.3.1
> 15/07/30 02:57:16 INFO SecurityManager: Changing view acls to: gridgain
> 15/07/30 02:57:16 INFO SecurityManager: Changing modify acls to: gridgain
> 15/07/30 02:57:16 INFO SecurityManager: SecurityManager: authentication
> disabled; ui acls disabled; users with view permissions: Set(gridgain); users
> with modify permissions: Set(gridgain)
> 15/07/30 02:57:16 INFO Slf4jLogger: Slf4jLogger started
> 15/07/30 02:57:16 INFO Remoting: Starting remoting
> 15/07/30 02:57:16 INFO Remoting: Remoting started; listening on addresses
> :[akka.tcp://sparkDriver@fosters-221:41342]
> 15/07/30 02:57:16 INFO Utils: Successfully started service 'sparkDriver' on
> port 41342.
> 15/07/30 02:57:16 INFO SparkEnv: Registering MapOutputTracker
> 15/07/30 02:57:16 INFO SparkEnv: Registering BlockManagerMaster
> 15/07/30 02:57:16 INFO DiskBlockManager: Created local directory at
> /tmp/spark-2630fb35-12f4-4e70-920f-30124a4b2657/blockmgr-5a7d7b6f-c296-4d16-82e3-14e020895ed8
> 15/07/30 02:57:16 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
> 15/07/30 02:57:16 INFO HttpFileServer: HTTP File server directory is
> /tmp/spark-6721e343-162b-4d45-bc55-eaadf103719d/httpd-0dc803d3-4bc4-4d23-8983-66c298f88c7d
> 15/07/30 02:57:16 INFO HttpServer: Starting HTTP Server
> 15/07/30 02:57:16 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:16 INFO AbstractConnector: Started
> SocketConnector@0.0.0.0:41602
> 15/07/30 02:57:16 INFO Utils: Successfully started service 'HTTP file server'
> on port 41602.
> 15/07/30 02:57:16 INFO SparkEnv: Registering OutputCommitCoordinator
> 15/07/30 02:57:17 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:17 INFO AbstractConnector: Started
> SelectChannelConnector@0.0.0.0:4040
> 15/07/30 02:57:17 INFO Utils: Successfully started service 'SparkUI' on port
> 4040.
> 15/07/30 02:57:17 INFO SparkUI: Started SparkUI at http://fosters-221:4040
> 15/07/30 02:57:17 INFO SparkContext: Added JAR
> file:/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-spark/ignite-spark-1.3.2.jar
> at http://10.20.0.221:41602/jars/ignite-spark-1.3.2.jar with timestamp
> 1438250237070
> 15/07/30 02:57:17 INFO SparkContext: Added JAR
> file:/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/cache-api-1.0.0.jar
> a
[jira] [Resolved] (IGNITE-1199) Spark integration: problem when start spark-shell with --jars
[
https://issues.apache.org/jira/browse/IGNITE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Suntsov resolved IGNITE-1199.
--
Resolution: Fixed
> Spark integration: problem when start spark-shell with --jars
> --
>
> Key: IGNITE-1199
> URL: https://issues.apache.org/jira/browse/IGNITE-1199
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
> Environment: Cent OS
> jdk 1.7
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
>
> Steps to reproduce:
> 1. Start spark master, worker and ignite node with default config
> 2. Start spark-shell:
> {noformat}
> $ ./spark-shell --jars
> /home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-spark/ignite-spark-1.3.2.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/cache-api-1.0.0.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-log4j/ignite-log4j-1.3.2.jar,/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-log4j/log4j-1.2.17.jar
> --master spark://fosters-218:7077
> log4j:WARN No appenders could be found for logger
> (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Using Spark's default log4j profile:
> org/apache/spark/log4j-defaults.properties
> 15/07/30 02:57:13 INFO SecurityManager: Changing view acls to: gridgain
> 15/07/30 02:57:13 INFO SecurityManager: Changing modify acls to: gridgain
> 15/07/30 02:57:13 INFO SecurityManager: SecurityManager: authentication
> disabled; ui acls disabled; users with view permissions: Set(gridgain); users
> with modify permissions: Set(gridgain)
> 15/07/30 02:57:13 INFO HttpServer: Starting HTTP Server
> 15/07/30 02:57:13 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:13 INFO AbstractConnector: Started
> SocketConnector@0.0.0.0:51608
> 15/07/30 02:57:13 INFO Utils: Successfully started service 'HTTP class
> server' on port 51608.
> Welcome to
> __
> / __/__ ___ _/ /__
> _\ \/ _ \/ _ `/ __/ '_/
>/___/ .__/\_,_/_/ /_/\_\ version 1.3.1
> /_/
> Using Scala version 2.10.4 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_75)
> Type in expressions to have them evaluated.
> Type :help for more information.
> 15/07/30 02:57:16 INFO SparkContext: Running Spark version 1.3.1
> 15/07/30 02:57:16 INFO SecurityManager: Changing view acls to: gridgain
> 15/07/30 02:57:16 INFO SecurityManager: Changing modify acls to: gridgain
> 15/07/30 02:57:16 INFO SecurityManager: SecurityManager: authentication
> disabled; ui acls disabled; users with view permissions: Set(gridgain); users
> with modify permissions: Set(gridgain)
> 15/07/30 02:57:16 INFO Slf4jLogger: Slf4jLogger started
> 15/07/30 02:57:16 INFO Remoting: Starting remoting
> 15/07/30 02:57:16 INFO Remoting: Remoting started; listening on addresses
> :[akka.tcp://sparkDriver@fosters-221:41342]
> 15/07/30 02:57:16 INFO Utils: Successfully started service 'sparkDriver' on
> port 41342.
> 15/07/30 02:57:16 INFO SparkEnv: Registering MapOutputTracker
> 15/07/30 02:57:16 INFO SparkEnv: Registering BlockManagerMaster
> 15/07/30 02:57:16 INFO DiskBlockManager: Created local directory at
> /tmp/spark-2630fb35-12f4-4e70-920f-30124a4b2657/blockmgr-5a7d7b6f-c296-4d16-82e3-14e020895ed8
> 15/07/30 02:57:16 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
> 15/07/30 02:57:16 INFO HttpFileServer: HTTP File server directory is
> /tmp/spark-6721e343-162b-4d45-bc55-eaadf103719d/httpd-0dc803d3-4bc4-4d23-8983-66c298f88c7d
> 15/07/30 02:57:16 INFO HttpServer: Starting HTTP Server
> 15/07/30 02:57:16 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:16 INFO AbstractConnector: Started
> SocketConnector@0.0.0.0:41602
> 15/07/30 02:57:16 INFO Utils: Successfully started service 'HTTP file server'
> on port 41602.
> 15/07/30 02:57:16 INFO SparkEnv: Registering OutputCommitCoordinator
> 15/07/30 02:57:17 INFO Server: jetty-8.y.z-SNAPSHOT
> 15/07/30 02:57:17 INFO AbstractConnector: Started
> SelectChannelConnector@0.0.0.0:4040
> 15/07/30 02:57:17 INFO Utils: Successfully started service 'SparkUI' on port
> 4040.
> 15/07/30 02:57:17 INFO SparkUI: Started SparkUI at http://fosters-221:4040
> 15/07/30 02:57:17 INFO SparkContext: Added JAR
> file:/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/optional/ignite-spark/ignite-spark-1.3.2.jar
> at http://10.20.0.221:41602/jars/ignite-spark-1.3.2.jar with timestamp
> 1438250237070
> 15/07/30 02:57:17 INFO SparkContext: Added JAR
> file:/home/gridgain/isuntsov/gridgain-community-fabric-1.3.2/libs/cache-api-1.0
[jira] [Commented] (IGNITE-3635) StackOeverflowError in BinaryObject.toString()
[
https://issues.apache.org/jira/browse/IGNITE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509387#comment-15509387
]
Vladimir Ozerov commented on IGNITE-3635:
-
Reopened as another stack overflow was found there when {{IgniteUuid}} which is
{{Iterable}} is in the object.
> StackOeverflowError in BinaryObject.toString()
> --
>
> Key: IGNITE-3635
> URL: https://issues.apache.org/jira/browse/IGNITE-3635
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 1.8
>
> Attachments: Test.java
>
>
> If the object field is a collection or map and one the elements in the
> collection is that object (circular reference), stack overflow happens in
> {{toString}} method. This happens because handles which are tracked when
> {{toString}} is called, are lost when {{Collection.toString()}} is called. We
> should add special handling for collections and maps and print the out
> manually, without delegating to their {{toString()}} method.
> Test attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3438) Caches: Add more info and examples to "Escape table and filed names" tooltip
[ https://issues.apache.org/jira/browse/IGNITE-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-3438. --- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Added example > Caches: Add more info and examples to "Escape table and filed names" tooltip > > > Key: IGNITE-3438 > URL: https://issues.apache.org/jira/browse/IGNITE-3438 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3938) JDBC POJO store should support escaping for database schema, table and field names
[
https://issues.apache.org/jira/browse/IGNITE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-3938:
-
Summary: JDBC POJO store should support escaping for database schema, table
and field names (was: JDBC POJO should support escaping for database schema,
table and field names)
> JDBC POJO store should support escaping for database schema, table and field
> names
> --
>
> Key: IGNITE-3938
> URL: https://issues.apache.org/jira/browse/IGNITE-3938
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 1.8
>
>
> Sometimes database names could be very *strange* and this could be handled
> only via escaping. We need to support this.
> Adding {code}String JdbcDialect.escape(name){code} method looks like a good
> solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3936) JDBC POJO store may load data twice in some conditions
[
https://issues.apache.org/jira/browse/IGNITE-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov closed IGNITE-3936.
> JDBC POJO store may load data twice in some conditions
> --
>
> Key: IGNITE-3936
> URL: https://issues.apache.org/jira/browse/IGNITE-3936
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Critical
> Fix For: 1.8
>
>
> If POJO class present and Binary marshaller configured then
> {code}cache.loadCache(null){code} may load same data twice.
> Also in case of empty table in database POJO store also tries to load data
> twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-3437) Caches: Start size - rename to Onheap start size and add more info into tooltip
[ https://issues.apache.org/jira/browse/IGNITE-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko resolved IGNITE-3437. --- Resolution: Fixed Assignee: Pavel Konstantinov (was: Alexey Kuznetsov) Changed tooitip to more clear. > Caches: Start size - rename to Onheap start size and add more info into > tooltip > --- > > Key: IGNITE-3437 > URL: https://issues.apache.org/jira/browse/IGNITE-3437 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov > Fix For: 1.8 > > > And moe under "Mode" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-3436) Caches: make SQL schema tooltip more informative, add example.
[ https://issues.apache.org/jira/browse/IGNITE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reopened IGNITE-3436: --- Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) Tooltip changed. > Caches: make SQL schema tooltip more informative, add example. > -- > > Key: IGNITE-3436 > URL: https://issues.apache.org/jira/browse/IGNITE-3436 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov > Fix For: 1.8 > > > For now it is not clear why we need this field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3436) Caches: make SQL schema tooltip more informative, add example.
[
https://issues.apache.org/jira/browse/IGNITE-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509063#comment-15509063
]
Pavel Konstantinov commented on IGNITE-3436:
I suggest the following tooltip text:
{code}
Using of schema name makes ignite SQL queries like a native ANSI SQL.
Query example without schema name:
select from "cache1".Type1
inner join "cache2".Type2 ...
The same query using schema name:
select from cache1.Type1
inner join cache2.Type2 ...
{code}
> Caches: make SQL schema tooltip more informative, add example.
> --
>
> Key: IGNITE-3436
> URL: https://issues.apache.org/jira/browse/IGNITE-3436
> Project: Ignite
> Issue Type: Sub-task
> Components: wizards
>Affects Versions: 1.6
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 1.8
>
>
> For now it is not clear why we need this field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
