Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

2015-09-25 Thread Sergi Vladykin 
+1

Sergi

2015-09-25 16:52 GMT+03:00 Alexey Kuznetsov :

> +1
>
> On Fri, Sep 25, 2015 at 8:48 PM, Anton Vinogradov  wrote:
>
> > +1
> >
> > On Fri, Sep 25, 2015 at 3:49 PM, Denis Magda 
> wrote:
> >
> > > +1
> > >
> > > -Original Message-
> > > From: "Yakov Zhdanov" 
> > > Sent: ‎9/‎25/‎2015 15:37
> > > To: "dev@ignite.apache.org" 
> > > Subject: [VOTE] Apache Ignite 1.4.0 Release (RC1)
> > >
> > > Dear Sirs!
> > >
> > > We have uploaded release candidate to
> > > https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/
> > >
> > > I am very glad to mention that this is the first Ignite release as top
> > > level project! Thanks everyone for help this to happen!
> > >
> > > Tag name is
> > > ignite-1.4.0-rc1
> > >
> > > 1.4.0 changes:
> > > * Added SSL support to communication and discovery.
> > > * Added support for log4j2.
> > > * Added versioned entry to cache API.
> > > * Added client node based JDBC driver implementation.
> > > * Fixed consistency issue for custom events processing within
> discovery.
> > > * Fixed race in cache swap/unswap logic.
> > > * Fixed IGNITE_HOME resolution with JBoss.
> > > * Fixed configuration file resolution on classpath.
> > > * Fixed MBean registration for caches.
> > > * Fixed near cache evictions with offheap.
> > > * Fixed SQL queries group index logic.
> > > * Fixed memory leak in partitioned transactional cache.
> > > * Fixed auto-retries for cache operations in recoverable cases.
> > > * Fixed affinity routing in compute grid.
> > > * Many stability and fault-tolerance fixes.
> > >
> > > DEVNOTES
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > >
> > > RELEASENOTES
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > >
> > > Please start voting.
> > >
> > > +1 - to accept Apache Ignite 1.4.0
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite 1.4.0 (explain why)
> > >
> > > This vote will go for 72 hours.
> > >
> > > --Yakov
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

2015-09-25 Thread Gianfranco Murador 
+1

2015-09-25 17:26 GMT+02:00 Sergi Vladykin :

> +1
>
> Sergi
>
> 2015-09-25 16:52 GMT+03:00 Alexey Kuznetsov :
>
> > +1
> >
> > On Fri, Sep 25, 2015 at 8:48 PM, Anton Vinogradov  wrote:
> >
> > > +1
> > >
> > > On Fri, Sep 25, 2015 at 3:49 PM, Denis Magda 
> > wrote:
> > >
> > > > +1
> > > >
> > > > -Original Message-
> > > > From: "Yakov Zhdanov" 
> > > > Sent: ‎9/‎25/‎2015 15:37
> > > > To: "dev@ignite.apache.org" 
> > > > Subject: [VOTE] Apache Ignite 1.4.0 Release (RC1)
> > > >
> > > > Dear Sirs!
> > > >
> > > > We have uploaded release candidate to
> > > > https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/
> > > >
> > > > I am very glad to mention that this is the first Ignite release as
> top
> > > > level project! Thanks everyone for help this to happen!
> > > >
> > > > Tag name is
> > > > ignite-1.4.0-rc1
> > > >
> > > > 1.4.0 changes:
> > > > * Added SSL support to communication and discovery.
> > > > * Added support for log4j2.
> > > > * Added versioned entry to cache API.
> > > > * Added client node based JDBC driver implementation.
> > > > * Fixed consistency issue for custom events processing within
> > discovery.
> > > > * Fixed race in cache swap/unswap logic.
> > > > * Fixed IGNITE_HOME resolution with JBoss.
> > > > * Fixed configuration file resolution on classpath.
> > > > * Fixed MBean registration for caches.
> > > > * Fixed near cache evictions with offheap.
> > > > * Fixed SQL queries group index logic.
> > > > * Fixed memory leak in partitioned transactional cache.
> > > > * Fixed auto-retries for cache operations in recoverable cases.
> > > > * Fixed affinity routing in compute grid.
> > > > * Many stability and fault-tolerance fixes.
> > > >
> > > > DEVNOTES
> > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > > >
> > > > RELEASENOTES
> > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > > >
> > > > Please start voting.
> > > >
> > > > +1 - to accept Apache Ignite 1.4.0
> > > > 0 - don't care either way
> > > > -1 - DO NOT accept Apache Ignite 1.4.0 (explain why)
> > > >
> > > > This vote will go for 72 hours.
> > > >
> > > > --Yakov
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

2015-09-25 Thread Vladimir Ozerov 
+1

On Fri, Sep 25, 2015 at 6:38 PM, chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:

> +1
>
> On Fri, Sep 25, 2015 at 9:03 PM, Gianfranco Murador <
> murador.gianfra...@gmail.com> wrote:
>
> > +1
> >
> > 2015-09-25 17:26 GMT+02:00 Sergi Vladykin :
> >
> > > +1
> > >
> > > Sergi
> > >
> > > 2015-09-25 16:52 GMT+03:00 Alexey Kuznetsov :
> > >
> > > > +1
> > > >
> > > > On Fri, Sep 25, 2015 at 8:48 PM, Anton Vinogradov 
> > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Fri, Sep 25, 2015 at 3:49 PM, Denis Magda 
> > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > -Original Message-
> > > > > > From: "Yakov Zhdanov" 
> > > > > > Sent: ‎9/‎25/‎2015 15:37
> > > > > > To: "dev@ignite.apache.org" 
> > > > > > Subject: [VOTE] Apache Ignite 1.4.0 Release (RC1)
> > > > > >
> > > > > > Dear Sirs!
> > > > > >
> > > > > > We have uploaded release candidate to
> > > > > > https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/
> > > > > >
> > > > > > I am very glad to mention that this is the first Ignite release
> as
> > > top
> > > > > > level project! Thanks everyone for help this to happen!
> > > > > >
> > > > > > Tag name is
> > > > > > ignite-1.4.0-rc1
> > > > > >
> > > > > > 1.4.0 changes:
> > > > > > * Added SSL support to communication and discovery.
> > > > > > * Added support for log4j2.
> > > > > > * Added versioned entry to cache API.
> > > > > > * Added client node based JDBC driver implementation.
> > > > > > * Fixed consistency issue for custom events processing within
> > > > discovery.
> > > > > > * Fixed race in cache swap/unswap logic.
> > > > > > * Fixed IGNITE_HOME resolution with JBoss.
> > > > > > * Fixed configuration file resolution on classpath.
> > > > > > * Fixed MBean registration for caches.
> > > > > > * Fixed near cache evictions with offheap.
> > > > > > * Fixed SQL queries group index logic.
> > > > > > * Fixed memory leak in partitioned transactional cache.
> > > > > > * Fixed auto-retries for cache operations in recoverable cases.
> > > > > > * Fixed affinity routing in compute grid.
> > > > > > * Many stability and fault-tolerance fixes.
> > > > > >
> > > > > > DEVNOTES
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > > > > >
> > > > > > RELEASENOTES
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > > > > >
> > > > > > Please start voting.
> > > > > >
> > > > > > +1 - to accept Apache Ignite 1.4.0
> > > > > > 0 - don't care either way
> > > > > > -1 - DO NOT accept Apache Ignite 1.4.0 (explain why)
> > > > > >
> > > > > > This vote will go for 72 hours.
> > > > > >
> > > > > > --Yakov
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
>
>
>
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660
>

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

2015-09-25 Thread chandresh pancholi 
+1

On Fri, Sep 25, 2015 at 9:03 PM, Gianfranco Murador <
murador.gianfra...@gmail.com> wrote:

> +1
>
> 2015-09-25 17:26 GMT+02:00 Sergi Vladykin :
>
> > +1
> >
> > Sergi
> >
> > 2015-09-25 16:52 GMT+03:00 Alexey Kuznetsov :
> >
> > > +1
> > >
> > > On Fri, Sep 25, 2015 at 8:48 PM, Anton Vinogradov 
> wrote:
> > >
> > > > +1
> > > >
> > > > On Fri, Sep 25, 2015 at 3:49 PM, Denis Magda 
> > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > -Original Message-
> > > > > From: "Yakov Zhdanov" 
> > > > > Sent: ‎9/‎25/‎2015 15:37
> > > > > To: "dev@ignite.apache.org" 
> > > > > Subject: [VOTE] Apache Ignite 1.4.0 Release (RC1)
> > > > >
> > > > > Dear Sirs!
> > > > >
> > > > > We have uploaded release candidate to
> > > > > https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/
> > > > >
> > > > > I am very glad to mention that this is the first Ignite release as
> > top
> > > > > level project! Thanks everyone for help this to happen!
> > > > >
> > > > > Tag name is
> > > > > ignite-1.4.0-rc1
> > > > >
> > > > > 1.4.0 changes:
> > > > > * Added SSL support to communication and discovery.
> > > > > * Added support for log4j2.
> > > > > * Added versioned entry to cache API.
> > > > > * Added client node based JDBC driver implementation.
> > > > > * Fixed consistency issue for custom events processing within
> > > discovery.
> > > > > * Fixed race in cache swap/unswap logic.
> > > > > * Fixed IGNITE_HOME resolution with JBoss.
> > > > > * Fixed configuration file resolution on classpath.
> > > > > * Fixed MBean registration for caches.
> > > > > * Fixed near cache evictions with offheap.
> > > > > * Fixed SQL queries group index logic.
> > > > > * Fixed memory leak in partitioned transactional cache.
> > > > > * Fixed auto-retries for cache operations in recoverable cases.
> > > > > * Fixed affinity routing in compute grid.
> > > > > * Many stability and fault-tolerance fixes.
> > > > >
> > > > > DEVNOTES
> > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > > > >
> > > > > RELEASENOTES
> > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
> > > > >
> > > > > Please start voting.
> > > > >
> > > > > +1 - to accept Apache Ignite 1.4.0
> > > > > 0 - don't care either way
> > > > > -1 - DO NOT accept Apache Ignite 1.4.0 (explain why)
> > > > >
> > > > > This vote will go for 72 hours.
> > > > >
> > > > > --Yakov
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>



-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

[jira] [Created] (IGNITE-1549) Optimize portable object fields write in non-raw mode.

2015-09-25 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-1549:
---

 Summary: Optimize portable object fields write in non-raw mode.
 Key: IGNITE-1549
 URL: https://issues.apache.org/jira/browse/IGNITE-1549
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Priority: Blocker
 Fix For: ignite-1.5


Currently we write user fields as follows:
0 ,, 3 - field ID;
4 - field type;
5 ..8 - field len;
9 .. - the field itself.

It can be optimized as follows:
1) Field len usually can be inferred from type. E.g., for int it is 4.
2) Frequently used constants can be written as separate types. E.g. INT - 
normal int, INT_0 - zero, etc.
3) Last, but not least, values should be encoded using "variable bytes" (and 
possibly ZigZag) algorithm. This will give us 2 bytes economy for ints and 
longs on average (I assume here that longs are usually bigger than 4 bytes, 
e.g. timestamps).

*New types will be introduced:*
1) Booleans: BOOL_FALSE, BOOL_TRUE;
2) Bytes: BYTE_C0 => zero, BYTE_C1 => 1, BYTE_C1N => -1;
3) Shorts, chars: SHORT_C0, SHORT_C1, SHORT_C1N;
4) Ints: INT_C0, INT_C1, INT_C1N, INT_1 - int which fits into 1 byte, INT_1N - 
same for negative value, INT_2, INT_2N, INT_3, INT_3N, INT_3, INT_3N, INT_4, 
INT_4N.
5) Longs: same as ints, but have only 2, 4, 6 and 8 byte count discriminators 
to avoid excessive calculations.

It means that instead of 6 integer types previously, we will have 2 + 3 + 3 + 3 
+ 11 + 11 = 32 types.

To avoid excessive switches or (even worse) array/map lookups to understand 
what the type is, we can divide all types space (256) into two parts: optimized 
and non-optimized. Optimized space will have the MSB set to 1, and mentioned 
~30 optimized types (or some of them) are located there.

For floats and doubles we simply infer length. 

For primitive arrays we do not write field length and then arrya length, but 
only array length.

*Expected compaction*:
bool: 10 -> 5 bytes (50%);
byte: 10 -> 5-6 bytes (45%);
short, char: 11 -> 5-7 bytes, 7 on average (35%);
int: 13 -> 5-9 bytes, 7 on average (45%).
long: 17 -> 5-13 bytes, 11 on average (35%).
float: 13 -> 9 bytes (30%);
double: 17 -> 13 bytes (25%);

*Expected CPU overhead on writes:*
Bool, float, double: -
Byte, short, char: zero check, sign check;
Int, long: two (shift + OR)s to understand bytes count, if small - "zero" and 
"one" checks, if big - sign check,

*Expected CPU overhead on reads:*
One additional branch between optimzied and non-optimized spaces.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Optimizing portable protocol.

2015-09-25 Thread Vladimir Ozerov 
Igniters,

Thorough analysis of portable object format lead me to conclusion that
significant part of transferred data is either zeros, several constants
(e.g. 0, 1, -1, true, false) or some redundant information.

I created two tickets for this with high priority and I think we should at
least evaluate them before 1.5 is released.

1) Portable object header can be shrunk from 18 to 10-11 bytes in the most
common cases.
https://issues.apache.org/jira/browse/IGNITE-1548

2) Portable object primitive fields in non-raw mode (the most common case
for user object) can be decreased in size on ~30-50%:
bool:  10 -> 5bytes (50%)
byte:  10 -> 5-6  bytes (45%)
short: 11 -> 5-7  bytes (~45%)
int:   13 -> 5-9  bytes (~45%)
long:  17 -> 5-13 bytes (~35% on average)
https://issues.apache.org/jira/browse/IGNITE-1549

Vladimir.

[GitHub] ignite pull request: Ignite 530

2015-09-25 Thread sylentprayer 
GitHub user sylentprayer opened a pull request:

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

Ignite 530

Fixes for 
https://issues.apache.org/jira/browse/IGNITE-530?focusedCommentId=14904705=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14904705

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

$ git pull https://github.com/sylentprayer/ignite ignite-530

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

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


commit 8a4ef1419c2b8fd720be3a65b53f9a56a6eea524
Author: sylentprayer 
Date:   2015-09-19T17:41:49Z

IGNITE-530 development of Twitter data streamer based on Twitter Streaming 
API (public statuses).
This data streamer requires valid Twitter OAuth credentials, so tests are 
skipped by default (in this module's pom.xml).
Need to set these OAuth keys in test/resources/twitter.properties and 
enable tests.

Test covers only statuses filter API endpoint as firehose and site stream 
requires special permissions.

commit e427113a0a1eb31b3db23dcee9eb057b17d0fdf2
Author: sylentprayer 
Date:   2015-09-25T18:40:44Z

IGNITE-530 fixes for comment 
https://issues.apache.org/jira/browse/IGNITE-530?focusedCommentId=14904705=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14904705




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Semaphore issue

2015-09-25 Thread Vladisav Jelisavcic 
Hi everyone,

my name is VJ, i would like to implement IgniteSemaphore datastructure (
IGNITE-638).
My Jira ID is vladisav, can someone please assign it to me?

Thanks,
VJ

[jira] [Created] (IGNITE-1552) Table function doesn't work properly in SQL query

2015-09-25 Thread Valentin Kulichenko (JIRA) 
Valentin Kulichenko created IGNITE-1552:
---

 Summary: Table function doesn't work properly in SQL query
 Key: IGNITE-1552
 URL: https://issues.apache.org/jira/browse/IGNITE-1552
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Valentin Kulichenko
Assignee: Sergi Vladykin
Priority: Critical
 Fix For: ignite-1.5


IN operator replacement query described in [1] doesn't seem to work properly. 
Test reproducing the issue is attached.

[1]https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Fwd: SQL IN operator example

2015-09-25 Thread Valentin Kulichenko 
Sergi,

Can you please take a look at this issue? I create a ticket and attached
the test to it: https://issues.apache.org/jira/browse/IGNITE-1552

I already made some debugging and I think the reason is that TableFunction
is parsed as an ordinary Function, so it's columnList field is ignored. As
a result, column identifiers are removed from the map query and this causes
syntax error.

Thanks!

-Val

-- Forwarded message --
From: kevin 
Date: Fri, Sep 25, 2015 at 9:21 AM
Subject: SQL IN operator example
To: u...@ignite.apache.org


I'm trying the example with the IN operator here.
https://apacheignite.readme.io/docs/sql-queries#performance-and-usability-considerations

This is the code
Integer[] ids = {Integer.valueOf(0), Integer.valueOf(1)};
System.out.println(personCache.query(new SqlFieldsQuery("select p.firstName
from Person p join table(id bigint = ?) i on p.id =
i.id").setArgs(ids)).getAll());

I get this error though
org.apache.ignite.IgniteException: Syntax error in SQL statement "SELECT
P.FIRSTNAME __C0
FROM TABLE(?[*]1) I
 INNER JOIN PERSON_CACHE.PERSON P
WHERE P.ID = I.ID"; expected "identifier" [42001-175]
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:466)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:777)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:59)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:71)



--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SQL-IN-operator-example-tp1493.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

[jira] [Created] (IGNITE-1553) Optimize transaction prepare step when store is enabled

2015-09-25 Thread Alexey Goncharuk (JIRA) 
Alexey Goncharuk created IGNITE-1553:


 Summary: Optimize transaction prepare step when store is enabled
 Key: IGNITE-1553
 URL: https://issues.apache.org/jira/browse/IGNITE-1553
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: ignite-1.4
Reporter: Alexey Goncharuk


Currently entries are enlisted in a database transaction after grid transaction 
is in PREPARED state. We can do this in parallel in the following fashion 
(pseudo-code):

{code}
fut = tx.prepareAsync();

db.write(tx.writes());

fut.get();

try {
db.commit();

tx.commit();
}
catch (Exception e) {
tx.rollback();
}
{code}

If this approach is applied, we should be able to reduce latency for 
transactions when write-through is enabled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-1547) NPE if using HTTP REST

2015-09-25 Thread Pavel Konstantinov (JIRA) 
Pavel Konstantinov created IGNITE-1547:
--

 Summary: NPE if using HTTP REST
 Key: IGNITE-1547
 URL: https://issues.apache.org/jira/browse/IGNITE-1547
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: ignite-1.4
Reporter: Pavel Konstantinov
Assignee: Yakov Zhdanov
 Fix For: ignite-1.5


I'm tested Ignite Console SQL feature and got NPE on node start if web agent 
trying to get cache information at this moment
{code}
[13:25:56,761][SEVERE][qtp79785210-70][GridJettyRestProtocol] Failed to process 
HTTP request [action=/ignite, req=(GET 
/ignite?cmd=top=true=false)@1215478528 
org.eclipse.jetty.server.Request@
4872bb00]
class org.apache.ignite.IgniteCheckedException: null
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:150)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.createNodeBean(GridTopologyCommandHandler.java:208)
at 
org.apache.ignite.internal.processors.rest.handlers.top.GridTopologyCommandHandler.handleAsync(GridTopologyCommandHandler.java:107)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:226)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:79)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:133)
... 4 more
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: ignite-schema-import

2015-09-25 Thread Dmitriy Setrakyan 
Alexey,

I have enabled schema-import profile, but know the whole project shows as
RED in the Maven take in IDEA. All modules have problem with
"com.sun.tools:1.4.2" dependency.

Any idea?

D.

On Wed, Sep 16, 2015 at 11:22 PM, Alexey Kuznetsov 
wrote:

> Seems that you unchecked "schema-import" profile in Maven projects /
> Profile tree?
>
> On Thu, Sep 17, 2015 at 10:44 AM, Dmitriy Setrakyan  >
> wrote:
>
> > Igniters,
> >
> > Is there a reason every time I update from GIT I get the following popup
> in
> > IDEA:
> >
> > "This modules have been removed from Maven structure:
> > "ignite-schema-import"?
> >
> > D.
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: ignite-schema-import

2015-09-25 Thread Alexey Kuznetsov 
Dmitry,

1) Could you take a screenshot of Idea Maven tool window with expanded
"profiles" and share with us via dropbox or smth. similar (apache dev list
does not allow attachments)?

2) Try to do in Idea: Main menu -> Files -> Invalidate Caches / restart ->
Invalidate and restart and after Idea restarted and source code indexing
finished -> Click "reimport" on Maven toolbox.
This often helped to resolve issues like this.


On Fri, Sep 25, 2015 at 3:18 PM, Dmitriy Setrakyan 
wrote:

> Alexey,
>
> I have enabled schema-import profile, but know the whole project shows as
> RED in the Maven take in IDEA. All modules have problem with
> "com.sun.tools:1.4.2" dependency.
>
> Any idea?
>
> D.
>
> On Wed, Sep 16, 2015 at 11:22 PM, Alexey Kuznetsov <
> akuznet...@gridgain.com>
> wrote:
>
> > Seems that you unchecked "schema-import" profile in Maven projects /
> > Profile tree?
> >
> > On Thu, Sep 17, 2015 at 10:44 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > Igniters,
> > >
> > > Is there a reason every time I update from GIT I get the following
> popup
> > in
> > > IDEA:
> > >
> > > "This modules have been removed from Maven structure:
> > > "ignite-schema-import"?
> > >
> > > D.
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: ignite-schema-import

2015-09-25 Thread Anton Vinogradov 
Dmitriy,

Thats not a git issue, it's an IDEA warning. I have no such warning.
Seems you have broken *.iml files or you are swithing betwen branches where
some branches have schema-import module, but some not.

Better way to fix broken files is to remove everything and checkout
repository again. (Removing of .idea folder and all .iml files should give
save effect). Don't forget to close IDEA before removing.

On Fri, Sep 25, 2015 at 11:30 AM, Alexey Kuznetsov 
wrote:

> Dmitry,
>
> 1) Could you take a screenshot of Idea Maven tool window with expanded
> "profiles" and share with us via dropbox or smth. similar (apache dev list
> does not allow attachments)?
>
> 2) Try to do in Idea: Main menu -> Files -> Invalidate Caches / restart ->
> Invalidate and restart and after Idea restarted and source code indexing
> finished -> Click "reimport" on Maven toolbox.
> This often helped to resolve issues like this.
>
>
> On Fri, Sep 25, 2015 at 3:18 PM, Dmitriy Setrakyan 
> wrote:
>
> > Alexey,
> >
> > I have enabled schema-import profile, but know the whole project shows as
> > RED in the Maven take in IDEA. All modules have problem with
> > "com.sun.tools:1.4.2" dependency.
> >
> > Any idea?
> >
> > D.
> >
> > On Wed, Sep 16, 2015 at 11:22 PM, Alexey Kuznetsov <
> > akuznet...@gridgain.com>
> > wrote:
> >
> > > Seems that you unchecked "schema-import" profile in Maven projects /
> > > Profile tree?
> > >
> > > On Thu, Sep 17, 2015 at 10:44 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > Is there a reason every time I update from GIT I get the following
> > popup
> > > in
> > > > IDEA:
> > > >
> > > > "This modules have been removed from Maven structure:
> > > > "ignite-schema-import"?
> > > >
> > > > D.
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[VOTE] Apache Ignite 1.4.0 Release (RC1)

2015-09-25 Thread Yakov Zhdanov 
Dear Sirs!

We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/

I am very glad to mention that this is the first Ignite release as top
level project! Thanks everyone for help this to happen!

Tag name is
ignite-1.4.0-rc1

1.4.0 changes:
* Added SSL support to communication and discovery.
* Added support for log4j2.
* Added versioned entry to cache API.
* Added client node based JDBC driver implementation.
* Fixed consistency issue for custom events processing within discovery.
* Fixed race in cache swap/unswap logic.
* Fixed IGNITE_HOME resolution with JBoss.
* Fixed configuration file resolution on classpath.
* Fixed MBean registration for caches.
* Fixed near cache evictions with offheap.
* Fixed SQL queries group index logic.
* Fixed memory leak in partitioned transactional cache.
* Fixed auto-retries for cache operations in recoverable cases.
* Fixed affinity routing in compute grid.
* Many stability and fault-tolerance fixes.

DEVNOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1

RELEASENOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1

Please start voting.

+1 - to accept Apache Ignite 1.4.0
0 - don't care either way
-1 - DO NOT accept Apache Ignite 1.4.0 (explain why)

This vote will go for 72 hours.

--Yakov

More efficient writes of messages in direct mode.

2015-09-25 Thread Vladimir Ozerov 
Igniters,

Several observations on our "direct" message writes:

1) For some reason we write null arrays, maps and ints as "-1" integer,
while it can be encoded in a single byte. And our cache messages have
lots of containers, which are commonly null.

2) Some frequently used data types could benefit significantly if integers
are written in compacted form, while others could not. Several examples:

GridCacheVersion:
topVer - fits in 2 bytes instead of 4;
nodeOrderDrId -  1 instead of 4;
globalTime - 6 instead of 8;
order -  6 instead of 8.
Result: shrunk from 24 to 15 bytes with minimal overhead.

AffinityTopologyVersion:
topVer -  1-2 bytes instead of 8.
minorTopVer - 1 byte instead of 4;
Result: shrunked from 12 to 2-3 bytes in 99% cases.

IgniteUuid - takes 24 bytes, but can be shrunk only to 22 bytes => bad
candidate for optimziation.

I picked random test and set breakpoint into random cache message -
GridDhtTxPrepareRequest. It was 444 bytes long with a single int-int pair
as a payload. At least 90 bytes (~20%) could be saved easily with described
optimziations.

Looks like we should pay more attention to it.

Vladimir.

[jira] [Created] (IGNITE-1550) Optimize "direct" message serialization.

2015-09-25 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-1550:
---

 Summary: Optimize "direct" message serialization.
 Key: IGNITE-1550
 URL: https://issues.apache.org/jira/browse/IGNITE-1550
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: ignite-1.5


*Overview*
Ignite use "direct" serialization to speed up marshalling of internal classes 
avoiding byte array copying.
This mechanism can be improved significantly on class-by-class basis reducing 
message size by 10-30% in different cases.

*Implementation*
1) Definte the list of possible optimizations. At the very least it includes:
- Var-length integer encoding; 
- Special cases (constants, positive-only values, low amount of significant 
bits, etc.);
- Efficient writes of "nulls";
- Write groups of relates fields with boolean switch if they are either null or 
not-null at the same time.

2) Determine what to optimize. This can be done on class-by-class basis for 
each of ~180 messages. Better approach will be to enable tracking of written 
values inside DirectMessageWriter. Then we should run Ignite with differnet 
payloads and identify fields which are good candidates for optimization.

3) Implement each optimziation.

*Risks*
Backward compatibility will be broken. We must either inform users about it, or 
support ability to use old non-optimized protocol version somehow.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [NOTICE] TeamCity is down

2015-09-25 Thread Konstantin Boudnik 
On Wed, Sep 23, 2015 at 10:20PM, Yakov Zhdanov wrote:
> Cos, is it ok that none of the domain names mentioned in ticket responds?
> Even those with "dig" output.

Looks like our CI master is down as well ;( Will look at it, thanks!

> 
> Created ticket for Ignite -
> https://issues.apache.org/jira/browse/INFRA-10484
> 
> 
> --Yakov
> 
> 2015-09-22 21:01 GMT+03:00 Konstantin Boudnik :
> 
> > Something like this could be arranged with INFRA
> > https://issues.apache.org/jira/browse/INFRA-10092
> > so there's an official CNAME for the CI server.
> >
> > Cos
> >
> > On Tue, Sep 22, 2015 at 11:31AM, Raul Kripalani wrote:
> > > Hey guys,
> > >
> > > (Continuing "Maybe review my first commits" thread here).
> > >
> > > I updated the Wiki in several places to point to .153:
> > >
> > > - Frontpage
> > > - Git process
> > > - How to Contribute
> > >
> > > Are there any plans to create a hostname for TeamCity? Else we can
> > create a
> > > page at http://ignite.apache.org/teamcity that redirects to the right
> > place.
> > >
> > > Thanks,
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > > Messaging Engineer
> > > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> > > On Tue, Sep 22, 2015 at 6:05 AM, Denis Magda 
> > wrote:
> > >
> > > > Hi Raul,
> > > >
> > > > That server got down almost a month ago.
> > > > There is a secondary one - http://204.14.53.153/
> > > >
> > > > Are we going to recover .152 server? If we don't then we have to update
> > > > our wiki and refer to .153.
> > > >
> > > > --
> > > > Denis
> > > >
> > > >
> > > > On 9/22/2015 12:25 AM, Raúl Kripalani wrote:
> > > >
> > > >> I'm trying to access TeamCity via the URL in the Wiki (
> > > >> http://204.14.53.152/)
> > > >> but it seems to be down...
> > > >>
> > > >> http://downforeveryoneorjustme.com/http://204.14.53.152/
> > > >>
> > > >> Could someone please check?
> > > >>
> > > >> Thanks,
> > > >> Raúl.
> > > >>
> > > >>
> > > >
> >

Re: [VOTE] Apache Ignite 1.4.0 Release (RC1)

2015-09-25 Thread Anton Vinogradov 
+1

On Fri, Sep 25, 2015 at 3:49 PM, Denis Magda  wrote:

> +1
>
> -Original Message-
> From: "Yakov Zhdanov" 
> Sent: ‎9/‎25/‎2015 15:37
> To: "dev@ignite.apache.org" 
> Subject: [VOTE] Apache Ignite 1.4.0 Release (RC1)
>
> Dear Sirs!
>
> We have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/1.4.0-rc1/
>
> I am very glad to mention that this is the first Ignite release as top
> level project! Thanks everyone for help this to happen!
>
> Tag name is
> ignite-1.4.0-rc1
>
> 1.4.0 changes:
> * Added SSL support to communication and discovery.
> * Added support for log4j2.
> * Added versioned entry to cache API.
> * Added client node based JDBC driver implementation.
> * Fixed consistency issue for custom events processing within discovery.
> * Fixed race in cache swap/unswap logic.
> * Fixed IGNITE_HOME resolution with JBoss.
> * Fixed configuration file resolution on classpath.
> * Fixed MBean registration for caches.
> * Fixed near cache evictions with offheap.
> * Fixed SQL queries group index logic.
> * Fixed memory leak in partitioned transactional cache.
> * Fixed auto-retries for cache operations in recoverable cases.
> * Fixed affinity routing in compute grid.
> * Many stability and fault-tolerance fixes.
>
> DEVNOTES
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
>
> RELEASENOTES
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/ignite-1.4.0-rc1
>
> Please start voting.
>
> +1 - to accept Apache Ignite 1.4.0
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 1.4.0 (explain why)
>
> This vote will go for 72 hours.
>
> --Yakov
>

[jira] [Created] (IGNITE-1548) Optimize portable object header.

2015-09-25 Thread Vladimir Ozerov (JIRA) 
Vladimir Ozerov created IGNITE-1548:
---

 Summary: Optimize portable object header.
 Key: IGNITE-1548
 URL: https://issues.apache.org/jira/browse/IGNITE-1548
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.1.4
Reporter: Vladimir Ozerov
Priority: Blocker
 Fix For: ignite-1.5


Currently portable object header takes 18 bytes:
1 - object type
1 - user flag
4 - type ID
4 - hash code
4 - length
4 - raw offset.

The following optimizations can be applied:
1) User flag can be easilty merged into object type. (-1 byte)
2) In most cases only length or raw-offset exists, but not both. Remove one of 
them and encode state into the object type. (-4 bytes)
3) Length usually fit in 1-2 bytes. Encode it with "variable bytes" algo (-2-3 
bytes).

As a result we will shrink header size from 18 to 10-11 bytes. Encoded states 
will require 6 additional object types:
104 => system, with length 
105 => system, with raw offset
106 => system, with both
107, 108, 109 - the same, but for user types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: More efficient writes of messages in direct mode.

2015-09-25 Thread Dmitriy Setrakyan 
Excellent points, and does not seem hard to do.

On Fri, Sep 25, 2015 at 7:06 AM, Vladimir Ozerov 
wrote:

> Igniters,
>
> Several observations on our "direct" message writes:
>
> 1) For some reason we write null arrays, maps and ints as "-1" integer,
> while it can be encoded in a single byte. And our cache messages have
> lots of containers, which are commonly null.
>
> 2) Some frequently used data types could benefit significantly if integers
> are written in compacted form, while others could not. Several examples:
>
> GridCacheVersion:
> topVer - fits in 2 bytes instead of 4;
> nodeOrderDrId -  1 instead of 4;
> globalTime - 6 instead of 8;
> order -  6 instead of 8.
> Result: shrunk from 24 to 15 bytes with minimal overhead.
>
> AffinityTopologyVersion:
> topVer -  1-2 bytes instead of 8.
> minorTopVer - 1 byte instead of 4;
> Result: shrunked from 12 to 2-3 bytes in 99% cases.
>
> IgniteUuid - takes 24 bytes, but can be shrunk only to 22 bytes => bad
> candidate for optimziation.
>
> I picked random test and set breakpoint into random cache message -
> GridDhtTxPrepareRequest. It was 444 bytes long with a single int-int pair
> as a payload. At least 90 bytes (~20%) could be saved easily with described
> optimziations.
>
> Looks like we should pay more attention to it.
>
> Vladimir.
>