[jira] [Created] (IGNITE-12541) Ignite BTL: Does not work as expected for a cluster of mix nodes (nodes with & without persistence)

[Ashish Bhosle (Jira)]

Ashish Bhosle created IGNITE-12541:
--

 Summary: Ignite BTL: Does not work as expected for a cluster of 
mix nodes (nodes with & without persistence)
 Key: IGNITE-12541
 URL: https://issues.apache.org/jira/browse/IGNITE-12541
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7.6
Reporter: Ashish Bhosle


I have three server node. Two of them with data-node attribute and remaining 
one with worker-node attribute. Persistence is enabled on data-nodes. Below are 
some of the cases:

Case 1: Exception occurs on worker node and the node get killed
Steps:
    -start data node
    -worker node
    -start data node
    -activate the cluster by client node (or by control script)

PF all nodes' logs 
[here|[https://gist.github.com/ashishb888/4afe60c681befd0e167ee280d3625521]]


Case 2: All nodes comes under baseline topology instead of 2 nodes (data nodes)
Steps:
    -worker node
    -start data node
    -start data node
    -activate the cluster by client node (or by control script)

Here is a reproducer:

[Client 
node|[https://github.com/ashishb888/ignite-poc/tree/master/ignite-persistence]]
[Data 
node|[https://github.com/ashishb888/ignite-poc/tree/master/ignite-persistence-data-node]]
[Worker 
node|[https://github.com/ashishb888/ignite-poc/tree/master/ignite-persistence-worker-node]]

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Incorrect fillFactor/memory usage metric

[Alex Plehanov]

Hello Colin,

AFAIK fill factor doesn't take into account reuse bucket by design, it's
not a bug.
To calculate memory consumption you can also use metric totalUsedPages
which take into account the reuse bucket (but doesn't take into account
free-list fill factor) This metric was introduced in Ignite 2.8 and hasn't
released yet.
.

вт, 14 янв. 2020 г. в 19:44, coliin :

> Regarding the below issue, which causes incorrect memory consumption metric
> in Ignite 2.7+ and related GG versions:
>
> https://issues.apache.org/jira/browse/IGNITE-12096
>
> As reported in the jira comment, this appears to be caused by failure to
> account for pages that are flagged for reuse - the FreeList REUSE_BUCKET is
> not counted when determining freeSpace.
>
> Is anyone able to comment on whether there is a good reason for not doing
> so? If there isn't then the issue is simple to fix.
>
> Regards,
> Colin.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[MTCGA]: new failures in builds [4928305] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New test failure in master 
GridManagerStopSelfTest.testStopCollisionManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=881612020023396=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopCheckpointManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4020074597629404611=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopDeploymentManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5717072216521686900=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopEventStorageManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7512696684099823959=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopDiscoveryManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2397182983684241664=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopCommunicationManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1880295835506842657=%3Cdefault%3E=testDetails

 *New test failure in master GridFutureAdapterSelfTest.testListenNotify 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5696906784744075001=%3Cdefault%3E=testDetails

 *New test failure in master GridPortProcessorSelfTest.testA 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3043758622014078312=%3Cdefault%3E=testDetails

 *New test failure in master GridPortProcessorSelfTest.testB 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6926532014524804389=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopLoadBalancingManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6725252410873093912=%3Cdefault%3E=testDetails

 *New test failure in master 
GridManagerStopSelfTest.testStopFailoverManager 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2492019339754081102=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - ivan bessonov  
https://ci.ignite.apache.org/viewModification.html?modId=895469

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 07:03:39 15-01-2020 

[MTCGA]: new failures in builds [4928307] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New test failure in master 
GridTimeoutProcessorSelfTest.testTimeoutNeverCalledMultithreaded 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6234414564355764510=%3Cdefault%3E=testDetails

 *New test failure in master 
GridTimeoutProcessorSelfTest.testTimeoutSameEndTime 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9190131626312456202=%3Cdefault%3E=testDetails

 *New test failure in master 
GridTimeoutProcessorSelfTest.testCancelingWithClearedInterruptedFlag 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1165923955847622821=%3Cdefault%3E=testDetails

 *New test failure in master 
GridTimeoutProcessorSelfTest.testTimeoutObjectAdapterMultithreaded 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1987065694168745962=%3Cdefault%3E=testDetails

 *New test failure in master 
GridTimeoutProcessorSelfTest.testTimeoutsMultithreaded 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8403345957621788966=%3Cdefault%3E=testDetails

 *New test failure in master 
GridTimeoutProcessorSelfTest.testTimeoutNeverCalled 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=565451096496967=%3Cdefault%3E=testDetails

 *New test failure in master 
GridTimeoutProcessorSelfTest.testTimeoutCallOnce 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=311778530894010126=%3Cdefault%3E=testDetails

 *New test failure in master GridTimeoutProcessorSelfTest.testTimeouts 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4357043967750785732=%3Cdefault%3E=testDetails

 *New test failure in master 
GridJobMetricsProcessorLoadTest.testJobMetricsMultiThreaded 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4110404458286024408=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - ivan bessonov  
https://ci.ignite.apache.org/viewModification.html?modId=895469

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 06:33:41 15-01-2020 

Re: Ignite-spring-boot-autoconfigurer

[Denis Magda]

Nikolay,

Thanks for contributing in this direction! That's one of the gaps on our
end and the user community will be certainly thankful once we fill it in.

*Alexey Kuznetsov*, as one of the Spring Boot experts, could you spend some
time reviewing the changes?

As for the extensions/modularization activities, please join Saikat in the
discussions ([1] and [2]). He is contributing the foundation and moving our
existing integrations to that new repository. The Spring Boot improvements
might be moved or, another option, we might add this class to the core?

[1]
http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12361-Migrate-Flume-module-to-ignite-extensions-td45010.html
[2]
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-td44064.html

-
Denis


On Sat, Jan 11, 2020 at 10:44 AM Николай Ижиков  wrote:

> Hello, Igniters.
>
> During Ignite meetup I took part in there was a request from the users.
> They propose to create a custom spring boot autoconfigurer module for
> Ignite.
> This module should provide a smooth injection of Ignite to any spring-boot
> application.
>
> I've implemented a tiny straightforward prototype of the module [1]
> Examples of the usage of integration can be found in the example
> application [2]
>
> For now, the module provides the following features:
>
> 1. Starts Ignite node and inject it in the spring ApplicationContext if
> bean of the type IgniteConfiguration exists in the context.
> This can be achieved in two ways:
> * create `IgniteConfiguration` from java code [3]
> * add `ignite.xml` file to the application context [4]
>
> 2. Starts IgniteClient instance and injects it int the spring Application
> if:
> * ClientConfiguration bean exists in the context [5]
> * `spring.data.ignite.clientAddresses` exists in the application
> properties. [6]
>
> I have a following questions regards new module:
>
> 1. We have an extension initiative so where is the right place for the
> new module?
> 2. Do we have spring experts in the community? What other features for
> this autoconfigurer module required?
>
> [1] https://github.com/apache/ignite/pull/7237/files
> [2] https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example
> [3]
> https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example/tree/master/src/main/java/org/apache/ignite/spring/boot/configfrombean
> [4]
> https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example/tree/master/src/main/java/org/apache/ignite/spring/boot/configfromfile
> [5]
> https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example/tree/master/src/main/java/org/apache/ignite/spring/boot/thinclientfrombean
> [6]
> https://github.com/nizhikov/ignite-spring-boot-autoconfigure-example/tree/master/src/main/java/org/apache/ignite/spring/boot/thinclientfromconfig
>
>

Re: AWS EBS Discovery: Contributor Wanted

[Denis Magda]

Hi Emmanouil,

Agree, let's check that the IP finder functions normally in the cloud
environment and the mock tests can be used for regular testing on Team
City. That's the way we tested other environment-specific IP finders
including the Kubernetes one.

Let us know once the IP finder is tested on AWS and then we can proceed
with the review.

-
Denis


On Tue, Jan 14, 2020 at 2:47 AM Emmanouil Gkatziouras 
wrote:

> Hi all!
>
> With regards to the `Node Discovery Using AWS Application ELB` issue [1]
> I made this pull request to fix the merge conflicts [2].
> Will also check if the concerns described on the mailing list topic
> `Volunteer needed: AWS Elastic Load Balancer IP Finders implemented` are
> addressed [3]
> Since I did not test it on an AWS infrastructure the next step would be to
> spin up some AWS resources and test it.
> By doing so it will help me on checking the Amazon S3 Based Discovery issue
> [4] .
> I will try to make the deployment as infrastructure as code, and see if
> this can be of value for the ignite project and testing.
>
> Kind regards,
> Emmanouil
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8617
> [2]  https://github.com/apache/ignite/pull/7247
> [3]
>
> http://apache-ignite-developers.2346864.n4.nabble.com/Volunteer-needed-AWS-Elastic-Load-Balancer-IP-Finders-implemented-td33847.html#a39793
> [4] https://issues.apache.org/jira/browse/IGNITE-12398
>
> >
>

Re: Hint for user that baseline topology should be changed in order to trigger rebalance

[Artem Budnikov]

Hi everyone,

I think a link to the documentation is unnecessary. We could simply 
mention "baseline topology", and users will be able to find what it is 
in the docs.


Artem Budnikov
Technical Writer
gridgain.com

On 13.01.2020 21:15, Denis Magda wrote:

Stan,

I would not suggest us adding any links to docs as long as the message 
needs to be self-explanatory. If someone doesn't get it then they 
should google. Taking your feedback into consideration:


"New server node joined the cluster, add it to the baseline topology 
to store data there  [[topVer=2, minorTopVer=0], force=false, 
evt=NODE_JOINED, node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]


*Artem*, could you share your thoughts on this? *Ivan*, what's your 
thinking?


-
Denis


On Mon, Jan 13, 2020 at 5:27 AM Stanislav Lukyanov 
mailto:stanlukya...@gmail.com>> wrote:


We already have a ticket for this open BTW:
https://issues.apache.org/jira/browse/IGNITE-8115
.

I would also avoid saying anything about rebalancing - at this
point the user may not know what it is.
This message is very clearly targeted at new users, so it is
probably wrong to assume that they know
what baseline topology or rebalancing is.

I think it's better to say something like "add it to the baseline
topology if you want it to store data. See  for details.".

Stan

> On 9 Jan 2020, at 23:28, Denis Magda mailto:dma...@apache.org>> wrote:
>
> Ivan, Igniters, thanks for starting the discussion,
>
> How about the following a bit simplified message template? It's
assumed the
> user is aware of what both rebalancing and baseline topology mean.
>
> "New server node joined the cluster, add it to the baseline topology
> manually to trigger data rebalancing [node details]"
>
> a complete message will look like this
>
> "New server node joined the cluster, add it to the baseline topology
> manually to trigger data rebalancing [[topVer=2, minorTopVer=0],
> force=false, evt=NODE_JOINED,
node=57bc10fe-1505-4e8e-9987-52c9c903c6ef]]
>
>
> -
> Denis
>
>
> On Thu, Jan 9, 2020 at 6:21 AM Ivan Rakov mailto:ivan.glu...@gmail.com>> wrote:
>
>> Folks,
>>
>> Since 2.4, Ignite cluster requires baseline topology in
persistent mode.
>> That means if user wants to scale cluster and add more nodes,
data won't be
>> redistributed among the whole node set until manual call of
>> IgniteCluster#setBaselineTopology.
>>
>> Surely this behavior is well-documented, but don't we need to
give user a
>> hint that baseline topology should be managed manually? I
think, log
>> message with something like "Current set of nodes differs from
baseline
>> topology, please call XXX in order to trigger rebalance and
redistribute
>> your data" will make the situation a bit more transparent.
>>
>> Right now we have only this message
>>
>>> [2020-01-07T19:36:45,997][INFO
>>>
>>

][exchange-worker-#39%blue-54.158.100.161%][GridCachePartitionExchangeManager]
>> Skipping
>>> rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=2,
>>> minorTopVer=0], force=false, evt=NODE_JOINED,
>> node=57bc10fe-1505-4e8e-9987-
>>> 52c9c903c6ef]
>>
>> which doesn't properly explain what's going on.
>>

[jira] [Created] (IGNITE-12540) Update versions of vulnerable dependencies

[Ilya Kasnacheev (Jira)]

Ilya Kasnacheev created IGNITE-12540:


 Summary: Update versions of vulnerable dependencies
 Key: IGNITE-12540
 URL: https://issues.apache.org/jira/browse/IGNITE-12540
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Ilya Kasnacheev






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Incorrect fillFactor/memory usage metric

[coliin]

Regarding the below issue, which causes incorrect memory consumption metric
in Ignite 2.7+ and related GG versions:

https://issues.apache.org/jira/browse/IGNITE-12096

As reported in the jira comment, this appears to be caused by failure to
account for pages that are flagged for reuse - the FreeList REUSE_BUCKET is
not counted when determining freeSpace.

Is anyone able to comment on whether there is a good reason for not doing
so? If there isn't then the issue is simple to fix.

Regards,
Colin.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Incorrect fillFactor/freeSpace metric

[coliin]

Regarding the below issue, which causes incorrect memory consumption metric
in Ignite 2.7+ and related GG versions:

https://issues.apache.org/jira/browse/IGNITE-12096

As reported in the jira comment, this appears to be caused by failure to
account for pages that are flagged for reuse - the FreeList REUSE_BUCKET is
not counted when determining freeSpace.

Is anyone able to comment on whether there is a good reason for not doing
so? If there isn't then the issue is simple to fix.

Regards,
Colin.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: New member request

[Ilya Kasnacheev]

Hello!

I have added you as a contributor of IGNITE project. You can now assign
this issue to you.

Please read
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Happy coding!

Regards,
-- 
Ilya Kasnacheev


вт, 14 янв. 2020 г. в 15:17, Philipp Masharov :

> Hello Ignite Community!
>
> My name is Philipp. I want to contribute to Apache Ignite. It seems like an
> interesting, complicated and useful project. Let me start with this issue -
> IGNITE-8115, my JIRA username fi1ipx. Any help on this will be appreciated.
>
> Have a fantastic day! Thanks!
>

[jira] [Created] (IGNITE-12539) JAVADOC broken for hibernate 5.3 module

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-12539:


 Summary: JAVADOC broken for hibernate 5.3 module
 Key: IGNITE-12539
 URL: https://issues.apache.org/jira/browse/IGNITE-12539
 Project: Ignite
  Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
 Fix For: 2.8


{code}
[17:02:15]W: [Step 2/2] [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run 
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException 
has occured: Execution failed due to: Class doesn't have description in file: 
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteCollectionDataAccess.html
[17:02:15]W: [Step 2/2] [ERROR] Class doesn't have description in file: 
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteDomainDataRegion.html
[17:02:15]W: [Step 2/2] [ERROR] Class doesn't have description in file: 
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteEntityDataAccess.html
[17:02:15]W: [Step 2/2] [ERROR] Class doesn't have description in file: 
/opt/buildagent/work/7bc1c54bc719b67c/target/javadoc/core/org/apache/ignite/cache/hibernate/IgniteNaturalIdDataAccess.html
[17:02:15]W: [Step 2/2] [ERROR] 
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12538) GridAffinityAssignmentV2 can return modifiable collection in some cases.

[Andrey Mashenkov (Jira)]

Andrey Mashenkov created IGNITE-12538:
-

 Summary: GridAffinityAssignmentV2 can return modifiable collection 
in some cases.
 Key: IGNITE-12538
 URL: https://issues.apache.org/jira/browse/IGNITE-12538
 Project: Ignite
  Issue Type: Task
Reporter: Andrey Mashenkov


GridAffinityAssignmentV2.nodes() and 
GridAffinityAssignmentV2.primaryPartitionNodes() methods can return modifiable 
collections.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12537) Util DbH2ServerStartup failed

[Taras Ledkov (Jira)]

Taras Ledkov created IGNITE-12537:
-

 Summary: Util DbH2ServerStartup failed
 Key: IGNITE-12537
 URL: https://issues.apache.org/jira/browse/IGNITE-12537
 Project: Ignite
  Issue Type: Bug
  Components: examples
Affects Versions: 2.7
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.8


{{DbH2ServerStartup}} fails with exception:

{code:java}Exception in thread "main" class org.apache.ignite.IgniteException: 
Failed to start database TCP server
at 
org.apache.ignite.examples.util.DbH2ServerStartup.main(DbH2ServerStartup.java:86)
Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: Database 
"mem:ExampleDb" not found, and IFEXISTS=true, so we cant auto-create it 
[90146-199]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:617)
at org.h2.message.DbException.getJdbcSQLException(DbException.java:427)
at org.h2.message.DbException.get(DbException.java:205)
at org.h2.message.DbException.get(DbException.java:181)
at org.h2.engine.Engine.openSession(Engine.java:67)
at org.h2.engine.Engine.openSession(Engine.java:201)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:178)
at org.h2.engine.Engine.createSession(Engine.java:161)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:160)
at java.lang.Thread.run(Thread.java:748)

at org.h2.message.DbException.getJdbcSQLException(DbException.java:617)
at org.h2.engine.SessionRemote.done(SessionRemote.java:607)
at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:143)
at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:431)
at 
org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:317)
at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:169)
at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:148)
at org.h2.Driver.connect(Driver.java:69)
at 
org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:189)
at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:352)
at 
org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:384)
at 
org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:234)
at 
org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:199)
at 
org.apache.ignite.examples.util.DbH2ServerStartup.populateDatabase(DbH2ServerStartup.java:56)
at 
org.apache.ignite.examples.util.DbH2ServerStartup.main(DbH2ServerStartup.java:74){code}

This issue blocks all store examples



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12536) Inconsistency between cache data and indexes when cache operation is interrupted

[Taras Ledkov (Jira)]

Taras Ledkov created IGNITE-12536:
-

 Summary: Inconsistency between cache data and indexes when cache 
operation is interrupted
 Key: IGNITE-12536
 URL: https://issues.apache.org/jira/browse/IGNITE-12536
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.7
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.8


*Root cause:*
Inconsistency between cache and indexes happens when cache operation put/remove 
is interrupted (e.g. thread is interrupted). The cache operation is finished, 
GridH2Table#lock(boolean) }} is interrupted because {{Lock#lockInterruptibly is 
used.

*Possible fix:*
Use not interruptible lock for cache operation and interruptible lock for SQL 
operation.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

New member request

[Philipp Masharov]

Hello Ignite Community!

My name is Philipp. I want to contribute to Apache Ignite. It seems like an
interesting, complicated and useful project. Let me start with this issue -
IGNITE-8115, my JIRA username fi1ipx. Any help on this will be appreciated.

Have a fantastic day! Thanks!

[jira] [Created] (IGNITE-12535) Jdbc Thin: Pass custom CipherSuites to JDBC thin client.

[Andrey Mashenkov (Jira)]

Andrey Mashenkov created IGNITE-12535:
-

 Summary: Jdbc Thin: Pass custom CipherSuites to JDBC thin client.
 Key: IGNITE-12535
 URL: https://issues.apache.org/jira/browse/IGNITE-12535
 Project: Ignite
  Issue Type: Task
  Components: thin client
Reporter: Andrey Mashenkov
 Fix For: 2.9


We widely own Ignite SSL Factory implementation and allow (e.g. control.sh 
tool) to pass cipher suites in most cases, but ThinClient.

Let's allow user to restrict cipher suites for ThinClient as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: How to use spark-2.4 module in Ignite 2.8?

[Alexey Zinoviev]

I've fixed this issue in master and release branch, it works locally on my
machine well
https://issues.apache.org/jira/browse/IGNITE-12534



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-12534) [Spark] The spark 2.4 is not found in optional folder

[Alexey Zinoviev (Jira)]

Alexey Zinoviev created IGNITE-12534:


 Summary: [Spark] The spark 2.4 is not found in optional folder
 Key: IGNITE-12534
 URL: https://issues.apache.org/jira/browse/IGNITE-12534
 Project: Ignite
  Issue Type: Bug
  Components: spark
Affects Versions: 2.8
Reporter: Alexey Zinoviev
Assignee: Alexey Zinoviev
 Fix For: 2.8


The bug from dev-list: 
[http://apache-ignite-developers.2346864.n4.nabble.com/Re-How-to-use-spark-2-4-module-in-Ignite-2-8-td44773.html#a45020]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: AWS EBS Discovery: Contributor Wanted

[Emmanouil Gkatziouras]

Hi all!

With regards to the `Node Discovery Using AWS Application ELB` issue [1]
I made this pull request to fix the merge conflicts [2].
Will also check if the concerns described on the mailing list topic
`Volunteer needed: AWS Elastic Load Balancer IP Finders implemented` are
addressed [3]
Since I did not test it on an AWS infrastructure the next step would be to
spin up some AWS resources and test it.
By doing so it will help me on checking the Amazon S3 Based Discovery issue
[4] .
I will try to make the deployment as infrastructure as code, and see if
this can be of value for the ignite project and testing.

Kind regards,
Emmanouil

[1] https://issues.apache.org/jira/browse/IGNITE-8617
[2]  https://github.com/apache/ignite/pull/7247
[3]
http://apache-ignite-developers.2346864.n4.nabble.com/Volunteer-needed-AWS-Elastic-Load-Balancer-IP-Finders-implemented-td33847.html#a39793
[4] https://issues.apache.org/jira/browse/IGNITE-12398

>

[jira] [Created] (IGNITE-12533) Remote security context tests refactoring.

[Denis Garus (Jira)]

Denis Garus created IGNITE-12533:


 Summary: Remote security context tests refactoring.
 Key: IGNITE-12533
 URL: https://issues.apache.org/jira/browse/IGNITE-12533
 Project: Ignite
  Issue Type: Improvement
Reporter: Denis Garus


To make tests more readable and robust, we should use the 
_AbstractRemoteSecurityContextCheckTest.Verifier#register(String)_ method in 
all related tests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Maxim Muzafarov]

Alexey,

I think yes. Otherwise, we will never finish.

On Tue, 14 Jan 2020 at 12:01, Alexey Goncharuk
 wrote:
>
> Folks,
>
> While I agree with Ivan that IGNITE-12531
>  should be fixed in
> 2.8, I also share Nikolay's concern regarding the 2.8 scope inflation.
> Should we consider fixing only blockers for 2.8.0 and moving the
> remaining tickets to a maintenance releases 2.8.1, 2.8.2, etc?
>
> --AG
>
> вт, 14 янв. 2020 г. в 11:08, Alexei Scherbakov  >:
>
> > This looks really bad.
> >
> > Let's fix it before releasing.
> >
> > пн, 13 янв. 2020 г. в 18:50, Ivan Rakov :
> >
> > > Igniters,
> > >
> > > Seems like we have another blocker for 2.8 [1].
> > > Impact: after migration of persistent cluster from 2.7- to 2.8 any
> > updates
> > > of baseline topology are not persisted.
> > >
> > > [1]: https://issues.apache.org/jira/browse/IGNITE-12531
> > >
> > > On Mon, Jan 13, 2020 at 6:14 PM Sergey Antonov <
> > antonovserge...@gmail.com>
> > > wrote:
> > >
> > > > Igniters, I got green TC Bit visas [1] [2] for patch and commit revert.
> > > >
> > > > [1]
> > > >
> > > >
> > >
> > https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7238%2Fhead=Latest
> > > >
> > > > [2]
> > > >
> > > >
> > >
> > https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7239%2Fhead=Latest
> > > >
> > > > пн, 13 янв. 2020 г., 17:51 Maxim Muzafarov :
> > > >
> > > > > Sergey,
> > > > >
> > > > > Thank you. I also do not support @IgniteExperemental annotation only
> > > > > for solving the current case of compatibility issues.
> > > > >
> > > > > I like your second suggestion to revert the issue [2] from 2.8
> > release
> > > > > by applying [1] PR. I'm going to apply this patch [1] within the next
> > > > > three days.
> > > > >
> > > > > Any objections?
> > > > >
> > > > > [1] https://github.com/apache/ignite/pull/7238
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-11256
> > > > >
> > > > > On Sat, 11 Jan 2020 at 17:59, Sergey Antonov <
> > > antonovserge...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > Guys, I created two pull requests [1] [2] for 2.8 release.
> > > > > >
> > > > > > First of them [1] is a patch with ticket [3] for ignite-2.8 branch.
> > > > > > Second [2] is a revert of ticket [4] from 2.8 release.
> > > > > >
> > > > > > I'm waiting TC run all nightly results for both PRs. I'll write
> > > update
> > > > > when
> > > > > > TC runs will be ok.
> > > > > > I'm okay with both proposals (add ticket [1] to release, remove
> > > > read-only
> > > > > > feature from 2.8 release scope). But I'm not okay with
> > > > > @IgniteExperemental
> > > > > > annotation.
> > > > > >
> > > > > > [1] https://github.com/apache/ignite/pull/7239
> > > > > > [2] https://github.com/apache/ignite/pull/7238
> > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12225
> > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-11256
> > > > > >
> > > > > >
> > > > > > пт, 10 янв. 2020 г. в 14:21, Zhenya Stanilovsky
> > > > >  > > > > > >:
> > > > > >
> > > > > > >
> > > > > > > Ivan, if i correctly understand, you suggest additional
> > > > «expiremental»
> > > > > > > stuff only for hiding already leaked RO interface ?
> > > > > > > poor approach as for me.
> > > > > > >
> > > > > > > >Folks,
> > > > > > > >
> > > > > > > >Some thoughts:
> > > > > > > >* Releasing an API with known fallacies sounds really bad thing
> > to
> > > > me.
> > > > > > > >It can have a negative consequences for a whole project for
> > years.
> > > > My
> > > > > > > >opinion here that we should resolve the problem with this API
> > > > somehow
> > > > > > > >before release.
> > > > > > > >* We can mark cluster read-only API (without enum) as
> > experimental
> > > > and
> > > > > > > >change the API in e.g. 2.8.1.
> > > > > > > >* We can try to exclude read-only API from 2.8 at all.
> > > > > > > >
> > > > > > > >What do you think?
> > > > > > > >
> > > > > > > >пт, 10 янв. 2020 г. в 11:20, Alex Plehanov <
> > > > plehanov.a...@gmail.com
> > > > > >:
> > > > > > > >>
> > > > > > > >> Guys,
> > > > > > > >>
> > > > > > > >> There is also an issue with cluster activation by thin
> > clients.
> > > > This
> > > > > > > >> feature (.NET thin client API change and protocol change) was
> > > > added
> > > > > by
> > > > > > > [1]
> > > > > > > >> without any discussion on dev-list. Sergey's patch [2]
> > deprecate
> > > > > methods
> > > > > > > >> "IgniteCluster.active(boolean)" and "IgniteCluster.active()",
> > > but
> > > > > > > didn't do
> > > > > > > >> this for thin clients. If we want to include IGNITE-12225 to
> > 2.8
> > > > we
> > > > > also
> > > > > > > >> should not forget about thin client changes, since it will be
> > > > > strange
> > > > > > > if we
> > > > > > > >> introduce some methods to thin client API and protocol and in
> > > the
> > > > > same
> > > > > > > >> Ignite 

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Alexey Goncharuk]

Folks,

While I agree with Ivan that IGNITE-12531
 should be fixed in
2.8, I also share Nikolay's concern regarding the 2.8 scope inflation.
Should we consider fixing only blockers for 2.8.0 and moving the
remaining tickets to a maintenance releases 2.8.1, 2.8.2, etc?

--AG

вт, 14 янв. 2020 г. в 11:08, Alexei Scherbakov :

> This looks really bad.
>
> Let's fix it before releasing.
>
> пн, 13 янв. 2020 г. в 18:50, Ivan Rakov :
>
> > Igniters,
> >
> > Seems like we have another blocker for 2.8 [1].
> > Impact: after migration of persistent cluster from 2.7- to 2.8 any
> updates
> > of baseline topology are not persisted.
> >
> > [1]: https://issues.apache.org/jira/browse/IGNITE-12531
> >
> > On Mon, Jan 13, 2020 at 6:14 PM Sergey Antonov <
> antonovserge...@gmail.com>
> > wrote:
> >
> > > Igniters, I got green TC Bit visas [1] [2] for patch and commit revert.
> > >
> > > [1]
> > >
> > >
> >
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7238%2Fhead=Latest
> > >
> > > [2]
> > >
> > >
> >
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7239%2Fhead=Latest
> > >
> > > пн, 13 янв. 2020 г., 17:51 Maxim Muzafarov :
> > >
> > > > Sergey,
> > > >
> > > > Thank you. I also do not support @IgniteExperemental annotation only
> > > > for solving the current case of compatibility issues.
> > > >
> > > > I like your second suggestion to revert the issue [2] from 2.8
> release
> > > > by applying [1] PR. I'm going to apply this patch [1] within the next
> > > > three days.
> > > >
> > > > Any objections?
> > > >
> > > > [1] https://github.com/apache/ignite/pull/7238
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-11256
> > > >
> > > > On Sat, 11 Jan 2020 at 17:59, Sergey Antonov <
> > antonovserge...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Guys, I created two pull requests [1] [2] for 2.8 release.
> > > > >
> > > > > First of them [1] is a patch with ticket [3] for ignite-2.8 branch.
> > > > > Second [2] is a revert of ticket [4] from 2.8 release.
> > > > >
> > > > > I'm waiting TC run all nightly results for both PRs. I'll write
> > update
> > > > when
> > > > > TC runs will be ok.
> > > > > I'm okay with both proposals (add ticket [1] to release, remove
> > > read-only
> > > > > feature from 2.8 release scope). But I'm not okay with
> > > > @IgniteExperemental
> > > > > annotation.
> > > > >
> > > > > [1] https://github.com/apache/ignite/pull/7239
> > > > > [2] https://github.com/apache/ignite/pull/7238
> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12225
> > > > > [4] https://issues.apache.org/jira/browse/IGNITE-11256
> > > > >
> > > > >
> > > > > пт, 10 янв. 2020 г. в 14:21, Zhenya Stanilovsky
> > > >  > > > > >:
> > > > >
> > > > > >
> > > > > > Ivan, if i correctly understand, you suggest additional
> > > «expiremental»
> > > > > > stuff only for hiding already leaked RO interface ?
> > > > > > poor approach as for me.
> > > > > >
> > > > > > >Folks,
> > > > > > >
> > > > > > >Some thoughts:
> > > > > > >* Releasing an API with known fallacies sounds really bad thing
> to
> > > me.
> > > > > > >It can have a negative consequences for a whole project for
> years.
> > > My
> > > > > > >opinion here that we should resolve the problem with this API
> > > somehow
> > > > > > >before release.
> > > > > > >* We can mark cluster read-only API (without enum) as
> experimental
> > > and
> > > > > > >change the API in e.g. 2.8.1.
> > > > > > >* We can try to exclude read-only API from 2.8 at all.
> > > > > > >
> > > > > > >What do you think?
> > > > > > >
> > > > > > >пт, 10 янв. 2020 г. в 11:20, Alex Plehanov <
> > > plehanov.a...@gmail.com
> > > > >:
> > > > > > >>
> > > > > > >> Guys,
> > > > > > >>
> > > > > > >> There is also an issue with cluster activation by thin
> clients.
> > > This
> > > > > > >> feature (.NET thin client API change and protocol change) was
> > > added
> > > > by
> > > > > > [1]
> > > > > > >> without any discussion on dev-list. Sergey's patch [2]
> deprecate
> > > > methods
> > > > > > >> "IgniteCluster.active(boolean)" and "IgniteCluster.active()",
> > but
> > > > > > didn't do
> > > > > > >> this for thin clients. If we want to include IGNITE-12225 to
> 2.8
> > > we
> > > > also
> > > > > > >> should not forget about thin client changes, since it will be
> > > > strange
> > > > > > if we
> > > > > > >> introduce some methods to thin client API and protocol and in
> > the
> > > > same
> > > > > > >> Ignite version deprecate these methods for servers and thick
> > > > clients.
> > > > > > >>
> > > > > > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-11709
> > > > > > >> [2]:  https://issues.apache.org/jira/browse/IGNITE-12225
> > > > > > >>
> > > > > > >>
> > > > > > >> пт, 10 янв. 2020 г. в 10:24, Zhenya Stanilovsky <
> > > > > > arzamas...@mail.ru.invalid
> > > > > > >> >:
> > > > > > >>
> > > > > > 

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Alexei Scherbakov]

This looks really bad.

Let's fix it before releasing.

пн, 13 янв. 2020 г. в 18:50, Ivan Rakov :

> Igniters,
>
> Seems like we have another blocker for 2.8 [1].
> Impact: after migration of persistent cluster from 2.7- to 2.8 any updates
> of baseline topology are not persisted.
>
> [1]: https://issues.apache.org/jira/browse/IGNITE-12531
>
> On Mon, Jan 13, 2020 at 6:14 PM Sergey Antonov 
> wrote:
>
> > Igniters, I got green TC Bit visas [1] [2] for patch and commit revert.
> >
> > [1]
> >
> >
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7238%2Fhead=Latest
> >
> > [2]
> >
> >
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAllNightly=ignite-2.8=pull%2F7239%2Fhead=Latest
> >
> > пн, 13 янв. 2020 г., 17:51 Maxim Muzafarov :
> >
> > > Sergey,
> > >
> > > Thank you. I also do not support @IgniteExperemental annotation only
> > > for solving the current case of compatibility issues.
> > >
> > > I like your second suggestion to revert the issue [2] from 2.8 release
> > > by applying [1] PR. I'm going to apply this patch [1] within the next
> > > three days.
> > >
> > > Any objections?
> > >
> > > [1] https://github.com/apache/ignite/pull/7238
> > > [2] https://issues.apache.org/jira/browse/IGNITE-11256
> > >
> > > On Sat, 11 Jan 2020 at 17:59, Sergey Antonov <
> antonovserge...@gmail.com>
> > > wrote:
> > > >
> > > > Guys, I created two pull requests [1] [2] for 2.8 release.
> > > >
> > > > First of them [1] is a patch with ticket [3] for ignite-2.8 branch.
> > > > Second [2] is a revert of ticket [4] from 2.8 release.
> > > >
> > > > I'm waiting TC run all nightly results for both PRs. I'll write
> update
> > > when
> > > > TC runs will be ok.
> > > > I'm okay with both proposals (add ticket [1] to release, remove
> > read-only
> > > > feature from 2.8 release scope). But I'm not okay with
> > > @IgniteExperemental
> > > > annotation.
> > > >
> > > > [1] https://github.com/apache/ignite/pull/7239
> > > > [2] https://github.com/apache/ignite/pull/7238
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-12225
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-11256
> > > >
> > > >
> > > > пт, 10 янв. 2020 г. в 14:21, Zhenya Stanilovsky
> > >  > > > >:
> > > >
> > > > >
> > > > > Ivan, if i correctly understand, you suggest additional
> > «expiremental»
> > > > > stuff only for hiding already leaked RO interface ?
> > > > > poor approach as for me.
> > > > >
> > > > > >Folks,
> > > > > >
> > > > > >Some thoughts:
> > > > > >* Releasing an API with known fallacies sounds really bad thing to
> > me.
> > > > > >It can have a negative consequences for a whole project for years.
> > My
> > > > > >opinion here that we should resolve the problem with this API
> > somehow
> > > > > >before release.
> > > > > >* We can mark cluster read-only API (without enum) as experimental
> > and
> > > > > >change the API in e.g. 2.8.1.
> > > > > >* We can try to exclude read-only API from 2.8 at all.
> > > > > >
> > > > > >What do you think?
> > > > > >
> > > > > >пт, 10 янв. 2020 г. в 11:20, Alex Plehanov <
> > plehanov.a...@gmail.com
> > > >:
> > > > > >>
> > > > > >> Guys,
> > > > > >>
> > > > > >> There is also an issue with cluster activation by thin clients.
> > This
> > > > > >> feature (.NET thin client API change and protocol change) was
> > added
> > > by
> > > > > [1]
> > > > > >> without any discussion on dev-list. Sergey's patch [2] deprecate
> > > methods
> > > > > >> "IgniteCluster.active(boolean)" and "IgniteCluster.active()",
> but
> > > > > didn't do
> > > > > >> this for thin clients. If we want to include IGNITE-12225 to 2.8
> > we
> > > also
> > > > > >> should not forget about thin client changes, since it will be
> > > strange
> > > > > if we
> > > > > >> introduce some methods to thin client API and protocol and in
> the
> > > same
> > > > > >> Ignite version deprecate these methods for servers and thick
> > > clients.
> > > > > >>
> > > > > >> [1]:  https://issues.apache.org/jira/browse/IGNITE-11709
> > > > > >> [2]:  https://issues.apache.org/jira/browse/IGNITE-12225
> > > > > >>
> > > > > >>
> > > > > >> пт, 10 янв. 2020 г. в 10:24, Zhenya Stanilovsky <
> > > > > arzamas...@mail.ru.invalid
> > > > > >> >:
> > > > > >>
> > > > > >> >
> > > > > >> >
> > > > > >> > Agree with Nikolay, -1 from me, too.
> > > > > >> >
> > > > > >> > >Hello, Igniters.
> > > > > >> > >
> > > > > >> > >I’m -1 to include the read-only patch to 2.8.
> > > > > >> > >I think we shouldn’t accept any patches to 2.8 except bug
> fixes
> > > for
> > > > > >> > blockers and major issues.
> > > > > >> > >
> > > > > >> > >Guys, we don’t release Apache Ignite for 13 months!
> > > > > >> > >We should focus on the release and make it ASAP.
> > > > > >> > >
> > > > > >> > >We can’t extend the scope anymore.
> > > > > >> > >
> > > > > >> > >> 10 янв. 2020 г., в 04:29, Sergey Antonov <
> > > > > antonovserge...@gmail.com >
> > > > > >> > написал(а):
>