igniterouter.sh

[Valentin Kulichenko]

Folks,

Our bin folder still contains igniterouter.{sh|bat} script. Previously it
was used to support indirect access from thin client to cluster. Since thin
client is deprecated for a while, is there a use case when router can be
used?

I think it makes sense to remove these scripts for now. If we ever
resurrect this functionality, we can always bring them back.

Thoughts?

-Val

[jira] [Created] (IGNITE-5978) [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5978:
-

 Summary: [Test Failed] 
IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1
 Key: IGNITE-5978
 URL: https://issues.apache.org/jira/browse/IGNITE-5978
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=759891=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId677264269171099154.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5980) [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5980:
-

 Summary: [Test Failed]  
IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
 Key: IGNITE-5980
 URL: https://issues.apache.org/jira/browse/IGNITE-5980
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Example of failing
http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId-4067536648656067727



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5979:
-

 Summary: [Test Failed]  
GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
 Key: IGNITE-5979
 URL: https://issues.apache.org/jira/browse/IGNITE-5979
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Example of failing  - 
http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: igniterouter.sh

[Valentin Kulichenko]

I'm pretty sure current router will not be able to work with new client
anyway, which will make even more confusing than now. I think it's better
to remove these scripts in next release (unless both client and router are
back in this release of course :) ).

-Val

On Mon, Aug 7, 2017 at 1:13 PM, Vladimir Ozerov 
wrote:

> Val,
>
> Thin client is like Arnold - he'll be back ) We already working on it. I
> propose to delay this question a bit, until we understand that router is
> not needed for new thin client.
>
> пн, 7 авг. 2017 г. в 23:07, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > Folks,
> >
> > Our bin folder still contains igniterouter.{sh|bat} script. Previously it
> > was used to support indirect access from thin client to cluster. Since
> thin
> > client is deprecated for a while, is there a use case when router can be
> > used?
> >
> > I think it makes sense to remove these scripts for now. If we ever
> > resurrect this functionality, we can always bring them back.
> >
> > Thoughts?
> >
> > -Val
> >
>

Re: igniterouter.sh

[Vladimir Ozerov]

Val,

Thin client is like Arnold - he'll be back ) We already working on it. I
propose to delay this question a bit, until we understand that router is
not needed for new thin client.

пн, 7 авг. 2017 г. в 23:07, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:

> Folks,
>
> Our bin folder still contains igniterouter.{sh|bat} script. Previously it
> was used to support indirect access from thin client to cluster. Since thin
> client is deprecated for a while, is there a use case when router can be
> used?
>
> I think it makes sense to remove these scripts for now. If we ever
> resurrect this functionality, we can always bring them back.
>
> Thoughts?
>
> -Val
>

[jira] [Created] (IGNITE-5981) IgniteContext starts server nodes on executors

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-5981:
---

 Summary: IgniteContext starts server nodes on executors
 Key: IGNITE-5981
 URL: https://issues.apache.org/jira/browse/IGNITE-5981
 Project: Ignite
  Issue Type: Bug
  Components: spark
Affects Versions: 2.1
Reporter: Valentin Kulichenko
 Fix For: 2.2


Currently {{IgniteContext#ignite()}} method creates client node only if it is 
invoked on driver. However, in case standalone mode is used, this should happen 
also executors (or basically anywhere within Spark).

Most likely, it would be enough to replace this line:
{code}
if (sparkContext != null) igniteCfg.setClientMode(true)
{code}
with this:
{code}
if (standalone || sparkContext != null) igniteCfg.setClientMode(true)
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5955:
---

 Summary: Ignite Continuous Query (Queries 3): 
IgniteCacheContinuousQueryClientReconnectTest fails
 Key: IGNITE-5955
 URL: https://issues.apache.org/jira/browse/IGNITE-5955
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov


Reproducible locally with the same exception as on TC.

According to [TC 
history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
 is failing since mid of April.

Last commit where test has been passing is *b6b3d3754849*. After it test 
started failing, but on different line than that it is failing on now.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: release procedure

[Anton Vinogradov]

Vote for #3

On Sun, Aug 6, 2017 at 3:37 PM, Oleg Ostanin  wrote:

> Hi,
>
> I'd like to start a discussion about Apache Ignite release procedure.
>
> I'm working on ticket Ignite-5249 "The release build procedure should be
> placed on the CI/CD server and available to run for the release engineer."
>
> https://issues.apache.org/jira/browse/IGNITE-5249
>
> Currently we have three options for release:
>
> 1. Release engineer can do all the necessary steps on his local machine. It
> will require installing tons of soft like maven, doxigen, candle and so on.
> Also building .net part of the project will require access to Windows OS.
> Build steps will not be transparent for community. Environment will not be
> the same for each release which can lead to the compatibility issues.
>
> 2. All the steps (including signing) can be done on the public continuous
> integration server. Environment will be the same for each release, all the
> steps will be transparent for community, but it will require uploading at
> least one private gpg certificate on the server. This is the high security
> risk and I'm mentioning this option only for the sake of completeness.
>
> 3. Building of the project can be performed on the public continuous
> integration server and then artifacts can be downloaded on the local
> machine and signed and deployed to the staging repository from that local
> machine by running maven commands. No sharing of any credentials and
> certificates will be needed, environment will be the same for each release,
> all the steps will be transparent for community, artifacts created on the
> CI server can be verified by check-sums after uploading to the repository.
>
> Please, let me know if you have any suggestion or any questions about
> anything related.
>

[jira] [Created] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5954:
-

 Summary: Ignite Cache Failover: 
GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails
 Key: IGNITE-5954
 URL: https://issues.apache.org/jira/browse/IGNITE-5954
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev


Probably, it's broken after IGNITE-5272.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: ODBC API conformance page updated

[Dmitriy Setrakyan]

Igor, can you please rename the page for now?

On Mon, Aug 7, 2017 at 2:33 AM, Igor Sapego  wrote:

> Dmitriy,
>
> There are comments where there are issues with implementation of certain
> features. Where there are no such comment, it is simply means that those
> features are not implemented just because no one has ever implemented
> them.
>
> Best Regards,
> Igor
>
> On Fri, Aug 4, 2017 at 9:32 PM, Dmitriy Setrakyan 
> wrote:
>
> > Nice!
> >
> > I am not sure I like the name "conformance" however. How about renaming
> it
> > to "specification"?
> >
> > Also, would be nice to get a sense about why certain features are
> > unsupported and what are the plans to get closer to 100% compliance?
> >
> > D.
> >
> > On Fri, Aug 4, 2017 at 1:08 PM, Vladimir Ozerov 
> > wrote:
> >
> > > Igor,
> > >
> > > Vary cool!
> > >
> > > On Fri, Aug 4, 2017 at 1:15 PM, Igor Sapego 
> wrote:
> > >
> > > > Hi Igniters,
> > > >
> > > > I've updated an ODBC API conformance page - [1],
> > > > so take a look if you are interested.
> > > >
> > > > Also, make sure you edit this page if you are adding
> > > > new features, or modifying existing features of the Ignite
> > > > ODBC driver.
> > > >
> > > > [1] - https://apacheignite.readme.io/v2.1/docs/conformance
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-5956) Ignite Continuous Query (Queries 3): IgniteCacheDistributedJoinPartitionedAndReplicatedTest fails

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5956:
---

 Summary: Ignite Continuous Query (Queries 3): 
IgniteCacheDistributedJoinPartitionedAndReplicatedTest fails
 Key: IGNITE-5956
 URL: https://issues.apache.org/jira/browse/IGNITE-5956
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
 Fix For: 2.2


Reproducible locally.

May be broken by commit *70eed75422ea*.

Fails with exception:
{noformat}
javax.cache.CacheException: Failed to execute query: for distributed join all 
REPLICATED caches must be at the end of the joined tables list.

at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2CollocationModel.isCollocated(GridH2CollocationModel.java:704)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:239)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1309)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1804)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1802)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2282)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1809)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:788)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:758)
at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.queryPlan(GridCommonAbstractTest.java:1650)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.checkQuery(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:389)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.checkQueries(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:364)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.join(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:283)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.testJoin2(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1980)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:131)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1895)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5951) DDL: Support CREATE VIEW

[Vyacheslav Koptilin (JIRA)]

Vyacheslav Koptilin created IGNITE-5951:
---

 Summary: DDL: Support CREATE VIEW
 Key: IGNITE-5951
 URL: https://issues.apache.org/jira/browse/IGNITE-5951
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.1
Reporter: Vyacheslav Koptilin
Priority: Minor


Ignite should support sql VIEW.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [IGNITE-5717] improvements of MemoryPolicy default size

[Sergey Chugunov]

Dmitriy,

When Ignite node "allocates memory" it actually just reserves a chunk in
its address space, almost no physical RAM is used.

I can easily start half a dozen of ignite nodes with current defaults on my
laptop with only 16 Gigs of RAM; and each node will "allocate" around 12
Gigs; 72 gigabytes in total.
The laptop will do easily with it so far I don't stream any data to the
grid.

But when I put some pressure to the grid, massive swapping of memory pages
will show up as OS begins trying to keep a huge amount of pages of
different processes in memory.

So indicator "we are running out of memory" just doesn't work here.

Thanks,
Sergey.

On Fri, Aug 4, 2017 at 1:01 PM,  wrote:

> But why? We allocate the memory, so we should know when it runs out. What
> am i missing?
>
> ⁣D.​
>
> On Aug 4, 2017, 11:55 AM, at 11:55 AM, Sergey Chugunov <
> sergey.chugu...@gmail.com> wrote:
> >I used GC and java only as an example, they are not applicable to
> >Ignite
> >case where we manage offheap memory.
> >
> >My point is that there is no easy way to implement this feature in
> >Ignite,
> >and more time is needed to properly design it and account for all
> >risks.
> >
> >Thanks,
> >Sergey.
> >
> >On Fri, Aug 4, 2017 at 12:44 PM,  wrote:
> >
> >> Hang on. I thought we were talking about offheap size, GC should not
> >be
> >> relevant. Am I wrong?
> >>
> >> ⁣D.​
> >>
> >> On Aug 4, 2017, 11:38 AM, at 11:38 AM, Sergey Chugunov <
> >> sergey.chugu...@gmail.com> wrote:
> >> >Do you see an obvious way of implementing it?
> >> >
> >> >In java there is a heap and GC working on it. And for instance, it
> >is
> >> >possible to make a decision to throw an OOM based on some gc
> >metrics.
> >> >
> >> >I may be wrong but I don't see a mechanism in Ignite to use it right
> >> >away
> >> >for such purposes.
> >> >And implementing something without thorough planning brings huge
> >risk
> >> >of
> >> >false positives with nodes stopping when they don't have to.
> >> >
> >> >That's why I think it must be implemented and intensively tested as
> >> >part of
> >> >a separate ticket.
> >> >
> >> >Thanks,
> >> >Sergey.
> >> >
> >> >On Fri, Aug 4, 2017 at 12:18 PM,  wrote:
> >> >
> >> >> Without #3, the #1 and #2 make little sense.
> >> >>
> >> >> Why is #3 so difficult?
> >> >>
> >> >> ⁣D.​
> >> >>
> >> >> On Aug 4, 2017, 10:46 AM, at 10:46 AM, Sergey Chugunov <
> >> >> sergey.chugu...@gmail.com> wrote:
> >> >> >Dmitriy,
> >> >> >
> >> >> >Last item makes perfect sense to me, one may think of it as an
> >> >> >"OutOfMemoryException" in java.
> >> >> >However, it looks like such feature requires considerable efforts
> >to
> >> >> >properly design and implement it, so I would propose to create a
> >> >> >separate
> >> >> >ticket and agree upon target version for it.
> >> >> >
> >> >> >Items #1 and #2 will be implemented under IGNITE-5717. Makes
> >sense?
> >> >> >
> >> >> >Thanks,
> >> >> >Sergey.
> >> >> >
> >> >> >On Thu, Aug 3, 2017 at 4:34 AM, Dmitriy Setrakyan
> >> >> >
> >> >> >wrote:
> >> >> >
> >> >> >> Here is what we should do:
> >> >> >>
> >> >> >>1. Pick an acceptable number. Does not matter if it is 10%
> >or
> >> >50%.
> >> >> >>2. Print the allocated memory in *BOLD* letters into the
> >log.
> >> >> >>3. Make sure that Ignite server never hangs due to the low
> >> >memory
> >> >> >issue.
> >> >> >>We should sense it and kick the node out automatically,
> >again
> >> >with
> >> >> >a
> >> >> >> *BOLD*
> >> >> >>message in the log.
> >> >> >>
> >> >> >>  Is this possible?
> >> >> >>
> >> >> >> D.
> >> >> >>
> >> >> >> On Wed, Aug 2, 2017 at 6:09 PM, Vladimir Ozerov
> >> >> >
> >> >> >> wrote:
> >> >> >>
> >> >> >> > My proposal is 10% instead of 80%.
> >> >> >> >
> >> >> >> > ср, 2 авг. 2017 г. в 18:54, Denis Magda :
> >> >> >> >
> >> >> >> > > Vladimir, Dmitriy P.,
> >> >> >> > >
> >> >> >> > > Please see inline
> >> >> >> > >
> >> >> >> > > > On Aug 2, 2017, at 7:20 AM, Vladimir Ozerov
> >> >> >
> >> >> >> > > wrote:
> >> >> >> > > >
> >> >> >> > > > Denis,
> >> >> >> > > >
> >> >> >> > > > The reason is that product should not hang user's
> >computer.
> >> >How
> >> >> >else
> >> >> >> > this
> >> >> >> > > > could be explained? I am developer. I start Ignite, 1
> >node,
> >> >2
> >> >> >nodes,
> >> >> >> X
> >> >> >> > > > nodes, observe how they join topology. Add one key, 10
> >keys,
> >> >1M
> >> >> >keys.
> >> >> >> > > Then
> >> >> >> > > > I do a bug in example and load 100M keys accidentally -
> >> >restart
> >> >> >the
> >> >> >> > > > computer. Correct behavior is to have small "maxMemory"
> >by
> >> >> >default to
> >> >> >> > > avoid
> >> >> >> > > > that. User should get exception instead of hang. E.g.
> >Java's
> >> >> >"-Xmx"
> >> >> >> is
> >> >> >> > > > typically 25% of RAM - more adequate value, comparing to
> >> >> >Ignite.
> >> >> 

[GitHub] ignite pull request #2408: IGNITE-5941 : Fixed index name length restriction...

[ilantukh]

GitHub user ilantukh opened a pull request:

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

IGNITE-5941 : Fixed index name length restrictions.



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

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

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

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


commit ef081b334f38e0a4d0fcb653009d9cdf2ba3d83c
Author: Ilya Lantukh 
Date:   2017-08-07T14:33:09Z

ignite-5941 : Fixed index name length restrictions.




---
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.
---

[GitHub] ignite pull request #2409: Ignite gg 12508

[glukos]

GitHub user glukos opened a pull request:

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

Ignite gg 12508

PR for tests run.

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

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

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

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


commit 2e5c343d911e353c6d82630d09562664cc5e89e2
Author: Sergey Chugunov 
Date:   2017-08-07T08:34:01Z

IGNITE-5950 incorrect assertion fixed

commit aeed07ff7e1095e9234c5bafa494bfa13378846e
Author: Ivan Rakov 
Date:   2017-08-07T14:26:07Z

IGNITE-5961 Align pages in LFS partition files to pageSize




---
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.
---

[jira] [Created] (IGNITE-5952) Need to refactor IgniteSystemProperties

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5952:
-

 Summary: Need to refactor IgniteSystemProperties
 Key: IGNITE-5952
 URL: https://issues.apache.org/jira/browse/IGNITE-5952
 Project: Ignite
  Issue Type: Improvement
Reporter: Yakov Zhdanov
Priority: Minor


I would think of introducing enum each member of one should clearly define:
# name and envvar/sysprop name to set
# type
# default value
# additional methods for parsing and validation
# documentation, possibly, with links to code 

This should help to avoid situations like this:
org.apache.ignite.internal.IgniteKernal#PERIODIC_STARVATION_CHECK_FREQ and 
org.apache.ignite.IgniteSystemProperties#IGNITE_STARVATION_CHECK_INTERVAL. Here 
property and its default are defined with different properties and default is 
not stated in configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2405: IGNITE-5384: cleanup

[tledkov-gridgain]

Github user tledkov-gridgain closed the pull request at:

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


---
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.
---

[jira] [Created] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5960:
---

 Summary: Ignite Continuous Query (Queries 3): 
CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic
 is flaky
 Key: IGNITE-5960
 URL: https://issues.apache.org/jira/browse/IGNITE-5960
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
 Fix For: 2.2


According to [TC 
history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=6546112007182082024=testDetails_Ignite20Tests=%3Cdefault%3E]
 test is flaky.

It is possible to reproduce it locally, sample run shows 9 failed tests out of 
30 overall executed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5961) Align pages in LFS partition files to pageSize

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5961:
--

 Summary: Align pages in LFS partition files to pageSize
 Key: IGNITE-5961
 URL: https://issues.apache.org/jira/browse/IGNITE-5961
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.1
Reporter: Ivan Rakov
Assignee: Ivan Rakov
Priority: Critical
 Fix For: 2.2


We store 17 bytes of header at the start of every partition file:
{noformat}
/** Allocated field offset. */
static final int HEADER_SIZE = 8/*SIGNATURE*/ + 4/*VERSION*/ + 1/*type*/ + 
4/*page size*/;
{noformat}
Even if pageSize is equal to OS page cache size and equal to SSD disk page size 
(which is best scenario), when generate two dirty pages insteadf of one. This 
is suboptimal and can be a bottleneck of checkpoint write speed. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5958) Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5958:
---

 Summary: Ignite Cache 3: 
IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator  fails
 Key: IGNITE-5958
 URL: https://issues.apache.org/jira/browse/IGNITE-5958
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko


Failure ratio ~90%.
No additional errors or exceptions in test.

{noformat}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Failed to perform cache operation (cache topology is not valid): test0
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1318)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1032)
at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:872)
at 
org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:230)
at 
org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator(IgniteTopologyValidatorGridSplitCacheTest.java:161)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to perform 
cache operation (cache topology is not valid): test0
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFutureAdapter.validateCache(GridDhtTopologyFutureAdapter.java:104)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:415)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1167)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:656)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2334)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2311)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1029)
... 12 more
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2407: IGNITE-5211 Classes based constructor for QueryEn...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5211  Classes based constructor for QueryEntities



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

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

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

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


commit f027c03167183254768c24c0aca4a8ddc33b985a
Author: tledkov-gridgain 
Date:   2017-08-03T14:36:23Z

IGNITE-5211 Classes based constructor for QueryEntities

commit e8a7317787a6b89e793745b37c53a8b6b9939136
Author: tledkov-gridgain 
Date:   2017-08-03T14:48:01Z

IGNITE-5211 minors

commit 4aa27a1efc75703a2fc40ba54e8a23ad2f4ff0cc
Author: tledkov-gridgain 
Date:   2017-08-07T09:49:03Z

Merge branch '_master' into ignite-5211

commit 91090b597a3d6a026b20b3477142376046c1808b
Author: tledkov-gridgain 
Date:   2017-08-07T09:52:36Z

Merge branch '_master' into ignite-5211

commit e8e850607a85152429a23fe72da2a0d5bbbe018c
Author: devozerov 
Date:   2017-08-07T10:53:56Z

Cosmetics.

commit 89c47cc290821db18b7731dace70d095829cdfcb
Author: tledkov-gridgain 
Date:   2017-08-07T12:23:36Z

IGNITE-5211: fix review comments

commit ca191457fe554c39a1395d778bfe119477f3b5a8
Author: devozerov 
Date:   2017-08-07T12:45:09Z

Removing unused classes.




---
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.
---

[jira] [Created] (IGNITE-5957) Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5957:
---

 Summary: Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated 
fails
 Key: IGNITE-5957
 URL: https://issues.apache.org/jira/browse/IGNITE-5957
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko


Test is flaky. Success ratio ~50%.

Exception:

{noformat}
junit.framework.AssertionFailedError: expected:<1> but was:<2>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at 
org.apache.ignite.internal.processors.igfs.IgfsStreamsSelfTest.testCreateFileColocated(IgfsStreamsSelfTest.java:213)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5959) Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5959:
---

 Summary: Ignite Hadoop: testClientReconnect and 
testClientReconnectMultithreaded fail
 Key: IGNITE-5959
 URL: https://issues.apache.org/jira/browse/IGNITE-5959
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko
 Fix For: 2.2


Tests are flaky. Failure ratio ~ 30%

IgniteHadoopFileSystemClientBasedDualSyncSelfTest.testClientReconnectMultithreaded
  
IgniteHadoopFileSystemClientBasedDualAsyncSelfTest.testClientReconnect  
IgniteHadoopFileSystemClientBasedDualAsyncSelfTest.testClientReconnectMultithreaded
 
IgniteHadoopFileSystemClientBasedPrimarySelfTest.testClientReconnectMultithreaded
   
IgniteHadoopFileSystemClientBasedProxySelfTest.testClientReconnect 

Common case - test fails when tries to stop Ignite node:

{noformat}
[2017-08-07 03:29:26,089][ERROR][test-runner-#23774%grid%][root] Failed to stop 
grid [igniteInstanceName=grid3, cancel=false]
class org.apache.ignite.IgniteClientDisconnectedException: Client node 
disconnected: test-IGFS-cli
at 
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1289)
at 
org.apache.ignite.internal.processors.hadoop.impl.igfs.IgniteHadoopFileSystemClientBasedAbstractSelfTest.restartServerNodesExceptOne(IgniteHadoopFileSystemClientBasedAbstractSelfTest.java:166)
at 
org.apache.ignite.internal.processors.hadoop.impl.igfs.IgniteHadoopFileSystemClientBasedAbstractSelfTest.testClientReconnectMultithreaded(IgniteHadoopFileSystemClientBasedAbstractSelfTest.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5962) Increase max length of index name

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-5962:


 Summary: Increase max length of index name
 Key: IGNITE-5962
 URL: https://issues.apache.org/jira/browse/IGNITE-5962
 Project: Ignite
  Issue Type: Improvement
  Components: general, sql
Affects Versions: 2.1
Reporter: Ilya Lantukh


In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length was 
reduced from 768 to 256 bytes. If we need to support longer names, we need to 
change format of metastore data pages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5963) Ignite Cache 6: Flaky failure IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5963:
--

 Summary:  Ignite Cache 6: Flaky failure 
IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC
 Key: IGNITE-5963
 URL: https://issues.apache.org/jira/browse/IGNITE-5963
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


Test sometimes fails on teamcity, please see
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-6026696383836355176=testDetails

{noformat}
java.lang.AssertionError: Exception has not been thrown.
at 
org.apache.ignite.testframework.GridTestUtils.assertThrowsWithCause(GridTestUtils.java:425)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:464)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:455)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$CI2Exc.apply(IgniteOptimisticTxSuspendResumeTest.java:697)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.executeTestForAllCaches(IgniteOptimisticTxSuspendResumeTest.java:669)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.testTxTimeoutOnSuspend(IgniteOptimisticTxSuspendResumeTest.java:455)
{noformat}

Test was created under issue IGNITE-5712

Does not reprocuced locally (30 runs on Win10).

But on CI server success rate is 94%



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5948) SQL: UNIQUE constraint support.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5948:


 Summary: SQL: UNIQUE constraint support.
 Key: IGNITE-5948
 URL: https://issues.apache.org/jira/browse/IGNITE-5948
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Reporter: Andrew Mashenkov






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2403: for test purposes.

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

for test purposes.



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4800-fix-test

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

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


commit a1235d400aec675b5b2b7d1c6d538dd8f38aa590
Author: Andrey V. Mashenkov 
Date:   2017-08-07T07:56:43Z

IGNITE-4800: Lucene query may fails with NPE. This closes #2315.




---
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.
---

[jira] [Created] (IGNITE-5950) Incorrect assertion for cache size

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5950:
---

 Summary: Incorrect assertion for cache size
 Key: IGNITE-5950
 URL: https://issues.apache.org/jira/browse/IGNITE-5950
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.1
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Critical
 Fix For: 2.2


*PagePartitionCountersIO::readCacheSizes* incorrectly asserts cache size:

{noformat}
public boolean readCacheSizes(long pageAddr, Map res) {
int cnt = getCount(pageAddr);

assert cnt >= 0 && cnt <= Short.MAX_VALUE : cnt;

if (cnt == 0)
return true;

int off = ITEMS_OFF;

for (int i = 0; i < cnt; i++) {
int cacheId = PageUtils.getInt(pageAddr, off);
off += 4;

assert cacheId != 0;

long cacheSize = PageUtils.getLong(pageAddr, off);
off += 8;

assert cacheSize > 0 : cacheSize; //WRONG assertion! cache of zero 
size if totally legal

Long old = res.put(cacheId, cacheSize);

assert old == null;
}

return getLastFlag(pageAddr);
}
{noformat}

Correct assertion is {{cacheSize >= 0}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: ODBC API conformance page updated

[Igor Sapego]

Dmitriy,

There are comments where there are issues with implementation of certain
features. Where there are no such comment, it is simply means that those
features are not implemented just because no one has ever implemented
them.

Best Regards,
Igor

On Fri, Aug 4, 2017 at 9:32 PM, Dmitriy Setrakyan 
wrote:

> Nice!
>
> I am not sure I like the name "conformance" however. How about renaming it
> to "specification"?
>
> Also, would be nice to get a sense about why certain features are
> unsupported and what are the plans to get closer to 100% compliance?
>
> D.
>
> On Fri, Aug 4, 2017 at 1:08 PM, Vladimir Ozerov 
> wrote:
>
> > Igor,
> >
> > Vary cool!
> >
> > On Fri, Aug 4, 2017 at 1:15 PM, Igor Sapego  wrote:
> >
> > > Hi Igniters,
> > >
> > > I've updated an ODBC API conformance page - [1],
> > > so take a look if you are interested.
> > >
> > > Also, make sure you edit this page if you are adding
> > > new features, or modifying existing features of the Ignite
> > > ODBC driver.
> > >
> > > [1] - https://apacheignite.readme.io/v2.1/docs/conformance
> > >
> > > Best Regards,
> > > Igor
> > >
> >
>

[GitHub] ignite pull request #2404: Ignite 5953 - Missed off-heap unswapping in GridC...

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

Ignite 5953 - Missed off-heap unswapping in GridCacheMap.versionedValue()



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

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

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

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


commit 3a9cbed4e692e76ad884e60a4f5edc670e6b3c8f
Author: Pavel Tupitsyn 
Date:   2016-08-08T14:00:04Z

IGNITE-3630 .NET: Add pure binary mode example with put-get and queries.

commit d5e15af76044cf65385672f8528d48ecdeca3cb6
Author: Pavel Tupitsyn 
Date:   2016-11-02T09:02:00Z

IGNITE-4121 .NET: add ScanQuery example

commit 74f8308d10fc011c00e52efcdb315b35cc79e60a
Author: Pavel Tupitsyn 
Date:   2016-11-02T12:59:15Z

IGNITE-4123 .NET: Remove [Serializable] from Employee in examples

commit 92fff630fbf36c82f93bbd9ddd53d11bed44e772
Author: devozerov 
Date:   2016-11-02T14:50:51Z

Restored services compatibility.

commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

commit fc7ce5a4d72145f2e8a86debeda264ef0a5b37e3
Author: isapego 
Date:   2016-11-07T10:26:05Z

IGNITE-4090: Added flags so stdint and limits can be used in C++.

commit a98804a249496ba9bafbc96daa7aaf25b3d36724
Author: Igor Sapego 
Date:   2016-11-07T11:00:00Z

IGNITE-4113: Added tests. Added Statement::Set/GetAttribute.

commit b1c7c9bb95c900083702d0ba0362edf3aea5a7b4
Author: sboikov 
Date:   2016-11-07T12:40:36Z

GG-11360 - Implement SQL queries cancellation
Fix for commit 80abd1b: for distributed joins need always send cancel 
request.

commit 319014de075c80fb15e58172cc24e35ce16b56cf
Author: Pavel Tupitsyn 
Date:   2016-11-07T14:53:40Z

IGNITE-4132 .NET: Improve BinaryConfiguration documentation

commit 950bad474ef29f9b808e74034c49a69d57eb2740
Author: dkarachentsev 
Date:   2016-11-08T11:03:34Z

GG-11655 - Restore service compatibility with releases before 1.5.30.

commit 3d19bfc2b66574e3945ce17c7a4dfe77d0070b8d
Author: dkarachentsev 
Date:   2016-11-08T11:04:36Z

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

commit 1612b6d66fed032182a41e90da71e6b986ae087b
Author: Pavel Tupitsyn 
Date:   2016-11-08T11:07:54Z

.NET: Fix minor analysis warnings

commit e821dc0083003bc81058b1cb223d8a8a2ee44daf
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:09:21Z

IGNITE-2079 (revert commit) GridCacheIoManager eats exception trail if it 
falls into the directed case

commit c2c82ca44befe4570325dd6cf2ba885e0d90596c
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:10:10Z

Merge remote-tracking branch 'professional/ignite-1.6.11' into ignite-1.6.11

commit 865bbcf0f41a0c4944e0928f1758d43a0eae82c5
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:18:29Z

Revert "Merge remote-tracking branch 'professional/ignite-1.6.11' into 
ignite-1.6.11"

This reverts commit c2c82ca44befe4570325dd6cf2ba885e0d90596c, reversing
changes made to e821dc0083003bc81058b1cb223d8a8a2ee44daf.

commit 9726421ff9efb2b19813b2fd6ad27a3728b5ab1a
Author: Dmitriy Govorukhin 
Date:   

[jira] [Created] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-5949:


 Summary: DDL: Support ALTER TABLE DROP COLUMN
 Key: IGNITE-5949
 URL: https://issues.apache.org/jira/browse/IGNITE-5949
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Reporter: Andrew Mashenkov
 Fix For: 2.2


Ignite should supports DROP COLUMN operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2394: IGNITE-5880: BLAS integration phase 2

[ybabak]

Github user ybabak closed the pull request at:

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


---
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.
---

[jira] [Created] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5967:
--

 Summary: Flaky fail in Ignite Java Client: 
RedisProtocolStringSelfTest.testGetSet 
 Key: IGNITE-5967
 URL: https://issues.apache.org/jira/browse/IGNITE-5967
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Govorukhin
 Fix For: 2.2


RedisProtocolStringSelfTest.testGetSet 

redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
stream.
at redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
at redis.clients.jedis.Protocol.process(Protocol.java:151)
at redis.clients.jedis.Protocol.read(Protocol.java:215)
at 
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
at redis.clients.jedis.Jedis.get(Jedis.java:153)
at 
org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
--- Stdout: ---
[2017-08-07 06:28:44,379][INFO ][main][root] >>> Starting test: 
RedisProtocolStringSelfTest#testGetSet <<<
[2017-08-07 06:28:52,390][INFO ][main][root] >>> Stopping test: 
RedisProtocolStringSelfTest#testGetSet in 8010 ms <<<
--- Stderr: ---
[2017-08-07 06:28:52,389][ERROR][main][root] Test failed.
redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
stream.
at redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
at redis.clients.jedis.Protocol.process(Protocol.java:151)
at redis.clients.jedis.Protocol.read(Protocol.java:215)
at 
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
at redis.clients.jedis.Jedis.get(Jedis.java:153)
at 
org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5968:
--

 Summary: Test fail in Ignite Cache 2: 
GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead
 Key: IGNITE-5968
 URL: https://issues.apache.org/jira/browse/IGNITE-5968
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Govorukhin
 Fix For: 2.2


java.util.concurrent.TimeoutException: Test has been timed out 
[test=testPrimaryAndBackupDead, timeout=30]
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1949)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5965) Ignite Basic: Flaky failure of GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5965:
--

 Summary: Ignite Basic: Flaky failure of  
GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology
 Key: IGNITE-5965
 URL: https://issues.apache.org/jira/browse/IGNITE-5965
 Project: Ignite
  Issue Type: Test
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


Test has 85% success rate in master:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-2642357454043293898=testDetails_Ignite20Tests=%3Cdefault%3E
Flaky failure is reproduced locally with similar success rate (24/30, Win 10).
{noformat}
junit.framework.AssertionFailedError: 
Expected :4
Actual   :5
 


at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessorAbstractSelfTest.checkCount(GridServiceProcessorAbstractSelfTest.java:765)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.checkDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:287)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:144)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)


{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5964) test fail: TcpClientDiscoverySpiSelfTest (disconnectLatch timeout)

[Konstantin Dudkov (JIRA)]

Konstantin Dudkov created IGNITE-5964:
-

 Summary: test fail: TcpClientDiscoverySpiSelfTest (disconnectLatch 
timeout)
 Key: IGNITE-5964
 URL: https://issues.apache.org/jira/browse/IGNITE-5964
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Konstantin Dudkov
 Fix For: 2.2


flake tests: testReconnectAfterFailTopologyChanged, 
testReconnectAfterTopologyChanged

disconnectLatch timeout

{code:java}
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.reconnectAfterFail(TcpClientDiscoverySpiSelfTest.java:1422)
at 
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testReconnectAfterFailTopologyChanged(TcpClientDiscoverySpiSelfTest.java:1331)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

IgniteUtils#currentTimeMillis

[Николай Ижиков]

Hello, Igniters.

I found unusual implementation of IgniteUtils#currentTimeMillis function.
Method is not simple proxy to System.currentTimeMillis
Instead it read static variable which updated by dedicated thread:

https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java#L3251

while (true) {
curTimeMillis = System.currentTimeMillis();

try {
Thread.sleep(10);
}
catch (InterruptedException ignored) {
break;
}
}

As far as i know `Thread.sleep` is unprecise function especially under
heavy load and on small timeout values like 10 ms.
Seems that we get very unprecise values of currentTimeMillis.

I think that can lead to difficult bugs like
https://issues.apache.org/jira/browse/IGNITE-5963

What is purpose of current implementation?

-- 
Nikolay Izhikov
nizhikov@gmail.com

[jira] [Created] (IGNITE-5966) IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory

[Alexey Kukushkin (JIRA)]

Alexey Kukushkin created IGNITE-5966:


 Summary: IgniteCache#get() fails with "Requesting mapping from 
grid failed" when deserialising binary object loaded from 
CacheJdbcPojoStoreFactory
 Key: IGNITE-5966
 URL: https://issues.apache.org/jira/browse/IGNITE-5966
 Project: Ignite
  Issue Type: Bug
 Environment: Ignite 2.1.4
Reporter: Alexey Kukushkin
Assignee: Alexey Kukushkin


STEPS TO REPRODUCE
1. A running MySQL database with at least one table with an Integer key and 
some data
2. Use WebConsole to automatically generate an Ignite project from the RDBMS. 
In the WebConsole add a cache for the table containing data
3. Build the project
4. Start the cluster (run ServerNodeSpringStartup)
5. Load the data (run LoadCaches)
6. Run simple "get data" code against the running cluster with the data loaded. 
Make sure you do NOT keep binary and do NOT put anything to the cache except 
loading data on step #5. For example, if the cache is "AircraftCache", the type 
is "Aircraft" and a row with ID 1 exists in the DB, then:
IgniteCache aircraftCache = 
ignite.getOrCreateCache("AircraftCache");
System.out.format("1->%s\n", aircraftCache.get(1));
EXPECTED:
1...5: Project is generated, cluster runs, data is loaded
6: The entry with ID 1 is output to the console
ACTUAL:"
1..5: As expected
6: javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Requesting mapping from grid failed for [platformId=0, typeId=-1267085398]
ANALYSIS
The “typeId -> MappedName” mappings are stored in the 
MarshallerContextImpl$allCaches[platformId] map.
My understanding is according to the existing implementations it is expected 
the mapping will always be registered when BinaryContext#descriptorForClass() 
-> MarshallerContextImpl#registerClassName(typeId) is called either from 
BinaryWriterExImpl or BinaryReaderExImpl.
However, that mechanism is never called when 
CacheJdbcPojoStore@buildBinaryObject builds the object, calling 
BinaryObjectBuilderImpl#build(). The latter method still requests 
BinaryContext#updateMetadata, which updates 
CacheObjectBinaryProcessorImpl#metadataFileStore on all server nodes. But the 
metadataFileStore is not the place where MarshallerContextImpl get mappings 
from.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5970) Ignite Binary Objects Simple Mapper Basic: Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5970:
--

 Summary: Ignite Binary Objects Simple Mapper Basic: Flaky failure 
of 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
 Key: IGNITE-5970
 URL: https://issues.apache.org/jira/browse/IGNITE-5970
 Project: Ignite
  Issue Type: Test
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


Can't reproduce locally on Win 10.
On TC test has 50% success rate.
{noformat}
org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not deployed: 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
at 
org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5974) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSemaphore

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5974:
-

 Summary: [Test Failed] 
IgniteClientDiscoveryDataStructuresTest.testSemaphore
 Key: IGNITE-5974
 URL: https://issues.apache.org/jira/browse/IGNITE-5974
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=755824=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-6847798749379612181



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5973) [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5973:
-

 Summary: [Test Failed] 
GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
 Key: IGNITE-5973
 URL: https://issues.apache.org/jira/browse/IGNITE-5973
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev
 Fix For: 2.1


Success right is 93.3%. Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=757906=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-979977708202725050



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5975) [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5975:
-

 Summary: [Test Failed] 
GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure
 Key: IGNITE-5975
 URL: https://issues.apache.org/jira/browse/IGNITE-5975
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-2988875689386264427.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5976) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5976:
-

 Summary: [Test Failed]  
IgniteClientDiscoveryDataStructuresTest.testReentrantLock
 Key: IGNITE-5976
 URL: https://issues.apache.org/jira/browse/IGNITE-5976
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2381: IGNITE-5732 Provide API to test compatibility wit...

[daradurvs]

Github user daradurvs closed the pull request at:

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


---
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.
---

[GitHub] ignite pull request #2410: IGNITE-5732 Provide API to test compatibility wit...

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-5732 Provide API to test compatibility with old releases



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

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

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

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






---
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.
---

[jira] [Created] (IGNITE-5971) Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5971:
--

 Summary: Ignite Continuous Query 2: Flaky failure of 
#testMultiThreadedFailover
 Key: IGNITE-5971
 URL: https://issues.apache.org/jira/browse/IGNITE-5971
 Project: Ignite
  Issue Type: Test
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest have 
flaky #testMultiThreadedFailover test. It fails from time to time in all 
inherited test classes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5972) [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5972:
-

 Summary: [Test Failed] 
IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast
 Key: IGNITE-5972
 URL: https://issues.apache.org/jira/browse/IGNITE-5972
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev


Fails locally. Flaky one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: IgniteUtils#currentTimeMillis

[Николай Ижиков]

Addition to my previous message:

1. IgniteUtils#currentTimeMillis used in current master to check
transaction timeout:

https://github.com/apache/ignite/blob/master/modules/
core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/
IgniteTxAdapter.java#L664

2. According to jdk docs System.nanoTime() is only method to measure
elapsed time
https://docs.oracle.com/javase/7/docs/api/java/lang/System.html#nanoTime().

"This method can only be used to measure elapsed time and is not related to
any other notion of system or wall-clock time"

What are reasons to use System.currentTimeMillis() in the way it used for
now?


2017-08-07 18:42 GMT+03:00 Николай Ижиков :

> Hello, Igniters.
>
> I found unusual implementation of IgniteUtils#currentTimeMillis function.
> Method is not simple proxy to System.currentTimeMillis
> Instead it read static variable which updated by dedicated thread:
>
> https://github.com/apache/ignite/blob/master/modules/
> core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java#L3251
>
> while (true) {
> curTimeMillis = System.currentTimeMillis();
>
> try {
> Thread.sleep(10);
> }
> catch (InterruptedException ignored) {
> break;
> }
> }
>
> As far as i know `Thread.sleep` is unprecise function especially under
> heavy load and on small timeout values like 10 ms.
> Seems that we get very unprecise values of currentTimeMillis.
>
> I think that can lead to difficult bugs like https://issues.apache.
> org/jira/browse/IGNITE-5963
>
> What is purpose of current implementation?
>
> --
> Nikolay Izhikov
> nizhikov@gmail.com
>



-- 
Nikolay Izhikov
nizhikov@gmail.com

[jira] [Created] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5977:
-

 Summary: [Test Failed]  
IgniteClientDiscoveryDataStructuresTest.testSequence
 Key: IGNITE-5977
 URL: https://issues.apache.org/jira/browse/IGNITE-5977
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)