[jira] [Assigned] (IGNITE-8550) CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also return 2 or 0

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan reassigned IGNITE-8550:
-

Assignee: Vladimir Ozerov

> CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also 
> return 2 or 0
> 
>
> Key: IGNITE-8550
> URL: https://issues.apache.org/jira/browse/IGNITE-8550
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Stanislav Lukyanov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.6
>
>
> CacheAbstractJdbcStore.write attempts to execute a merge update if it is 
> available, and expects the merge to always return 1 (as the number of updated 
> entries is always 1).
> However, MySQL's `INSERT ... ON DUPLICATE KEY UPDATE` 
> (https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html) may return 
> 0 or 2, depending on what was updated:
> {quote}With ON DUPLICATE KEY UPDATE, the affected-rows value per row is 1 if 
> the row is inserted as a new row, 2 if an existing row is updated, and 0 if 
> an existing row is set to its current values.{quote}
> Because of that, CacheAbstractJdbcStore may report a false warning.
> Need to consider either removing the warning or special-case the MySQL 
> dialect to allow to return values other than 1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8550) CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also return 2 or 0

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-8550:
--
Fix Version/s: 2.6

> CacheAbstractJdbcStore expects merge to always return 1 but MySQL may also 
> return 2 or 0
> 
>
> Key: IGNITE-8550
> URL: https://issues.apache.org/jira/browse/IGNITE-8550
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Stanislav Lukyanov
>Priority: Minor
> Fix For: 2.6
>
>
> CacheAbstractJdbcStore.write attempts to execute a merge update if it is 
> available, and expects the merge to always return 1 (as the number of updated 
> entries is always 1).
> However, MySQL's `INSERT ... ON DUPLICATE KEY UPDATE` 
> (https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html) may return 
> 0 or 2, depending on what was updated:
> {quote}With ON DUPLICATE KEY UPDATE, the affected-rows value per row is 1 if 
> the row is inserted as a new row, 2 if an existing row is updated, and 0 if 
> an existing row is set to its current values.{quote}
> Because of that, CacheAbstractJdbcStore may report a false warning.
> Need to consider either removing the warning or special-case the MySQL 
> dialect to allow to return values other than 1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8552) Unable to use date as primary key

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan reassigned IGNITE-8552:
-

Assignee: Vladimir Ozerov

> Unable to use date as primary key
> -
>
> Key: IGNITE-8552
> URL: https://issues.apache.org/jira/browse/IGNITE-8552
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.6
>
>
> It' is unable to create cache via ddl:
> create table tab(id date primary key, date_field date);
> Result:
> ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to 
> rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in 
> the node classpath (use default marshaller to enable binary objects) : 
> SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
>   at 
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8552) Unable to use date as primary key

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-8552:
--
Fix Version/s: 2.6

> Unable to use date as primary key
> -
>
> Key: IGNITE-8552
> URL: https://issues.apache.org/jira/browse/IGNITE-8552
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Priority: Major
> Fix For: 2.6
>
>
> It' is unable to create cache via ddl:
> create table tab(id date primary key, date_field date);
> Result:
> ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to 
> rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in 
> the node classpath (use default marshaller to enable binary objects) : 
> SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
>   at 
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8552) Unable to use date as primary key

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-8552:
--
Priority: Blocker  (was: Major)

> Unable to use date as primary key
> -
>
> Key: IGNITE-8552
> URL: https://issues.apache.org/jira/browse/IGNITE-8552
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Priority: Blocker
> Fix For: 2.6
>
>
> It' is unable to create cache via ddl:
> create table tab(id date primary key, date_field date);
> Result:
> ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to 
> rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in 
> the node classpath (use default marshaller to enable binary objects) : 
> SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
>   at 
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-4958) Make data pages recyclable into index/meta/etc pages and vice versa

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4958:


Github user asfgit closed the pull request at:

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


> Make data pages recyclable into index/meta/etc pages and vice versa
> ---
>
> Key: IGNITE-4958
> URL: https://issues.apache.org/jira/browse/IGNITE-4958
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Ivan Rakov
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> Recycling for data pages is disabled for now. Empty data pages are 
> accumulated in FreeListImpl#emptyDataPagesBucket, and can be reused only as 
> data pages again. What has to be done:
> * Empty data pages should be recycled into reuse bucket
> * We should check reuse bucket first before allocating a new data page
> * MemoryPolicyConfiguration#emptyPagesPoolSize should be removed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-4958) Make data pages recyclable into index/meta/etc pages and vice versa

[Ivan Rakov (JIRA)]

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

Ivan Rakov commented on IGNITE-4958:


[~cyberdemon], thanks for your contribution!
Merged to master.

> Make data pages recyclable into index/meta/etc pages and vice versa
> ---
>
> Key: IGNITE-4958
> URL: https://issues.apache.org/jira/browse/IGNITE-4958
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Ivan Rakov
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> Recycling for data pages is disabled for now. Empty data pages are 
> accumulated in FreeListImpl#emptyDataPagesBucket, and can be reused only as 
> data pages again. What has to be done:
> * Empty data pages should be recycled into reuse bucket
> * We should check reuse bucket first before allocating a new data page
> * MemoryPolicyConfiguration#emptyPagesPoolSize should be removed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8460) Document JDBC thin driver DataSource

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-8460:
---

Assignee: Taras Ledkov  (was: Denis Magda)

> Document JDBC thin driver DataSource
> 
>
> Key: IGNITE-8460
> URL: https://issues.apache.org/jira/browse/IGNITE-8460
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, jdbc
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8460) Document JDBC thin driver DataSource

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-8460:
-

[~tledkov-gridgain], thanks, I've reviewed the docs. As for the DataSource 
section, first, agree, let's put a link to Javadoc but I would use the "latest" 
one so that we don't need to update the reference with every release. Second, 
could you write a short paragraph explaining what are the benefits of using the 
DataSource approach?

> Document JDBC thin driver DataSource
> 
>
> Key: IGNITE-8460
> URL: https://issues.apache.org/jira/browse/IGNITE-8460
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, jdbc
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.5
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8590) Overridden members in descendant classes can cause BinaryMarshaller exceptions

[Raymond Wilson (JIRA)]

Raymond Wilson created IGNITE-8590:
--

 Summary: Overridden members in descendant classes can cause 
BinaryMarshaller exceptions
 Key: IGNITE-8590
 URL: https://issues.apache.org/jira/browse/IGNITE-8590
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.4
 Environment: Apache Ignite 2.4 using .Net client with .Net Standard 
artifacts.
Reporter: Raymond Wilson


If you define a pair of classes, one descended from the other, with an 
overridden field, the Ignite binary marshaller throws the exception shown 
below. 

 

public class A

{

public int Filters;

}

 

public class B : A

{

public int Filters;

}

 

This code compiles (with a warning about an overridden field that does not use 
the C# 'new' annotation) and runs, but produces this exception if class B is 
supplied to an Ignite Compute function as an argument.

 

2018-05-22 13:40:50,523 [13] ERROR PlanViewTileRenderer. ExecutePipeline raised 
exception System.AggregateException: One or more errors occurred. ---> 
Apache.Ignite.Core.Binary.BinaryObjectException: Conflicting field IDs 
[type=SubGridsRequestArgument, field1=Filters, field2=Filters, 
fieldId=-854547461]

   at 
Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type 
type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper, 
Boolean forceTimestamp)

   at 
Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration 
cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId, 
IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type, Int32 
typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type, 
BinaryFullTypeDescriptor desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at 
Apache.Ignite.Core.Impl.Deployment.PeerLoadingExtensions.WriteWithPeerDeployment(BinaryWriter
 writer, Object o)

   at 
Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1 
obj, BinaryWriter writer)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at 
Apache.Ignite.Core.Impl.Binary.BinarySystemTypeSerializer`1.WriteBinary[T1](T1 
obj, BinaryWriter writer)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.Write[T](T obj)

   at Apache.Ignite.Core.Impl.Binary.BinaryWriter.WriteObjectDetached[T](T o)

   at Apache.Ignite.Core.Impl.Compute.ComputeImpl.WriteJob(IComputeJob job, 
BinaryWriter writer)

   at 
Apache.Ignite.Core.Impl.Compute.ComputeImpl.<>c__DisplayClass1d`3.b__1a(BinaryWriter
 writer)

   at Apache.Ignite.Core.Impl.PlatformTargetAdapter.WriteToStream(Action`1 
action, IBinaryStream stream, Marshaller marsh)

   at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutObject(Int32 type, 
Action`1 writeAction)

   at 
Apache.Ignite.Core.Impl.Compute.ComputeImpl.ExecuteClosures0[TArg,TJobRes,TReduceRes](IComputeTask`3
 task, IComputeJob job, IEnumerable`1 jobs, Int32 opId, Int32 jobsCount, 
Action`1 writeAction)

   --- End of inner exception stack trace ---

   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean 
includeTaskCanceledExceptions)

   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, 
CancellationToken cancellationToken)

   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout)

   at VSS.TRex.GridFabric.Requests.SubGridRequestsProgressive`2.Execute() in 
C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\GridFabric\Requests\SubGridRequestsProgressive.cs:line
 107

   at VSS.TRex.Pipelines.SubGridPipelineBase`3.Initiate() in 
C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Pipelines\SubGridPipelineBase.cs:line
 241

   at VSS.TRex.Rendering.PlanViewTileRenderer.ExecutePipeline() in 
C:\Dev\VSS.TRex\src\netstandard\RaptorClassLibrary.netstandard\Rendering\PlanViewTileRenderer.cs:line
 262

---> (Inner Exception #0) Apache.Ignite.Core.Binary.BinaryObjectException: 
Conflicting field IDs [type=SubGridsRequestArgument, field1=Filters, 
field2=Filters, fieldId=-854547461]

   at 
Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Register(Type 
type, Int32 typeId, IBinaryNameMapper converter, IBinaryIdMapper idMapper, 
Boolean forceTimestamp)

   at 
Apache.Ignite.Core.Impl.Binary.Marshaller.GetSerializer(BinaryConfiguration 
cfg, BinaryTypeConfiguration typeCfg, Type type, Int32 typeId, 
IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, ILogger log)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(Type type, Int32 
typeId, String typeName, Boolean registered, BinaryFullTypeDescriptor desc)

   at Apache.Ignite.Core.Impl.Binary.Marshaller.RegisterType(Type type, 

[jira] [Commented] (IGNITE-8039) Binary Client Protocol spec: data types/format clarifications

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-8039:
-

[~isapego], [~vozerov]

The below text is from the "Schema" section on the Data Format page - 
https://apacheignite.readme.io/v2.4/docs/data-format#section-schema

"_There are two formats of schema supported. The first one is harder to 
implement, and is called "Compact footer", while the second one is simpler to 
implement but uses more resources. You can find more details on both formats 
below._

_It is highly recommended for clients to support "Compact footer". The flag 
{{COMPACT_FOOTER}}should be checked by clients to determine, which approach is 
used in every specific object._"

Here, you have mentioned that "Compact footer" is hard to implement, but at the 
same time you are recommending to use it. This is a bit confusing.

Also, what is the second format called?

Can you please rephrase the above section to make things clearer?

> Binary Client Protocol spec: data types/format clarifications
> -
>
> Key: IGNITE-8039
> URL: https://issues.apache.org/jira/browse/IGNITE-8039
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation, thin client
>Affects Versions: 2.4
>Reporter: Alexey Kosenchuk
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
>
> Assuming the Binary Client Protocol spec should be detalized enough to allow 
> a client development basing on the spec only, w/o looking at other client 
> implementations and asking additional questions...
> The following should be clarified / corrected in the Binary Client Protocol 
> spec (v.2.4) 
> (https://apacheignite.readme.io/v2.4/docs/binary-client-protocol#section-data-format):
> Type Codes table:
> -
> - UUID (Guid) size: should be 16 bytes, not 8 (?) 
> - what is Object array (type code 23) ? What is the difference between it and 
> Objects Wrapped In​ Array (type code 27) ?
> - what is Collection USER_SET ?
> - what is Collection USER_COL ?
> - what is Collection SINGLETON_LIST ?
> - Collection: misprint: should be "... + length ..."
> - what is Decimal ?
> - what is Timestamp ?
> - what is Time ?
> Complex Objects:
> 
> - what does flag USER_TYPE mean ?
> - Schema "field Id; Java-style hash code of field" -> should be "... of field 
> name".
> - "Repeat for as many times as the total number of schemas you have" -> 
> should be "... total number of fields you have".
> - is it mandated that the number of fields in the Schema must be equal to the 
> number of fields in the Data Object ?
> Objects Wrapped In​ Array
> 
> - may binary objects with different type codes be in the same array ?
> - may complex objects with different type ids be in the same array ?
> - "All cache operations return complex objects inside a wrapper (but not 
> primitives)." -> does it mean that in general a complex object (103) must 
> always be sent via the Binary Protocol in a wrapper (27)? 
> - "Byte array size" -> "Payload size" or "Size of the whole array with 
> header" ?
> - Offset. What is "object graph" here ? The Binary Protocol nowhere describes 
> any relations ("graph") between data objects in the protocol.
> Terminology
> ---
> Not critical but would be really convenient to define and use the same terms 
> along the whole spec. For example:
> - "binary object" is always the same as "data object" of any type (?). Can be 
> "standard/predefined type object" or "complex object".
> - "cluster" or "server" ?
> - "cluster member" or "server nodes" ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8589) Prepare Node.JS Thin Client documentation

[Denis Magda (JIRA)]

Denis Magda created IGNITE-8589:
---

 Summary: Prepare Node.JS Thin Client documentation
 Key: IGNITE-8589
 URL: https://issues.apache.org/jira/browse/IGNITE-8589
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
Assignee: Pavel Petroshenko
 Fix For: 2.6


The hidden page is presently here:
https://apacheignite.readme.io/v2.4/docs/nodejs-thin-client

Once all the suggestions are resolved, we might split this page into several 
pages. I can do this closer to 2.6 release.

[~pavel.petroshenko], [~alexey.kosenchuk], please address the following 
suggestions for now:

Installation section:
* Ignite repository has to be used instead of the private one
* The section needs to explain the installation steps once the NPM module is 
released. It's fine to put the current installation instructions under 
"Installing from Sources" section.

Data Types:
* The term "field" is truly confusing. Does it really imply any possible data 
(value, key, element of an array)? Why can't we use the term "value" instead?
* Provide a code snippet that shows how to configure the explicit mapping
* Default mapping has to be documented in place on readme.io (no references to 
the private GIT repo)

Configuring Ignite Client
*Failover on a reconnect code snippet. How to pass a list of the endpoints.

General:
* You use CacheClient or just Cache notion to refer to an instance of the cache 
class. Let's use one term. I prefer the Cache one or IgniteCache if it's named 
this way.
* Add a reference to the examples once they are merged to Ignite repo (see the 
latest section on the readme page)
* Add a reference to Node.JS APIs within supported APIs section.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8588) .NET: Serialization issue when derived type hides base type member

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-8588:
---
Labels: .NET  (was: )

> .NET: Serialization issue when derived type hides base type member
> --
>
> Key: IGNITE-8588
> URL: https://issues.apache.org/jira/browse/IGNITE-8588
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
>
> The following class structure causes an exception that is hard to understand 
> (when putting instance of B into Ignite cache):
> {code}
> public class A
> {
>   public int bob;
> } 
> public class B : A
> {
>   public int bob;
> }
> {code}
> See user list thread for more details:
> http://apache-ignite-users.70518.x6.nabble.com/Binary-type-has-different-fields-error-td21540.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8588) .NET: Serialization issue when derived type hides base type member

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-8588:
--

 Summary: .NET: Serialization issue when derived type hides base 
type member
 Key: IGNITE-8588
 URL: https://issues.apache.org/jira/browse/IGNITE-8588
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


The following class structure causes an exception that is hard to understand 
(when putting instance of B into Ignite cache):

{code}
public class A
{
  public int bob;
} 

public class B : A
{
  public int bob;
}
{code}

See user list thread for more details:
http://apache-ignite-users.70518.x6.nabble.com/Binary-type-has-different-fields-error-td21540.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8584) Provide ability to terminate any thread with enabled test features

[Dmitriy Sorokin (JIRA)]

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

Dmitriy Sorokin commented on IGNITE-8584:
-

[~agura], review my patch, please!

> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> We already have {{WorkersControlMXBean}} that provides possibility to 
> interrupt thread registered in system workers registry. We also want stop any 
> thread in the system for testing purposes.
> Method {{stop(String threadName)}} should be added that have to find thread 
> by name and stop it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8584) Provide ability to terminate any thread with enabled test features

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8584:


GitHub user x-kreator opened a pull request:

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

IGNITE-8584: Provide ability to terminate any thread with enabled tes…

…t features.

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

$ git pull https://github.com/x-kreator/ignite ignite-8584

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

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


commit 7c0cd0e08a0460982a392c96bbfe02353ec35227
Author: Dmitriy Sorokin 
Date:   2018-05-23T18:24:24Z

IGNITE-8584: Provide ability to terminate any thread with enabled test 
features.




> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> We already have {{WorkersControlMXBean}} that provides possibility to 
> interrupt thread registered in system workers registry. We also want stop any 
> thread in the system for testing purposes.
> Method {{stop(String threadName)}} should be added that have to find thread 
> by name and stop it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8530) Exchange hangs during start/stop stress test

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-8530:
--
Fix Version/s: 2.6

> Exchange hangs during start/stop stress test
> 
>
> Key: IGNITE-8530
> URL: https://issues.apache.org/jira/browse/IGNITE-8530
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.4
>Reporter: Mikhail Cherkasov
>Assignee: Anton Kalashnikov
>Priority: Blocker
> Fix For: 2.6
>
> Attachments: LocalRunner.java, MyCounterService.java, 
> MyCounterServiceImpl.java
>
>
> Please see attached test, it starts N_CORES*2+2 nodes first and after this 
> starts N_CORES*2 threads with while(true) cycle in which closes and starts 
> nodes with small random pause.
> After couple minutes it hangs with Failed to wait for partition map exchange.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8530) Exchange hangs during start/stop stress test

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan updated IGNITE-8530:
--
Priority: Blocker  (was: Major)

> Exchange hangs during start/stop stress test
> 
>
> Key: IGNITE-8530
> URL: https://issues.apache.org/jira/browse/IGNITE-8530
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.4
>Reporter: Mikhail Cherkasov
>Assignee: Anton Kalashnikov
>Priority: Blocker
> Fix For: 2.6
>
> Attachments: LocalRunner.java, MyCounterService.java, 
> MyCounterServiceImpl.java
>
>
> Please see attached test, it starts N_CORES*2+2 nodes first and after this 
> starts N_CORES*2 threads with while(true) cycle in which closes and starts 
> nodes with small random pause.
> After couple minutes it hangs with Failed to wait for partition map exchange.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8587) High Contention in GridToStringBuilder.toStringImpl

[Sergey Kosarev (JIRA)]

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

Sergey Kosarev updated IGNITE-8587:
---
Description: 
org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache 
implemented as 

ordinal HashMap with all operations syncronised by one ReadWriteLock.

this can trigger high contention as this class widely used in toString() 
methods.

For instance it shoots when DEBUG or TRACE logs are  enabled as count of 
toString() invocations increases in this case extremely.

We need to use ConcurrentHashMap instead and avoid global locks.

  was:
org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache 
implemented as 

ordinal HashMap with all operations syncronised by one ReadWriteLock.

this can trigger high contention as this class widely used in toString() 
methods.

For instnace it shoots when DEBUG or TRACE logs are  enabled as count of 
toString() invocations increases in this case massively.

We need to use ConcurrentHashMap instead and avoid global locks.


> High Contention in GridToStringBuilder.toStringImpl  
> -
>
> Key: IGNITE-8587
> URL: https://issues.apache.org/jira/browse/IGNITE-8587
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache 
> implemented as 
> ordinal HashMap with all operations syncronised by one ReadWriteLock.
> this can trigger high contention as this class widely used in toString() 
> methods.
> For instance it shoots when DEBUG or TRACE logs are  enabled as count of 
> toString() invocations increases in this case extremely.
> We need to use ConcurrentHashMap instead and avoid global locks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8586) Minor fix for Apache Ignite's release procedure

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-8586:
-

Thanks for contribution! Merged to master and ignite-2.5 branches.

> Minor fix for Apache Ignite's release procedure
> ---
>
> Key: IGNITE-8586
> URL: https://issues.apache.org/jira/browse/IGNITE-8586
> Project: Ignite
>  Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.5
>
>
> Fix package.sh to not require sudo permissions for packages build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8586) Minor fix for Apache Ignite's release procedure

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-8586:

Fix Version/s: 2.5

> Minor fix for Apache Ignite's release procedure
> ---
>
> Key: IGNITE-8586
> URL: https://issues.apache.org/jira/browse/IGNITE-8586
> Project: Ignite
>  Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.5
>
>
> Fix package.sh to not require sudo permissions for packages build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8584) Provide ability to terminate any thread with enabled test features

[Dmitriy Sorokin (JIRA)]

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

Dmitriy Sorokin reassigned IGNITE-8584:
---

Assignee: Dmitriy Sorokin

> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.6
>
>
> We already have {{WorkersControlMXBean}} that provides possibility to 
> interrupt thread registered in system workers registry. We also want stop any 
> thread in the system for testing purposes.
> Method {{stop(String threadName)}} should be added that have to find thread 
> by name and stop it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8343) InetSocketAddress.getAddress() returns null, should check it in TcpCommunicationSpi

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-8343:

Labels: test  (was: )

> InetSocketAddress.getAddress() returns null, should check it in 
> TcpCommunicationSpi
> ---
>
> Key: IGNITE-8343
> URL: https://issues.apache.org/jira/browse/IGNITE-8343
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Labels: test
> Attachments: TcpDiscoveryMultiJvmTest.java
>
>
> This is especially notorious in the following scenario:
> {code}
> // -Djava.net.preferIPv4Stack=true
> System.err.println(new InetSocketAddress("0:0:0:0:0:0:0:1%lo", 
> 12345).getAddress()); // null
> {code}
> Yes we already warn if different nodes have differing preferIPv4Stack, still 
> this is warning not a error, and there may be other cases where getAddress() 
> returns null. Should make a check.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8343) InetSocketAddress.getAddress() returns null, should check it in TcpCommunicationSpi

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-8343:

Attachment: TcpDiscoveryMultiJvmTest.java

> InetSocketAddress.getAddress() returns null, should check it in 
> TcpCommunicationSpi
> ---
>
> Key: IGNITE-8343
> URL: https://issues.apache.org/jira/browse/IGNITE-8343
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Labels: test
> Attachments: TcpDiscoveryMultiJvmTest.java
>
>
> This is especially notorious in the following scenario:
> {code}
> // -Djava.net.preferIPv4Stack=true
> System.err.println(new InetSocketAddress("0:0:0:0:0:0:0:1%lo", 
> 12345).getAddress()); // null
> {code}
> Yes we already warn if different nodes have differing preferIPv4Stack, still 
> this is warning not a error, and there may be other cases where getAddress() 
> returns null. Should make a check.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8587) High Contention in GridToStringBuilder.toStringImpl

[Sergey Kosarev (JIRA)]

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

Sergey Kosarev updated IGNITE-8587:
---
Description: 
org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache 
implemented as 

ordinal HashMap with all operations syncronised by one ReadWriteLock.

this can trigger high contention as this class widely used in toString() 
methods.

For instnace it shoots when DEBUG or TRACE logs are  enabled as count of 
toString() invocations increases in this case massively.

We need to use ConcurrentHashMap instead and avoid global locks.

> High Contention in GridToStringBuilder.toStringImpl  
> -
>
> Key: IGNITE-8587
> URL: https://issues.apache.org/jira/browse/IGNITE-8587
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Sergey Kosarev
>Assignee: Sergey Kosarev
>Priority: Major
>
> org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache 
> implemented as 
> ordinal HashMap with all operations syncronised by one ReadWriteLock.
> this can trigger high contention as this class widely used in toString() 
> methods.
> For instnace it shoots when DEBUG or TRACE logs are  enabled as count of 
> toString() invocations increases in this case massively.
> We need to use ConcurrentHashMap instead and avoid global locks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8587) High Contention in GridToStringBuilder.toStringImpl

[Sergey Kosarev (JIRA)]

Sergey Kosarev created IGNITE-8587:
--

 Summary: High Contention in GridToStringBuilder.toStringImpl  
 Key: IGNITE-8587
 URL: https://issues.apache.org/jira/browse/IGNITE-8587
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.4
Reporter: Sergey Kosarev
Assignee: Sergey Kosarev






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8586) Minor fix for Apache Ignite's release procedure

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8586:


GitHub user vveider opened a pull request:

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

IGNITE-8586 Minor fix for Apache Ignite's release procedure



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

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

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

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


commit 16244d7ff374d59975e6b6b735f423d782c759f5
Author: Ivanov Petr 
Date:   2018-05-23T15:33:19Z

IGNITE-8586 Minor fix for Apache Ignite's release procedure




> Minor fix for Apache Ignite's release procedure
> ---
>
> Key: IGNITE-8586
> URL: https://issues.apache.org/jira/browse/IGNITE-8586
> Project: Ignite
>  Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
>
> Fix package.sh to not require sudo permissions for packages build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8586) Minor fix for Apache Ignite's release procedure

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8586:


 Summary: Minor fix for Apache Ignite's release procedure
 Key: IGNITE-8586
 URL: https://issues.apache.org/jira/browse/IGNITE-8586
 Project: Ignite
  Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Fix package.sh to not require sudo permissions for packages build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8585) Remove ignored-tests module, move those tests to regular suites in commented out form

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-8585:

Issue Type: Task  (was: Bug)

> Remove ignored-tests module, move those tests to regular suites in commented 
> out form
> -
>
> Key: IGNITE-8585
> URL: https://issues.apache.org/jira/browse/IGNITE-8585
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.6
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Minor
>  Labels: test
>
> Nobody either updates or runs this module and it's infeasible to use!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8585) Remove ignored-tests module, move those tests to regular suites in commented out form

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-8585:
---

 Summary: Remove ignored-tests module, move those tests to regular 
suites in commented out form
 Key: IGNITE-8585
 URL: https://issues.apache.org/jira/browse/IGNITE-8585
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6
Reporter: Ilya Kasnacheev
Assignee: Ilya Kasnacheev


Nobody either updates or runs this module and it's infeasible to use!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8584) Provide ability to terminate any thread with enabled test features

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-8584:
---

 Summary: Provide ability to terminate any thread with enabled test 
features
 Key: IGNITE-8584
 URL: https://issues.apache.org/jira/browse/IGNITE-8584
 Project: Ignite
  Issue Type: New Feature
Reporter: Andrey Gura
 Fix For: 2.6


We already have {{WorkersControlMXBean}} that provides possibility to interrupt 
thread registered in system workers registry. We also want stop any thread in 
the system for testing purposes.

Method {{stop(String threadName)}} should be added that have to find thread by 
name and stop it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not obvious

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: 
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is not obvious.

-  add new method getUsedCheckpointBufferPages, should show used size.

-  should show real size of checkpoint buffer geCheckpointBufferSize

  was:
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is nor clear.

-  add new method getUsedCheckpointBufferPages, should show used size.

-  should show real size of checkpoint buffer geCheckpointBufferSize


> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not obvious
> ---
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is not obvious.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7951) Add metrics for remains to evict keys/partitions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7951:


GitHub user alex-plekhanov opened a pull request:

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

IGNITE-7951 Add metrics for remains to evict keys/partitions



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

$ git pull https://github.com/alex-plekhanov/ignite ignite-7951

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

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


commit 8d21d5713f3ea326d252ae3dd13adb890102d8a9
Author: Aleksey Plekhanov 
Date:   2018-05-23T15:05:54Z

IGNITE-7951 Add metrics for remains to evict keys/partitions




> Add metrics for remains to evict keys/partitions
> 
>
> Key: IGNITE-7951
> URL: https://issues.apache.org/jira/browse/IGNITE-7951
> Project: Ignite
>  Issue Type: New Feature
>  Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: jmx
> Fix For: 2.6
>
>
> Need to add some metrics for remains to evict keys/partitions to indicate 
> total amount of evicting work. In some cases we have synchronous eviction and 
> it's critically important to know how many keys need to be evicted before 
> exchange process end and cluster became working again. In some other cases we 
> just wanna know what happens in cluster now (background eviction without 
> workload) and when cluster will became 100% healthy. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not obvious

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: 
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is not obvious.

-  add new method getUsedCheckpointBufferSize, should show used size.

-  should show real size of checkpoint buffer geCheckpointBufferSize

  was:
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is not obvious.

-  add new method getUsedCheckpointBufferPages, should show used size.

-  should show real size of checkpoint buffer geCheckpointBufferSize


> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not obvious
> ---
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is not obvious.
> -  add new method getUsedCheckpointBufferSize, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov edited comment on IGNITE-7809 at 5/23/18 3:06 PM:
-

- added link to TC run, 
- added small updates to code:
-- revered import-only changes, 
-- removed unused imports, 
-- done several javadoc changes,
- unmuned tests on TC 
- and merged changes to master. 

[~ilantukh] thank you for contribution, [~astelmak], thank you for review.


was (Author: dpavlov):
- added link to TC run, 
- added small updates to code:
-- revered import-only changes, 
-- removed unused imports, 
-- done several javadoc changes,
-unmuned tests on TC 
-and merged changes to master. 

[~ilantukh] thank you for contribution, [~astelmak], thank you for review.

> Ignite PDS 2 & PDS 2 Direct IO: stable failures of 
> IgniteWalFlushDefaultSelfTest
> 
>
> Key: IGNITE-7809
> URL: https://issues.apache.org/jira/browse/IGNITE-7809
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop 
> after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail
>Ignite PDS 2 (Direct IO) [ tests 2 ]  
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailAfterStart (fail rate 13,0%) 
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailWhileStart (fail rate 13,0%) 
>Ignite PDS 2 [ tests 2 ]  
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailAfterStart 
> (fail rate 8,4%) 
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailWhileStart 
> (fail rate 8,4%) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not obvious

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8583:


GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-8583 fix checkpoint buffer size metric



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

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

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

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


commit 1aa8e4c00659d79411a611d503473bdec78195d6
Author: Dmitriy Govorukhin 
Date:   2018-05-23T15:04:05Z

IGNITE-8583 fix checkpoint buffer size metric




> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not obvious
> ---
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7809:


Github user asfgit closed the pull request at:

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


> Ignite PDS 2 & PDS 2 Direct IO: stable failures of 
> IgniteWalFlushDefaultSelfTest
> 
>
> Key: IGNITE-7809
> URL: https://issues.apache.org/jira/browse/IGNITE-7809
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop 
> after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail
>Ignite PDS 2 (Direct IO) [ tests 2 ]  
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailAfterStart (fail rate 13,0%) 
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailWhileStart (fail rate 13,0%) 
>Ignite PDS 2 [ tests 2 ]  
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailAfterStart 
> (fail rate 8,4%) 
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailWhileStart 
> (fail rate 8,4%) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not obvious

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin reassigned IGNITE-8583:
--

Assignee: Dmitriy Govorukhin

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not obvious
> ---
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not obvious

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Summary: DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer 
size, this is not obvious  (was: DataStorageMetricsMXBean.getOffHeapSize 
include checkpoint buffer size, this is not clear)

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not obvious
> ---
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: 
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is nor clear.

-  add new method getUsedCheckpointBufferPages, should show used size.

-  should show real size of checkpoint buffer geCheckpointBufferSize

  was:
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is nor clear.

-  add new method getUsedCheckpointBufferPages

-  geCheckpointBufferSize


> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Affects Version/s: 2.4

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Fix Version/s: 2.6

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.6
>
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages, should show used size.
> -  should show real size of checkpoint buffer geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: 
Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer inside, 
on mxbean this is nor clear.

-  add new method getUsedCheckpointBufferPages

-  geCheckpointBufferSize

  was:Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
inside, on mxbean this is nor clear.


> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.
> -  add new method getUsedCheckpointBufferPages
> -  geCheckpointBufferSize



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: Now DataStorageMetricsMXBean.getOffHeapSize includes 
checkpoint buffer inside, on mxbean this is nor clear.  (was: Now 
DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer inside, on 
mxbean this is nor cleaer.)

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
>
> Now DataStorageMetricsMXBean.getOffHeapSize includes checkpoint buffer 
> inside, on mxbean this is nor clear.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: Now DataStorageMetricsMXBean.getOffHeapSize include checkpoing 
buffer inside, on mxbean this is nor cleaer.  (was: Now )

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
>
> Now DataStorageMetricsMXBean.getOffHeapSize include checkpoing buffer inside, 
> on mxbean this is nor cleaer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: Now DataStorageMetricsMXBean.getOffHeapSize include checkpoint 
buffer inside, on mxbean this is nor cleaer.  (was: Now 
DataStorageMetricsMXBean.getOffHeapSize include checkpoing buffer inside, on 
mxbean this is nor cleaer.)

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
>
> Now DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer inside, 
> on mxbean this is nor cleaer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-8583:
---
Description: Now 

> DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this 
> is not clear
> -
>
> Key: IGNITE-8583
> URL: https://issues.apache.org/jira/browse/IGNITE-8583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Priority: Major
>
> Now 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8583) DataStorageMetricsMXBean.getOffHeapSize include checkpoint buffer size, this is not clear

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-8583:
--

 Summary: DataStorageMetricsMXBean.getOffHeapSize include 
checkpoint buffer size, this is not clear
 Key: IGNITE-8583
 URL: https://issues.apache.org/jira/browse/IGNITE-8583
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Govorukhin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8582) MVCC TX: Cache store read-through support

[Sergey Kalashnikov (JIRA)]

Sergey Kalashnikov created IGNITE-8582:
--

 Summary: MVCC TX: Cache store read-through support
 Key: IGNITE-8582
 URL: https://issues.apache.org/jira/browse/IGNITE-8582
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Sergey Kalashnikov


Add support for read-through cache store for mvcc caches.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8581) MVCC TX: data streamer support

[Sergey Kalashnikov (JIRA)]

Sergey Kalashnikov created IGNITE-8581:
--

 Summary: MVCC TX: data streamer support
 Key: IGNITE-8581
 URL: https://issues.apache.org/jira/browse/IGNITE-8581
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Sergey Kalashnikov


Add support for data streamer for mvcc caches.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8480) Broken Ignite Examples test Support Spring Data 2.0

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-8480:


Hi [~skozlov], could you please take a look?

This does not change example itself, but fix is related to examples. 

It seems user which will use SpringData 2.0 will get correct dependencies 
(without any additional steps). But it would be good if you could look also.

> Broken Ignite Examples test Support Spring Data 2.0
> ---
>
> Key: IGNITE-8480
> URL: https://issues.apache.org/jira/browse/IGNITE-8480
> Project: Ignite
>  Issue Type: Test
>  Components: spring
>Affects Versions: 2.6
>Reporter: Dmitriy Pavlov
>Assignee: Roman Meerson
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://issues.apache.org/jira/browse/IGNITE-6879 implementation was 
> introduced support of spring data of version 2.0+ 
>  
> But example test is broken on TC after this change
> [Examples 
> |https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples=%3Cdefault%3E=buildTypeStatusDiv]
>   IgniteExamplesSelfTestSuite: 
> SpringDataExampleSelfTest.testSpringDataExample
>  
> Test history: 
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9052304574499269123=%3Cdefault%3E=testDetails]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8561) SinglSegmentLogicalRecordsIterator is broken

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8561:


GitHub user glukos opened a pull request:

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

IGNITE-8561 SingleSegmentLogicalRecordsIterator is broken

Signed-off-by: Ivan Rakov 

(cherry picked from commit 21678bc)

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

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

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

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


commit 3c112ccdb08512febd1234b14ca08521130a49df
Author: Anton Kalashnikov 
Date:   2018-05-23T09:24:51Z

IGNITE-8561 SingleSegmentLogicalRecordsIterator is broken

Signed-off-by: Ivan Rakov 

(cherry picked from commit 21678bc)




> SinglSegmentLogicalRecordsIterator is broken
> 
>
> Key: IGNITE-8561
> URL: https://issues.apache.org/jira/browse/IGNITE-8561
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.6
>
>
> It causes by https://issues.apache.org/jira/browse/IGNITE-8464



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8580) Print page read/write metrics splitted by type

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-8580:
---

 Summary: Print page read/write metrics splitted by type
 Key: IGNITE-8580
 URL: https://issues.apache.org/jira/browse/IGNITE-8580
 Project: Ignite
  Issue Type: Task
  Components: persistence
Reporter: Vladimir Ozerov
 Fix For: 2.6


Currently it is impossible to track how many pages of a certain type were read 
from or written to disk. This might be very useful for performance tuning and 
debugging purposes. E.g. excessive page reads may highlight missing SQL index.

We need to expose total read/write pages metrics splitted by page type (see 
org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO#getType()).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8579) SQL: Unicast request with LIMIT should skip merge table if possible

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-8579:
---

 Summary: SQL: Unicast request with LIMIT should skip merge table 
if possible
 Key: IGNITE-8579
 URL: https://issues.apache.org/jira/browse/IGNITE-8579
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.5
Reporter: Vladimir Ozerov
 Fix For: 2.6


*Problem*
We have two cases when request could be executed only over a single partition:
1) With explicit partition
2) When partition pruning optimization reduced request to a single partition 
(IGNITE-4509). E.g. if {{department_id}} is affinity key in the query below:
{code}
SELECT * FROM emp WHERE department_id=? LIMIT 50;
{code}

In both cases we need to ensure that instead of fully-fledged two-step 
execution, we perform only map request, and reduce phase is skipped. I.e. 
{{org.apache.ignite.internal.processors.cache.query.GridCacheTwoStepQuery#skipMergeTbl}}
 is resolved to true.

*Reproducer*
The following query reproduces a situation when this is not the case at the 
moment, and merge table is initialized
{code}
CREATE TABLE emp (pk_id BIGINT, dept_ID BIGINT, name VARCHAR, PRIMARY 
KEY(pk_id, dept_id) WITH "AFFINITY_KEY=dept_id";
SELECT * FROM emp WHERE dept_id=? LIMIT 10
{code}

Notice that reduce phase exists, while in reality it is not needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-8560) Update index validation utility to use statistical check approach

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov edited comment on IGNITE-8560 at 5/23/18 2:04 PM:
--

Patch artifacts: [PR|https://github.com/apache/ignite/pull/4051], [TC 
run|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll=buildTypeStatusDiv_IgniteTests24Java8=pull%2F4051%2Fhead],
 [review|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-619]


was (Author: sergey-chugunov):
Patch artifacts: [PR|https://github.com/apache/ignite/pull/4051], [TC 
run|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll=buildTypeStatusDiv_IgniteTests24Java8=pull%2F4051%2Fhead]

> Update index validation utility to use statistical check approach
> -
>
> Key: IGNITE-8560
> URL: https://issues.apache.org/jira/browse/IGNITE-8560
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.6
>
>
> Currently, the check index feature of {{control.sh}} scans the full data set 
> which has N * logN complexity. On large data sets this takes too long to 
> complete. 
> To mitigate this, I suggest to add an option 
> * to check either first K entries
> * to check each Kth entry



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8578) .Net Add support baseline auto-adjust parameters (definition, run-time change)

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-8578:
-

 Summary: .Net Add support baseline auto-adjust parameters 
(definition, run-time change)
 Key: IGNITE-8578
 URL: https://issues.apache.org/jira/browse/IGNITE-8578
 Project: Ignite
  Issue Type: New Feature
Reporter: Eduard Shangareev
 Fix For: 2.6


We would introduce at IGNITE-8571 new parameters. 

We need their support in .Net side.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8577) Add MIGRATION_GUIDE file

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-8577.
---

> Add MIGRATION_GUIDE file
> 
>
> Key: IGNITE-8577
> URL: https://issues.apache.org/jira/browse/IGNITE-8577
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.6
>
>
> We are going to log all important changes in public API (deprecations, better 
> APIs, changes to default behavior) in separate document, called 
> "MIGRATION_GUIDE". 
> Need to create it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-8577) Add MIGRATION_GUIDE file

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-8577.
-
Resolution: Fixed

> Add MIGRATION_GUIDE file
> 
>
> Key: IGNITE-8577
> URL: https://issues.apache.org/jira/browse/IGNITE-8577
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.6
>
>
> We are going to log all important changes in public API (deprecations, better 
> APIs, changes to default behavior) in separate document, called 
> "MIGRATION_GUIDE". 
> Need to create it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8577) Add MIGRATION_GUIDE file

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-8577:
---

 Summary: Add MIGRATION_GUIDE file
 Key: IGNITE-8577
 URL: https://issues.apache.org/jira/browse/IGNITE-8577
 Project: Ignite
  Issue Type: Task
  Components: general
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.6


We are going to log all important changes in public API (deprecations, better 
APIs, changes to default behavior) in separate document, called 
"MIGRATION_GUIDE". 
Need to create it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8576) Change Baseline auto-adjust parameters via SQL

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-8576:
-

 Summary: Change Baseline auto-adjust parameters via SQL
 Key: IGNITE-8576
 URL: https://issues.apache.org/jira/browse/IGNITE-8576
 Project: Ignite
  Issue Type: New Feature
Reporter: Eduard Shangareev
 Fix For: 2.6


We would introduce at IGNITE-8571 new parameters. 

We need to have option change them via SQL.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8560) Update index validation utility to use statistical check approach

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-8560:

Fix Version/s: 2.6

> Update index validation utility to use statistical check approach
> -
>
> Key: IGNITE-8560
> URL: https://issues.apache.org/jira/browse/IGNITE-8560
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.6
>
>
> Currently, the check index feature of {{control.sh}} scans the full data set 
> which has N * logN complexity. On large data sets this takes too long to 
> complete. 
> To mitigate this, I suggest to add an option 
> * to check either first K entries
> * to check each Kth entry



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov edited comment on IGNITE-5954 at 5/23/18 1:42 PM:
---

the bug is in the following scenario:
1) near node requests key, save it in near cache
2) near node becames primary or backup
3) new value is inserted and propagated to the node. On this step, new value is 
set into DHT cache, not Near one. We have obsolete value in Near cache
4) near node again became near
5) we have obsolete value in Near cache. This is a bug 

Fix is to remove value from near cache on 3 step. Removing should be performed 
in
processDhtAtomicUpdateRequest(), after new value is inserted in DHT cache.


was (Author: alexey kuznetsov):
the bug is in the following scenario:
1) near node requests key, save it in near cache
2) near node becames primary or backup
3) new value is inserted and propagated to the node. On this step, new value is 
set into DHT cache, not Near one. We have obsolete value in Near cache
4) near node again became near
5) we have obsolete value in Near cache. This is a bug 

> Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove 
> fails
> --
>
> Key: IGNITE-5954
> URL: https://issues.apache.org/jira/browse/IGNITE-5954
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Alexey Kuznetsov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Probably, it's broken after IGNITE-5272.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5954:


GitHub user voipp opened a pull request:

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

IGNITE-5954 Remove obsolete near cache value from primary\backup node.



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

$ git pull https://github.com/voipp/ignite IGNITE-5954

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

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


commit 4e6cd513856d460b65d91f5eee05ad3bd6269277
Author: voipp 
Date:   2018-05-23T13:14:51Z

IGNITE-5954 Remove obsolete near cache value from primary\backup node.




> Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove 
> fails
> --
>
> Key: IGNITE-5954
> URL: https://issues.apache.org/jira/browse/IGNITE-5954
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Alexey Kuznetsov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Probably, it's broken after IGNITE-5272.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8575) Change Baseline auto-adjust parameters via console.sh

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-8575:
-

 Summary: Change Baseline auto-adjust parameters via console.sh
 Key: IGNITE-8575
 URL: https://issues.apache.org/jira/browse/IGNITE-8575
 Project: Ignite
  Issue Type: New Feature
Reporter: Eduard Shangareev
 Fix For: 2.6


We would introduce at IGNITE-8571 new parameters. 
We need to have option change them via JMX.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8574) Change Baseline auto-adjust parameters via JMX

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-8574:
-

 Summary: Change Baseline auto-adjust parameters via JMX
 Key: IGNITE-8574
 URL: https://issues.apache.org/jira/browse/IGNITE-8574
 Project: Ignite
  Issue Type: New Feature
Reporter: Eduard Shangareev
 Fix For: 2.6


We would introduce at IGNITE-8571 new parameters. 
We need to have option change them via JMX.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8573) Save baseline auto-adjust parameters to metastore

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-8573:
-

 Summary: Save baseline auto-adjust parameters to metastore
 Key: IGNITE-8573
 URL: https://issues.apache.org/jira/browse/IGNITE-8573
 Project: Ignite
  Issue Type: New Feature
Reporter: Eduard Shangareev
 Fix For: 2.6


We would introduce at IGNITE-8048 new parameters. They should be saved in the 
metastore and restored from it on node/cluster restart.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8573) Save baseline auto-adjust parameters to metastore

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-8573:
--
Description: We would introduce at IGNITE-8571 new parameters. They should 
be saved in the metastore and restored from it on node/cluster restart.  (was: 
We would introduce at IGNITE-8048 new parameters. They should be saved in the 
metastore and restored from it on node/cluster restart.)

> Save baseline auto-adjust parameters to metastore
> -
>
> Key: IGNITE-8573
> URL: https://issues.apache.org/jira/browse/IGNITE-8573
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Eduard Shangareev
>Priority: Major
>  Labels: IEP-4, Phase-2
> Fix For: 2.6
>
>
> We would introduce at IGNITE-8571 new parameters. They should be saved in the 
> metastore and restored from it on node/cluster restart.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8560) Update index validation utility to use statistical check approach

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8560:


GitHub user sergey-chugunov-1985 opened a pull request:

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

IGNITE-8560 checkFirst and checkThrough parameters added



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

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

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

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


commit 4462573638e9b06e5686a0f8ebfce4e9aa8d481b
Author: Sergey Chugunov 
Date:   2018-05-23T12:55:27Z

IGNITE-8560 checkFirst and checkThrough parameters added




> Update index validation utility to use statistical check approach
> -
>
> Key: IGNITE-8560
> URL: https://issues.apache.org/jira/browse/IGNITE-8560
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
>Priority: Major
>
> Currently, the check index feature of {{control.sh}} scans the full data set 
> which has N * logN complexity. On large data sets this takes too long to 
> complete. 
> To mitigate this, I suggest to add an option 
> * to check either first K entries
> * to check each Kth entry



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8572) StandaloneWalRecordsIterator may throw NPE if compressed WAL segment is empty

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-8572:
--

 Summary: StandaloneWalRecordsIterator may throw NPE if compressed 
WAL segment is empty
 Key: IGNITE-8572
 URL: https://issues.apache.org/jira/browse/IGNITE-8572
 Project: Ignite
  Issue Type: New Feature
  Components: persistence
Reporter: Ivan Rakov
Assignee: Ivan Rakov
 Fix For: 2.6


In case ZIP archive with WAL segment doesn't contain any ZIP entries, attempt 
to iterate through it with standalone WAL iterator will throw NPE:
{noformat}
Caused by: java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.persistence.file.UnzipFileIO.(UnzipFileIO.java:53)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:265)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.advanceSegment(StandaloneWalRecordsIterator.java:262)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:155)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.(StandaloneWalRecordsIterator.java:111)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.iteratorArchiveDirectory(IgniteWalIteratorFactory.java:156)
... 6 more
{noformat}
We should throw excpetion with descriptive error message instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8571) Baseline auto-adjust feature

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-8571:
--
Fix Version/s: 2.6

> Baseline auto-adjust feature
> 
>
> Key: IGNITE-8571
> URL: https://issues.apache.org/jira/browse/IGNITE-8571
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Eduard Shangareev
>Priority: Major
>  Labels: IEP-4, Phase-2
> Fix For: 2.6
>
>
> Now we have only one way to change BLAT - manually update it via console.sh 
> or API.
> We need to add the possibility to change it automatically. Adjust to current 
> topology.
> So, I propose 3 new parameters which would be responsible to tune this 
> feature.
> 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto 
> adjusting baseline.
> 2. autoAdjustTimeout - time which we would wait after the actual topology 
> change. But it would be reset if new discovery event happened. (node 
> join/exit).
> 3. autoAdjustMaxTimeout - time which we would wait from the first dicovery 
> event in the chain. If we achieved it than we would change BLAT right away 
> (no matter were another node join/exit happened or not).
> We need to change API next way:
> 1. org.apache.ignite.IgniteCluster
> *Add*
> isBaselineAutoAdjustEnabled()
> setBaselineAutoAdjustEnabled(boolean enabled);
> setBaselineAutoAdjustTimeout(long timeoutInMs);
> setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> 2. org.apache.ignite.configuration.IgniteConfiguration
> *Add*
> IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled);
> IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs);
> IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> Also, we need to ensure that all nodes would have the same parameters.
> And we should be able to survive coordinator left during parameters changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-8571) Baseline auto-adjust feature

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-8571:
--
Labels: IEP-4 Phase-2  (was: )

> Baseline auto-adjust feature
> 
>
> Key: IGNITE-8571
> URL: https://issues.apache.org/jira/browse/IGNITE-8571
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Eduard Shangareev
>Priority: Major
>  Labels: IEP-4, Phase-2
>
> Now we have only one way to change BLAT - manually update it via console.sh 
> or API.
> We need to add the possibility to change it automatically. Adjust to current 
> topology.
> So, I propose 3 new parameters which would be responsible to tune this 
> feature.
> 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto 
> adjusting baseline.
> 2. autoAdjustTimeout - time which we would wait after the actual topology 
> change. But it would be reset if new discovery event happened. (node 
> join/exit).
> 3. autoAdjustMaxTimeout - time which we would wait from the first dicovery 
> event in the chain. If we achieved it than we would change BLAT right away 
> (no matter were another node join/exit happened or not).
> We need to change API next way:
> 1. org.apache.ignite.IgniteCluster
> *Add*
> isBaselineAutoAdjustEnabled()
> setBaselineAutoAdjustEnabled(boolean enabled);
> setBaselineAutoAdjustTimeout(long timeoutInMs);
> setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> 2. org.apache.ignite.configuration.IgniteConfiguration
> *Add*
> IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled);
> IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs);
> IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs);
> Also, we need to ensure that all nodes would have the same parameters.
> And we should be able to survive coordinator left during parameters changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8571) Baseline auto-adjust feature

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-8571:
-

 Summary: Baseline auto-adjust feature
 Key: IGNITE-8571
 URL: https://issues.apache.org/jira/browse/IGNITE-8571
 Project: Ignite
  Issue Type: New Feature
Reporter: Eduard Shangareev


Now we have only one way to change BLAT - manually update it via console.sh or 
API.

We need to add the possibility to change it automatically. Adjust to current 
topology.

So, I propose 3 new parameters which would be responsible to tune this feature.
1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto 
adjusting baseline.

2. autoAdjustTimeout - time which we would wait after the actual topology 
change. But it would be reset if new discovery event happened. (node join/exit).

3. autoAdjustMaxTimeout - time which we would wait from the first dicovery 
event in the chain. If we achieved it than we would change BLAT right away (no 
matter were another node join/exit happened or not).

We need to change API next way:
1. org.apache.ignite.IgniteCluster

*Add*
isBaselineAutoAdjustEnabled()
setBaselineAutoAdjustEnabled(boolean enabled);
setBaselineAutoAdjustTimeout(long timeoutInMs);
setBaselineAutoAdjustMaxTimeout(long timeoutInMs);

2. org.apache.ignite.configuration.IgniteConfiguration

*Add*
IgniteConfiguration setBaselineAutoAdjustEnabled(boolean enabled);
IgniteConfiguration setBaselineAutoAdjustTimeout(long timeoutInMs);
IgniteConfiguration setBaselineAutoAdjustMaxTimeout(long timeoutInMs);

Also, we need to ensure that all nodes would have the same parameters.
And we should be able to survive coordinator left during parameters changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8183) ZookeeperDiscoverySpiTest#testSegmentation3 fails on TC and locally

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8183:


GitHub user dgarus opened a pull request:

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

IGNITE-8183 run test 50 times



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

$ git pull https://github.com/dgarus/ignite ignite-8183

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

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


commit 0893dbac3409248c0638f0bd259ac088c279e09c
Author: Garus Denis 
Date:   2018-05-23T12:17:24Z

IGNITE-8183 run test 50 times




> ZookeeperDiscoverySpiTest#testSegmentation3 fails on TC and locally
> ---
>
> Key: IGNITE-8183
> URL: https://issues.apache.org/jira/browse/IGNITE-8183
> Project: Ignite
>  Issue Type: Bug
>  Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Denis Garus
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Test fails with assertion on awaits on latch:
> {noformat}
> junit.framework.AssertionFailedError
> 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.zk.internal.ZookeeperDiscoverySpiTest.testSegmentation3(ZookeeperDiscoverySpiTest.java:1060)
> 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:2080)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> For some reason SEGMENTATION event is never fired, so assertion on latch 
> fails. Investigation is needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in client's configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5789:


Github user asfgit closed the pull request at:

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


> After client reconnects to server if server was restarted, client doesn't 
> create caches defined in client's configuration
> -
>
> Key: IGNITE-5789
> URL: https://issues.apache.org/jira/browse/IGNITE-5789
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Evgenii Zhuravlev
>Assignee: vk
>Priority: Major
> Fix For: 2.6
>
> Attachments: ClientReconnectAfterClusterRestartTest.java
>
>
> User with this problem on SO:
> https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8480) Broken Ignite Examples test Support Spring Data 2.0

[Roman Meerson (JIRA)]

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

Roman Meerson commented on IGNITE-8480:
---

Hi [~dpavlov],

If end user would want to use spring-data_2.0 they do not need to have 
additional dependency on ignite-spring, that`s why everything would work fine.

If they have separate dependency on ignite-spring they should exlude separate 
dependencies from ignite-spring as i did in examples module.

Anyway, as far as i understand migration to spring version 5.0 didn`t affect 
module ignite-spring, that`s why it`s possible only to change dependencies on 
newer version and everything works fine

> Broken Ignite Examples test Support Spring Data 2.0
> ---
>
> Key: IGNITE-8480
> URL: https://issues.apache.org/jira/browse/IGNITE-8480
> Project: Ignite
>  Issue Type: Test
>  Components: spring
>Affects Versions: 2.6
>Reporter: Dmitriy Pavlov
>Assignee: Roman Meerson
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://issues.apache.org/jira/browse/IGNITE-6879 implementation was 
> introduced support of spring data of version 2.0+ 
>  
> But example test is broken on TC after this change
> [Examples 
> |https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples=%3Cdefault%3E=buildTypeStatusDiv]
>   IgniteExamplesSelfTestSuite: 
> SpringDataExampleSelfTest.testSpringDataExample
>  
> Test history: 
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9052304574499269123=%3Cdefault%3E=testDetails]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8570) Create lighter version of GridStringLogger

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-8570:


 Summary: Create lighter version of GridStringLogger
 Key: IGNITE-8570
 URL: https://issues.apache.org/jira/browse/IGNITE-8570
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.4
Reporter: Andrey Kuznetsov
 Fix For: 2.6


Most usages of {{GridStringLogger}} in test assumes the following scenario. 
First, it is set as a logger for some Ignite node. Then, after some activity on 
that node, log content is searched for some predefined strings. 
{{GridStringLogger}} uses {{StringBuilder}} of bounded size internally to store 
log contents, older contents gets dropped on exaustion. Thus, changes that add 
more logging may damage some independent tests that use {{GridStringLogger}}.

The suggestion is to implement and use another test logger conforming to these 
requirements:
* It does not accumulate any logs.
* It allows to set the listener that fires when log message matches certain 
regular expression, {{Matcher}} can be passed to the listener.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8568) Web Console: Add support for "collocated" query mode on Query screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-8568:
---

Implemented possibility to execute collocated query on Query screen.

> Web Console: Add support for "collocated" query mode on Query screen
> 
>
> Key: IGNITE-8568
> URL: https://issues.apache.org/jira/browse/IGNITE-8568
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.6
>
>
> Ignite SQL engine supports special flag "collocated" that can improve 
> performance of  SQL queries in special situations.
> Lets add this flag to Query screen UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8568) Web Console: Add support for "collocated" query mode on Query screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-8568:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web Console: Add support for "collocated" query mode on Query screen
> 
>
> Key: IGNITE-8568
> URL: https://issues.apache.org/jira/browse/IGNITE-8568
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.6
>
>
> Ignite SQL engine supports special flag "collocated" that can improve 
> performance of  SQL queries in special situations.
> Lets add this flag to Query screen UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7165) Re-balancing is cancelled if client node joins

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7165:


GitHub user Mmuzaf opened a pull request:

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

 IGNITE-7165: do not cancel rebalance at client join left topology



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

$ git pull https://github.com/Mmuzaf/ignite ignite-7165

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

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


commit 339e5a6e6e18bb136d988e85dc81f67686bda285
Author: Maxim Muzafarov 
Date:   2018-05-23T11:07:53Z

IGNITE-7165: do not cancel rebalance at client join left topology

commit 4c0b5a3649033bf22f773f753bf96f0ae54e7537
Author: Maxim Muzafarov 
Date:   2018-05-23T11:11:10Z

IGNITE-7165: code styles




> Re-balancing is cancelled if client node joins
> --
>
> Key: IGNITE-7165
> URL: https://issues.apache.org/jira/browse/IGNITE-7165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Muzafarov
>Priority: Critical
>  Labels: rebalance
> Fix For: 2.6
>
>
> Re-balancing is canceled if client node joins. Re-balancing can take hours 
> and each time when client node joins it starts again:
> [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Added new node to topology: TcpDiscoveryNode 
> [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, 
> /172.31.16.213:0], discPort=0, order=36, intOrder=24, 
> lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, 
> isClient=true]
> [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager]
>  Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, 
> customEvt=null, allowMerge=true]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture]
>  Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, 
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> err=null]
> [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished 
> exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> crd=false]
> [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion 
> [topVer=36, minorTopVer=0], evt=NODE_JOINED, 
> node=979cf868-1c37-424a-9ad1-12db501f32ef]
> [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion 
> [topVer=35, minorTopVer=0]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing scheduled [order=[statementp]]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager]
>  Rebalancing started [top=null, evt=NODE_JOINED, 
> node=a8be3c14-9add-48c3-b099-3fd304cfdbf4]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander]
>  Starting rebalancing [mode=ASYNC, 
> fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, 
> topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], 
> updateSeq=-1754630006]
> 

[jira] [Commented] (IGNITE-7309) Sutable exception should be return as job results when node is about to stop.

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7309:


[~guseinov] I left some comments in PR, could you please address?

> Sutable exception should be return as job results when node is about to stop.
> -
>
> Key: IGNITE-7309
> URL: https://issues.apache.org/jira/browse/IGNITE-7309
> Project: Ignite
>  Issue Type: Bug
>  Components: compute, general
>Reporter: Andrew Mashenkov
>Assignee: Roman Guseinov
>Priority: Minor
>  Labels: newbie, pull-request-available
>
> User job can fails with confusing exception when server node is stopping and 
> going to leave the grid. 
> We should suppress InterruptedException. If node is stopping then user should 
> see NodeStoppingException.
> {code:java}
> [org.apache.ignite.internal.processors.job.GridJobWorker] Failed to serialize 
> job response [nodeId=02e1588
> c-53eb-454a-99a1-48ac6cb33667, ses=GridJobSessionImpl 
> [ses=GridTaskSessionImpl 
> ..
> org.apache.ignite.IgniteCheckedException: Failed to register class.
>   at 
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9929)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:819)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:760)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:619)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:483)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1180)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1899)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1519)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1147)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:119)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1087)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.binary.BinaryObjectException: Failed to register 
> class.
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerUserClassDescriptor(BinaryContext.java:778)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.registerClassDescriptor(BinaryContext.java:751)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForClass(BinaryContext.java:621)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:164)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:239)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.marshal0(BinaryMarshaller.java:82)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:9923)
>   ... 14 common frames omitted
> Caused by: org.apache.ignite.internal.IgniteInterruptedCheckedException: null
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.tryGetAndPut(GridDhtAtomicCache.java:724)
>   at 
> org.apache.ignite.internal.MarshallerContextImpl.registerClassName(MarshallerContextImpl.java:169)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:168)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter$1.applyx(MarshallerContextAdapter.java:166)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.computeIfAbsent(MarshallerContextAdapter.java:224)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.registerClass(MarshallerContextAdapter.java:164)
>   at 
> 

[jira] [Commented] (IGNITE-8480) Broken Ignite Examples test Support Spring Data 2.0

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-8480:


Hi [~homich] I found PR change reasonable for now.

How this change affect end users? What if users will have dependency to 
ignite-spring-data_2.0, whould they have to set  custom spring version?

> Broken Ignite Examples test Support Spring Data 2.0
> ---
>
> Key: IGNITE-8480
> URL: https://issues.apache.org/jira/browse/IGNITE-8480
> Project: Ignite
>  Issue Type: Test
>  Components: spring
>Affects Versions: 2.6
>Reporter: Dmitriy Pavlov
>Assignee: Roman Meerson
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.6
>
>
> https://issues.apache.org/jira/browse/IGNITE-6879 implementation was 
> introduced support of spring data of version 2.0+ 
>  
> But example test is broken on TC after this change
> [Examples 
> |https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples=%3Cdefault%3E=buildTypeStatusDiv]
>   IgniteExamplesSelfTestSuite: 
> SpringDataExampleSelfTest.testSpringDataExample
>  
> Test history: 
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9052304574499269123=%3Cdefault%3E=testDetails]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8008) Web console: Add a link to the SQL documentation in Notebook title

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8008:


Tested on master

> Web console: Add a link to the SQL documentation in Notebook title
> --
>
> Key: IGNITE-8008
> URL: https://issues.apache.org/jira/browse/IGNITE-8008
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
> Attachments: screenshot-1.png
>
>
> Add a link to the documentation in Notebook title
> https://apacheignite-sql.readme.io/docs/sql-reference-overview
>  !screenshot-1.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-8008) Web console: Add a link to the SQL documentation in Notebook title

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-8008:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: Add a link to the SQL documentation in Notebook title
> --
>
> Key: IGNITE-8008
> URL: https://issues.apache.org/jira/browse/IGNITE-8008
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
> Attachments: screenshot-1.png
>
>
> Add a link to the documentation in Notebook title
> https://apacheignite-sql.readme.io/docs/sql-reference-overview
>  !screenshot-1.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8547) Deserialization of Enum values as anonymous classes may cause deadlock

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-8547:
-

[~vkulichenko] in Binary marshaller, the issue was fixed with IGNITE-5087. I'm 
adding the test which tries all 3 of them (JDK, Bin, Opt)

> Deserialization of Enum values as anonymous classes may cause deadlock
> --
>
> Key: IGNITE-8547
> URL: https://issues.apache.org/jira/browse/IGNITE-8547
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>  Labels: test
> Attachments: MarshallerDeadlockMultiJvmTest.java
>
>
> Due to the following problem:
> {code}
> package jvmtest;
> import java.util.ArrayList;
> import java.util.List;
> import java.util.concurrent.BrokenBarrierException;
> import java.util.concurrent.CyclicBarrier;
> public class LegTypeTest {
> public static void main(String[] args) throws InterruptedException, 
> BrokenBarrierException {
> List threadList = new ArrayList<>();
> CyclicBarrier b1 = new CyclicBarrier(16);
> CyclicBarrier b2 = new CyclicBarrier(17);
>   for (int i = 0; i < 16; i++) {
>   final int ii = i;
>   Thread thread = new Thread(() -> {
> try {
> b1.await();
> if (ii % 2 == 0)
> Class.forName("jvmtest.LegTypeTest$E$1");
> if (ii % 2 == 1)
> Class.forName("jvmtest.LegTypeTest$E");
> b2.await();
> } catch (Exception e) {
> e.printStackTrace();
> }
> });
> thread.start();
> threadList.add(thread);
> }
> b2.await();
> for (Thread thread : threadList) {
>   thread.join();
> }
> }
> private enum E {
> A("A"),
> B("B") {
> @Override
> public String virtual() {
> return null;
> }
> };
> private String displayString;
> E(String displayString) {
> this.displayString = displayString;
> }
> public String virtual() {
> return displayString;
> }
> }
> }
> {code}
> When doing Class.forName on different enum values deadlock can be caused. And 
> that's exactly what OptimizedMarshaller does.
> See also the attached test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8569) Web console: incorrect user activities amount on admin page

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-8569:
--

 Summary: Web console: incorrect user activities amount on admin 
page
 Key: IGNITE-8569
 URL: https://issues.apache.org/jira/browse/IGNITE-8569
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


# create a cluster configuration on basic page, save
# open admin panel and check Cfg counter



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8132) Web console: A little re-design of Checkpointing section

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8132.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: A little re-design of Checkpointing section 
> -
>
> Key: IGNITE-8132
> URL: https://issues.apache.org/jira/browse/IGNITE-8132
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.5
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
>  !screenshot-1.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8132) Web console: A little re-design of Checkpointing section

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8132:


Tested on master

> Web console: A little re-design of Checkpointing section 
> -
>
> Key: IGNITE-8132
> URL: https://issues.apache.org/jira/browse/IGNITE-8132
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.5
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
>  !screenshot-1.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8235) Implement execution of selected part of SQL query

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8235:


Tested on master

> Implement execution of selected part of SQL query
> -
>
> Key: IGNITE-8235
> URL: https://issues.apache.org/jira/browse/IGNITE-8235
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.6
>
>
> If we had 3 SQL rows in the notebook, and selected one and clicked execute. 
> We should only execute the highlighted row. If no row is highlighted, then 
> all rows should be executed. That's a standard feature of graphical SQL tools.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8235) Implement execution of selected part of SQL query

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8235.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Implement execution of selected part of SQL query
> -
>
> Key: IGNITE-8235
> URL: https://issues.apache.org/jira/browse/IGNITE-8235
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.6
>
>
> If we had 3 SQL rows in the notebook, and selected one and clicked execute. 
> We should only execute the highlighted row. If no row is highlighted, then 
> all rows should be executed. That's a standard feature of graphical SQL tools.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8267) Web console: cluster client connector configuration fields are too narrow

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8267.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: cluster client connector configuration fields are too narrow
> -
>
> Key: IGNITE-8267
> URL: https://issues.apache.org/jira/browse/IGNITE-8267
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.6
>
> Attachments: image-2018-04-16-11-31-15-136.png, screenshot-1.png
>
>
> *How to reproduce:*
> 1. Go to advanced cluster configuration.
> 2. Open "client connector configuration" section.
> *What happens:*
> "Socket send buffer size" and "Socket receive buffer size" field labels wrap 
> to second line.
>  !image-2018-04-16-11-31-15-136.png! 
> *What should happen:*
> "Socket send buffer size" and "Socket receive buffer size" field labels 
> should be on a single line.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8267) Web console: cluster client connector configuration fields are too narrow

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8267:


Tested on master

> Web console: cluster client connector configuration fields are too narrow
> -
>
> Key: IGNITE-8267
> URL: https://issues.apache.org/jira/browse/IGNITE-8267
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.6
>
> Attachments: image-2018-04-16-11-31-15-136.png, screenshot-1.png
>
>
> *How to reproduce:*
> 1. Go to advanced cluster configuration.
> 2. Open "client connector configuration" section.
> *What happens:*
> "Socket send buffer size" and "Socket receive buffer size" field labels wrap 
> to second line.
>  !image-2018-04-16-11-31-15-136.png! 
> *What should happen:*
> "Socket send buffer size" and "Socket receive buffer size" field labels 
> should be on a single line.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8334) Web console: add ability to show/hide password field value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8334.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: add ability to show/hide password field value
> --
>
> Key: IGNITE-8334
> URL: https://issues.apache.org/jira/browse/IGNITE-8334
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Fix For: 2.6
>
> Attachments: eye-icon-close.svg, eye-icon-open.svg
>
>
> The ability to toggle password inputs value visibility will improve the UX of 
> several forms. Since most of password inputs are located on sign-in and 
> profile pages, for now it'll be enough to update inputs used on these pages 
> only.
> The button should:
> 1. Has opened eye icon when password value is visible.
> 2. Has closed eye icon when password value is hidden (i.e. default dots).
> 3. Be placed at the right side of the input and to the right of validation 
> error message. That means that error message will be place a bit more to the 
> left compared to text inputs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8334) Web console: add ability to show/hide password field value

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8334:


Tested on master

> Web console: add ability to show/hide password field value
> --
>
> Key: IGNITE-8334
> URL: https://issues.apache.org/jira/browse/IGNITE-8334
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Ilya Borisov
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.6
>
> Attachments: eye-icon-close.svg, eye-icon-open.svg
>
>
> The ability to toggle password inputs value visibility will improve the UX of 
> several forms. Since most of password inputs are located on sign-in and 
> profile pages, for now it'll be enough to update inputs used on these pages 
> only.
> The button should:
> 1. Has opened eye icon when password value is visible.
> 2. Has closed eye icon when password value is hidden (i.e. default dots).
> 3. Be placed at the right side of the input and to the right of validation 
> error message. That means that error message will be place a bit more to the 
> left compared to text inputs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8142) Web Console: Fix change detection logic on configuration.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8142:


Tested on master

> Web Console: Fix change detection logic on configuration.
> -
>
> Key: IGNITE-8142
> URL: https://issues.apache.org/jira/browse/IGNITE-8142
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.5
>
> Attachments: ignite-8142.png
>
>
> How to reproduce:
>  # Input value in some EMPTY input.
>  # Delete content.
>  # Click on Profile link.
>  # You will see question about unsaved changes (see image attached).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8142) Web Console: Fix change detection logic on configuration.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8142.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web Console: Fix change detection logic on configuration.
> -
>
> Key: IGNITE-8142
> URL: https://issues.apache.org/jira/browse/IGNITE-8142
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.5
>
> Attachments: ignite-8142.png
>
>
> How to reproduce:
>  # Input value in some EMPTY input.
>  # Delete content.
>  # Click on Profile link.
>  # You will see question about unsaved changes (see image attached).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8214) Web console: add validation for Persistent + Swap file for data region configuration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8214:


Tested on master

> Web console: add validation for Persistent + Swap file for data region 
> configuration
> 
>
> Key: IGNITE-8214
> URL: https://issues.apache.org/jira/browse/IGNITE-8214
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.6
>
>
> The 'Swap file' option can be set only if 'Persistent Enable' is OFF.
> Please add corresponding validation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8214) Web console: add validation for Persistent + Swap file for data region configuration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8214.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: add validation for Persistent + Swap file for data region 
> configuration
> 
>
> Key: IGNITE-8214
> URL: https://issues.apache.org/jira/browse/IGNITE-8214
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
>
> The 'Swap file' option can be set only if 'Persistent Enable' is OFF.
> Please add corresponding validation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-8479) Web console: query text is empty on opening query section

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-8479.
--
Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: query text is empty on opening query section
> -
>
> Key: IGNITE-8479
> URL: https://issues.apache.org/jira/browse/IGNITE-8479
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>Priority: Major
> Fix For: 2.6
>
> Attachments: image-2018-05-14-16-39-34-686.png
>
>
> On the first second the query text is empty and then it appears.
>  !image-2018-05-14-16-39-34-686.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-8479) Web console: query text is empty on opening query section

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-8479:


Tested on master

> Web console: query text is empty on opening query section
> -
>
> Key: IGNITE-8479
> URL: https://issues.apache.org/jira/browse/IGNITE-8479
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.6
>
> Attachments: image-2018-05-14-16-39-34-686.png
>
>
> On the first second the query text is empty and then it appears.
>  !image-2018-05-14-16-39-34-686.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8568) Web Console: Add support for "collocated" query mode on Query screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8568:


 Summary: Web Console: Add support for "collocated" query mode on 
Query screen
 Key: IGNITE-8568
 URL: https://issues.apache.org/jira/browse/IGNITE-8568
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Vasiliy Sisko
 Fix For: 2.6


Ignite SQL engine supports special flag "collocated" that can improve 
performance of  SQL queries in special situations.

Lets add this flag to Query screen UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)