[jira] [Created] (IGNITE-13979) .NET: Modernize examples

[Pavel Tupitsyn (Jira)]

Pavel Tupitsyn created IGNITE-13979:
---

 Summary: .NET: Modernize examples
 Key: IGNITE-13979
 URL: https://issues.apache.org/jira/browse/IGNITE-13979
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.11


Rework and modernize Ignite.NET examples:
* Refactor to .NET Core
* One project per example to run with {{dotnet run}} or from the IDE
* NuGet-based (similar to how Java examples are Maven-based)



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

[jira] [Created] (IGNITE-13978) Ignite 3 alpha Unix binary opens on click instead of being downloaded

[Valentin Kulichenko (Jira)]

Valentin Kulichenko created IGNITE-13978:


 Summary: Ignite 3 alpha Unix binary opens on click instead of 
being downloaded
 Key: IGNITE-13978
 URL: https://issues.apache.org/jira/browse/IGNITE-13978
 Project: Ignite
  Issue Type: Bug
  Components: website
Reporter: Valentin Kulichenko
 Fix For: 3.0.0-alpha1


1. Go to binary downloads: https://ignite.apache.org/download.cgi#binaries
2. Locate the 3.0.0 alpha and click on the download for Unix.
3. Expected: {{ignite}} file is downloaded. Actual: the file opens up in the 
same window.



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

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

[dpavlov . tasks]

Hi Igniters,

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

 *New Critical Failure in master Cache (Restarts) 1 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
 No changes in the build

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

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 02:31:21 12-01-2021 

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

[Никита Сафонов]

Hi everyone,

I'm finally back and ready to continue the work, sorry for this delay.
Maxim, thanks once again for preparing a list of important documentation
issues.

Regards,
Nikita

чт, 7 янв. 2021 г. в 13:47, Nikolay Izhikov :

> Hello.
>
> I prepared docs [1] for the following tickets
>
> Denis, can you, please, take a look?
>
> > https://issues.apache.org/jira/browse/IGNITE-13488 - Add command to
> control.(sh|bin) to get an arbitrary Metric
> > https://issues.apache.org/jira/browse/IGNITE-13426 - Add command to
> control.(sh|bin) to get an arbitrary SystemView
> > https://issues.apache.org/jira/browse/IGNITE-13380 - Output
> IgniteSystemProperties via ignite.sh
>
> [1] https://github.com/apache/ignite/pull/8630
>
> > 29 дек. 2020 г., в 21:42, Denis Magda  написал(а):
> >
> > Thanks, Maksim,
> >
> > Considering that most of the contributors will be on holidays through Jan
> > 10th, it's highly unlikely that all documentation tickets will be ready
> by
> > Jan 18th (the vote date).
> >
> > Anyway, Nikita confirmed that he'll be actively working on the tickets
> > starting Jan 11th. As for me, unfortunately, I have no time for
> > contributions in January.
> >
> > Special thanks for preparing a list of resolved but undocumented
> features.
> > Most of those just need to be donated from the GridGain documentation
> page.
> > I'll take care of those.
> >
> > -
> > Denis
> >
> >
> > On Tue, Dec 29, 2020 at 12:43 AM Maxim Muzafarov 
> wrote:
> >
> >> Folks,
> >>
> >> 1.
> >> I've prepared the list of unhandled important documentation issues for
> >> the 2.10 release, please check the wiki page link [1]. Note, that some
> >> of the important (from my point of view) documentation issues even not
> >> created.
> >>
> >> 2.
> >> Here is the list of resolved issues which seems to be documented, but
> >> an appropriate documentation task doesn't exist. Should we create
> >> appropriate documentation issues for them? Check the list [3].
> >>
> >> 3.
> >> Some of the documentation pages must be completed prior to 2.10
> >> release or removed, right? Check the [2] page for example.
> >>
> >>
> >> Denis, Nikita
> >>
> >>> So we should probably allocate more time for this work.
> >> Let's start the work, track the progress and looks at how it goes.
> >> I'll try to ask some folks for the help with documentation and also
> >> plan to help with the issues by myself. We can shift the dates if it's
> >> necessary, but currently, I see no reasons.
> >>
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10#ApacheIgnite2.10-Documentationtasksforimportantfeatures
> >> [2] https://ignite.apache.org/docs/latest/cpp-specific/
> >> [3] The list of issues without documentation tasks :
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13488
> >> Add command to control.(sh|bin) to get an arbitrary Metric
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13467
> >> Add events for snapshot operation state
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13535
> >> Support cluster snapshot security permissions
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13426
> >> Add command to control.(sh|bin) to get an arbitrary SystemView
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13327
> >> Add a metric for processed keys when rebuilding indexes.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13310
> >> Add tracing of SQL queries.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-12380
> >> Add event for node validation failure.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-7623
> >> Thin client Java API - async API
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13380
> >> Output IgniteSystemProperties via ignite.sh
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-11731
> >> CPP: Implement Cluster API
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-13308
> >> C++: Thin client transactions
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-12754
> >> .NET: Thin Client: Service invocation
> >>
> >> On Fri, 25 Dec 2020 at 22:43, Никита Сафонов  >
> >> wrote:
> >>>
> >>> Hi Denis, Maxim,
> >>>
> >>> I'd like to clarify that I'm pretty sure to complete the tasks below
> >> before
> >>> the voting date:
> >>>
> >>> https://issues.apache.org/jira/browse/IGNITE-13659
> >>> https://issues.apache.org/jira/browse/IGNITE-13796
> >>>
> >>> I'll start to work on them right after the long Russian NY holidays.
> >>> But I'm not quite sure that we'll meet the deadline with other tickets
> >>> that should be on the list.
> >>> So we should probably allocate more time for this work.
> >>>
> >>> I'd be glad to get your opinion on this.
> >>>
> >>> Regards,
> >>> Nikita
> >>>
> >>> сб, 19 дек. 2020 г. в 11:39, Maxim Muzafarov :
> >>>
>  Denis, Nikita
> 
>  Yes, the list of important documentation issues will be ready prior to
>  the scope freeze date. I'll prepare it.
> 
>  I mean if we want to start working right now on 

[jira] [Created] (IGNITE-13977) Code enhancement after review of encryption persistent storage

[Vladislav Pyatkov (Jira)]

Vladislav Pyatkov created IGNITE-13977:
--

 Summary: Code enhancement after review of encryption persistent 
storage
 Key: IGNITE-13977
 URL: https://issues.apache.org/jira/browse/IGNITE-13977
 Project: Ignite
  Issue Type: Bug
Reporter: Vladislav Pyatkov


# There are a lot of difficult code snipped in `GridCacheOffheapManager` where 
the type of page choosing.
 # CacheGroupReencryptionTest.testPhysicalRecoveryWithUpdates test is flaky, 
when checkpoint is triggered before expected.

 



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

[jira] [Created] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss

[Ilya Kasnacheev (Jira)]

Ilya Kasnacheev created IGNITE-13976:


 Summary: WAL disable/enable with node restarts results in 
mismatching state, data loss
 Key: IGNITE-13976
 URL: https://issues.apache.org/jira/browse/IGNITE-13976
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.9.1
Reporter: Ilya Kasnacheev
Assignee: Ilya Kasnacheev


If you try to enable/disable WAL on unstable topology, you will get to state 
when WAL status is undefined, nodes might have different wall status and the 
only way to fix it is to restart the cluster, which will lead to data loss 
because ignite removes data if WAL is disabled on restart.

See the attached reproducer.



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

[GitHub] [ignite-nodejs-thin-client] asfgit closed pull request #2: IGNITE-13794 Partition awareness for Node.js

[GitBox]

asfgit closed pull request #2:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/2


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (IGNITE-13975) Validate that tables beind joined have the same partition distribution

[Stanislav Lukyanov (Jira)]

Stanislav Lukyanov created IGNITE-13975:
---

 Summary: Validate that tables beind joined have the same partition 
distribution
 Key: IGNITE-13975
 URL: https://issues.apache.org/jira/browse/IGNITE-13975
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Reporter: Stanislav Lukyanov


To be able to join two PARTITIONED tables one needs to perform the JOIN on an 
affinity key, and also to make sure that the tables have the same partition 
distribution - otherwise, the result will be incorrect.

Validation of whether the affinity key is being used for JOIN is to be done in 
https://issues.apache.org/jira/browse/IGNITE-13019.

The goal of this ticket is to add validation of the partition distribution.

Whenever a JOIN of PARTITIONED tables is being done, the SQL engine needs to 
ensure that
 * The tables use the same affinity function
 * The tables have the same number of partitions
 * The tables have the same node filters

Same is for when REPLICATED tables are used and 
`treatReplicatedAsPartitioned=true` (see 
https://issues.apache.org/jira/browse/IGNITE-8732).



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

[jira] [Created] (IGNITE-13974) onDisconnected() method does not get called for thinClient on "kubectl delete pod"

[Vishwas (Jira)]

Vishwas created IGNITE-13974:


 Summary: onDisconnected() method does not get called for 
thinClient on "kubectl delete pod"
 Key: IGNITE-13974
 URL: https://issues.apache.org/jira/browse/IGNITE-13974
 Project: Ignite
  Issue Type: Bug
  Components: jdbc, thin client
Affects Versions: 2.9
 Environment: k8s
Reporter: Vishwas


Below is the test I am performing:
1) Bring up ignite on k8s cluster 2 pods of Ignite server are running.

2) Connect via sqlline to the Ignite Cluster (connect via k8s service):
{code:java}
./sqlline.sh --verbose=true -u 
"jdbc:ignite:thin://ignite-service.ignite.svc.cluster.local:10800" -n test_user 
-p test_user
{code}
3) Restart the pod on which sqlline connection is made
{code:java}
kubectl delete pod   
{code}

4) *Observation ClientListenerAbstractConnectionContext.onDisconnected() is not 
getting called.* 

*This causes leak of the authenticationContext as onSessionExpired method does 
not get called.*
 
+Note:+ 

When I tried the same scenario on a windows machine, I did not hit the issue 
and the onDisconnected() method is getting called.
 For step 3 above, I connected to ignite visor and ran the kill -k command on 
windows. 
 When I ran the same kill -k command on k8s cluster from visor, I do not see 
this issue.

 

What should be the behaviour when "kubectl delete pod" is triggered ? I think 
onDisconnected() should get called.

 



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

[jira] [Created] (IGNITE-13973) Calcite integration. Query get frozen if assertion error was thrown

[Konstantin Orlov (Jira)]

Konstantin Orlov created IGNITE-13973:
-

 Summary: Calcite integration. Query get frozen if assertion error 
was thrown
 Key: IGNITE-13973
 URL: https://issues.apache.org/jira/browse/IGNITE-13973
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Konstantin Orlov


Need to fix the issue and verify that assertion error on any stage of query 
planning/execution (this includes fragment splitting phase) doesn't lead to 
freezes.

Mentioned problem could be reproduced for example as follow:
1) place fake {{assert false}} inside {{IgniteMergeJoin(RelInput input)}}
2) run {{CalciteQueryProcessorTest.query2()}}



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

[jira] [Created] (IGNITE-13972) Clear the item id before moving the page to the reuse bucket

[Anton Kalashnikov (Jira)]

Anton Kalashnikov created IGNITE-13972:
--

 Summary: Clear the item id before moving the page to the reuse  
bucket
 Key: IGNITE-13972
 URL: https://issues.apache.org/jira/browse/IGNITE-13972
 Project: Ignite
  Issue Type: Task
Reporter: Anton Kalashnikov


There is assert - 'Incorrectly recycled pageId in reuse 
bucket:'(org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList#takeEmptyPage).
 This assert sometimes fails. The reason is not clear because the same 
condition checked before putting this page in to reuse bucket. (Perhaps we have 
more than 1 link to this page?)

There is an idea to reset item id to 1 before the putting page to reuse bucket 
in order of decreasing the possible invariants which can break this assert. It 
is already true for all data pages but item id can be still more than 1 if it 
is not a data page(ex. inner page).

After that, we can change this assert from checking the range to checking the 
equality to 1 which theoretically will help us detect the problem fastly.

Maybe it is also not a bad idea to set itemId to an impossible value(ex. 0 or 
255). Then we can add the assert on every taking from the free list which 
checks that itemId more than 0 and if it is false that means we have a link to 
the reuse bucket page from the bucket which is not reused. Which is a bug.



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

[jira] [Created] (IGNITE-13971) Merge Calcite SQL engine to master

[Yury Gerzhedovich (Jira)]

Yury Gerzhedovich created IGNITE-13971:
--

 Summary: Merge Calcite SQL engine to master
 Key: IGNITE-13971
 URL: https://issues.apache.org/jira/browse/IGNITE-13971
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Reporter: Yury Gerzhedovich


The main goal is start development on a ticket-based approach when we could 
merge each new ticket to master separately, instead of integration branch 
approach.  Also the new engine will be available to users to start using and 
testing it.

We need to ensure the new SQL engine based on Calcite is not affect the current 
implementation, discuss it on a dev list and merge it to master branch.




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

[jira] [Created] (IGNITE-13970) [Ducktape: Thin client] Cache API Test

[Anton Vinogradov (Jira)]

Anton Vinogradov created IGNITE-13970:
-

 Summary: [Ducktape: Thin client] Cache API Test
 Key: IGNITE-13970
 URL: https://issues.apache.org/jira/browse/IGNITE-13970
 Project: Ignite
  Issue Type: Sub-task
Reporter: Anton Vinogradov


Need to check put/get (atomic, tx) and other cache API works while the user 
uses TC.



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

[jira] [Created] (IGNITE-13969) Thin client test [umbrella]

[Anton Vinogradov (Jira)]

Anton Vinogradov created IGNITE-13969:
-

 Summary: Thin client test [umbrella]
 Key: IGNITE-13969
 URL: https://issues.apache.org/jira/browse/IGNITE-13969
 Project: Ignite
  Issue Type: Task
Reporter: Anton Vinogradov


Ensure Thin client work.
Check the whole TC API.



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

[jira] [Created] (IGNITE-13968) Add documentation for snapshot events

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-13968:


 Summary: Add documentation for snapshot events
 Key: IGNITE-13968
 URL: https://issues.apache.org/jira/browse/IGNITE-13968
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov


The documentation pages must be added for newly created snapshot events:

EVT_CLUSTER_SNAPSHOT_STARTED,
EVT_CLUSTER_SNAPSHOT_FINISHED,
EVT_CLUSTER_SNAPSHOT_FAILED



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

[jira] [Created] (IGNITE-13967) Refactor and imrpove performance of python thin client marshaller

[Ivan Daschinskiy (Jira)]

Ivan Daschinskiy created IGNITE-13967:
-

 Summary: Refactor and imrpove performance of python thin client 
marshaller
 Key: IGNITE-13967
 URL: https://issues.apache.org/jira/browse/IGNITE-13967
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Reporter: Ivan Daschinskiy
Assignee: Ivan Daschinskiy


Currently implemented serialization has questionable design and suffers from 
some problems
1. It is tightly coupled with Client object
2. It doesn't use protocol feature that total length of message is in the 
header,
thus it constantly load from Client some data instead of iteration over byte 
array.
3. It uses some tricky hacks and sometimes new connection is created when 
deserializing object.
4. It constantly allocates bytes (immutable data structure).


I suggest to rewrite serialization and deserialization:
1. Pass to corresponding methods specific SerDe context + BytesIO
2. Context can be sync and async and contains specific flags and methods for 
loading/uploading binary object schemas
3. Refactor Client in order to retrieve full packet from socket at once then 
pass full packet futher.

These steps can significantly improve performance, reduce amount of allocations 
and give
foundation for implementing asyncio version of client.



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

[jira] [Created] (IGNITE-13966) Change copyrights to 2021

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-13966:


 Summary: Change copyrights to 2021
 Key: IGNITE-13966
 URL: https://issues.apache.org/jira/browse/IGNITE-13966
 Project: Ignite
  Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov


The copyrights of 2020 must be changed to 2021.



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

[jira] [Created] (IGNITE-13964) Query cancellation freezes on local lazy queries

[Konstantin Orlov (Jira)]

Konstantin Orlov created IGNITE-13964:
-

 Summary: Query cancellation freezes on local lazy queries
 Key: IGNITE-13964
 URL: https://issues.apache.org/jira/browse/IGNITE-13964
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.9.1
Reporter: Konstantin Orlov
Assignee: Konstantin Orlov


The reason is a query cancellation that acquires an iterator's lock to check 
the availability of a next row and thus update a state of the cursor to prevent 
unnecessary request cancelation. But the lock is already held by a query thread 
to fetch a next page, so the cancellation is forced to wait till the page will 
be completely prefetched.

 



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

Re: Apache Ignite Extensions TeamCity project

[Petr Ivanov]

Hi.


I've refactored the hierarchy of the project and moved it here: 
https://ci.ignite.apache.org/project/IgniteExtensions_Tests?mode=builds 

Check your permissions, please.

> On 11 Jan 2021, at 01:01, Saikat Maitra  wrote:
> 
> Hi,
> 
> We had a project for IgniteExtensions under Tests main project in TeamCity.
> 
> https://ci.ignite.apache.org/project.html?projectId=Tests_IgniteExtensions
> 
> I am no longer able to access the IgniteExtensions project.
> 
> Was it refactored and moved to another location?
> 
> Regards,
> Saikat