[jira] [Created] (IGNITE-12150) Ignite javadoc contains bogus links, copyright is outdated
Alexey Goncharuk created IGNITE-12150:
-
Summary: Ignite javadoc contains bogus links, copyright is outdated
Key: IGNITE-12150
URL: https://issues.apache.org/jira/browse/IGNITE-12150
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Ignite Javadoc contains links to {{http://agorbatchev.typepad.com}} which may
be broken and unnecessary. Also, the copyright year is hardcoded and outdated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12151) Load Cache: Failed to load bean in app context
Kurt Semba created IGNITE-12151: --- Summary: Load Cache: Failed to load bean in app context Key: IGNITE-12151 URL: https://issues.apache.org/jira/browse/IGNITE-12151 Project: Ignite Issue Type: Bug Components: binary, cache Affects Versions: 2.7.5 Environment: * Ubuntu 18.04 * Ignite server v2.7.5 - running in a docker container with the REST API module enabled * Ignite web-console: 2.7.0 - also running in a docker container * Ignite web-agent - downloaded from the web-console so I assume also using version 2.7.0 - not running in a docker container (properly connects to both the web-console as well as the cluster... until I kill my cluster ;) ) * MySQL DB: v5.7 running on a remote VM * IDE: Visual Studio Code (latest update) Reporter: Kurt Semba Attachments: Dockerfile, clientLoadCaches.log, cluster.log Hi team, I was following the instructions from [https://www.youtube.com/watch?v=SJ6h55VhUBI] and onwards to use the web-console and web-agent to import data from a MySQL DB. It all works fine until I download the cluster configuration Java project from the web-console and try to run the "LoadCaches" java file in my IDE. The client (LoadCaches code) fails with an "IgniteCheckedException: Failed to connect to node" exception but more importantly, the ignite cluster crashes as well with an "IgniteException: Failed to load bean in application context" exception. See both logs attached. The parts where I diverged from the demo video series: * I did not tweak the cluster config using the web-console - just kept it as it was auto-created by the web-console * I edited /src/main/resources/META-INF/ImportedCluster-client.xml and configured the IP of my Ignite cluster (both the ignite cluster and the IDE code are running on the same server, but using the default 127.0.0.1 didn't connect) * I edited the pom.xml file to make the Java code use the latest v2.7.5 libraries to load the cache (since the cluster is also running this version) Do I have to somehow pre-stage the cluster / cache with the DB table I'm trying to import? I was hoping that the web-console would do that when I use the "Import from Database" wizard? Maybe the version mismatch between web-console (2.7.0) and cluster (2.7.5) is an issue? Thanks Kurt -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: Non-blocking PME discussion, ASF Slack, September 10, 13.00 (MSK)
Hello Anton, I doubt that Slack channel is a good way to discuss/make decisions on such an important topic. Changes in PME are usually the hard ones, and slack is kind of a synchronous communication channel - with no known context it will be hard to give appropriate feedback. Do you have something to make Igniters familiar with beforehand? пн, 9 сент. 2019 г. в 09:01, Anton Vinogradov : > Igniters, > > As far as you may know, we have blocking PME now. > It means that the upcoming operation's latency may be increased or already > started operations can be canceled. > > I've done some homework and found it's possible to have almost non-blocking > PME (fully non-blocked in some cases). > I'd like to discuss found with the community before starting the > implementation. > > Let's have a first community-wide discussion using the ASF Slack. > I've created the channel [1] and going to explain found tomorrow (September > 10) 13.00 (MSK). > Disclaimer: We'll use the Russian language this time. > > [1] https://the-asf.slack.com/messages/CMTJBREKD >
Re: Non-blocking PME discussion, ASF Slack, September 10, 13.00 (MSK)
Alexey, thanks for pointing this. I've prepared the presentation with explanation how it works now and with a set of proposals. So, I'm not going to have a chat with somebody tomorrow. I'll, as usual, will start a video call and share the screen with the presentation, like a regular webinar. Sounds good? BTW, I'll be at GG office, you may join me via the internet or in the same room. On Mon, Sep 9, 2019 at 1:34 PM Alexey Goncharuk wrote: > Hello Anton, > > I doubt that Slack channel is a good way to discuss/make decisions on such > an important topic. Changes in PME are usually the hard ones, and slack is > kind of a synchronous communication channel - with no known context it will > be hard to give appropriate feedback. Do you have something to make > Igniters familiar with beforehand? > > пн, 9 сент. 2019 г. в 09:01, Anton Vinogradov : > > > Igniters, > > > > As far as you may know, we have blocking PME now. > > It means that the upcoming operation's latency may be increased or > already > > started operations can be canceled. > > > > I've done some homework and found it's possible to have almost > non-blocking > > PME (fully non-blocked in some cases). > > I'd like to discuss found with the community before starting the > > implementation. > > > > Let's have a first community-wide discussion using the ASF Slack. > > I've created the channel [1] and going to explain found tomorrow > (September > > 10) 13.00 (MSK). > > Disclaimer: We'll use the Russian language this time. > > > > [1] https://the-asf.slack.com/messages/CMTJBREKD > > >
[jira] [Created] (IGNITE-12152) Disk space not getting released after deleting rows from a table or after records expired with expiration policy
shivakumar created IGNITE-12152: --- Summary: Disk space not getting released after deleting rows from a table or after records expired with expiration policy Key: IGNITE-12152 URL: https://issues.apache.org/jira/browse/IGNITE-12152 Project: Ignite Issue Type: Bug Components: documentation, persistence, sql Affects Versions: 2.7 Reporter: shivakumar To reproduce, create a cache group and create a sql table using that cache group, then insert considerable rows of records to the table, monitor the disk space usage, now stop inserting records and delete records from the table using *DELETE FROM table; (not a drop table operation)* once this is done the *select count(*) from table;* shows the count 0 but after this when disk space is monitored it will be in the same usage level as it is in the level before rows deletion. When I start inserting records again, the new records re-used the space occupied by the deleted records but still, it is not a good idea to unnecessarily hold disk resource. The same can be reproduced by configuring cache expiry policy (CreatedExpiryPolicy) where after records expires it will not be visible in sql query (select * from table) but still it will hold disk resource. -- This message was sent by Atlassian Jira (v8.3.2#803003)
Start contributing Ignite
Hello, team! My name is Lev, I'm Java developer from Russia, Nizhny Novgorod. I'd be kindly glad to join your community and start contributing Ignite. Could you please grant to my Jira account 'levagafonov' contributor permissions? Best Regards, Lev Agafonov
Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)
Igniters, I just pushed the last ticket to ignite-2.7.6 branch; looks like we are ready for the next iteration. Given that Dmitriy Pavlov will be unavailable till the end of this week, I will take over the release. TC re-run is started. чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: > Hi Igniters, > > I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, fix > already in master and ignite-2.7.6 > > On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi Alexey, > > > > I think that I will finish work on the fix tomorrow. Fix already > completed > > but I need to get VISA from TC bot. > > > > On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk < > > alexey.goncha...@gmail.com> wrote: > > > >> Folks, it looks like I was overly optimistic with the estimates for the > >> mentioned two tickets. > >> > >> Dmitriy, Anton, > >> Can you share your vision when the issues will be fixed? Perhaps, it > makes > >> sense to release 2.7.6 with the already fixed issues and schedule 2.7.7? > >> Neither of them is a regression, so it's ok to release 2.7.6 as it is > now. > >> > >> Thoughts? > >> > >> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk < > alexey.goncha...@gmail.com > >> >: > >> > >> > Yes, my bad, forgot to include the link. That's the one. > >> > > >> > пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov : > >> > > >> >> Alexey, > >> >> > >> >> Does the issue [1] is related to this [2] discussion on the > user-list? > >> >> If yes, I think it is very important to include these fixes to 2.7.6. > >> >> > >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12127 > >> >> [2] > >> >> > >> > http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html > >> >> > >> >> On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov > >> >> wrote: > >> >> > > >> >> > Alexey, > >> >> > > >> >> > Looks like important fixes, better to include them. > >> >> > > >> >> > пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk < > >> >> alexey.goncha...@gmail.com>: > >> >> > > >> >> > > Igniters, > >> >> > > > >> >> > > Given that the RC1 vote did not succeed and we are still waiting > >> for > >> >> a few > >> >> > > minor fixes, may I suggest including these two tickest to the > 2.7.6 > >> >> scope? > >> >> > > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12127 > >> >> > > https://issues.apache.org/jira/browse/IGNITE-12128 > >> >> > > > >> >> > > The first one has been already reported on the dev-list [1], the > >> >> second one > >> >> > > may cause a state when an Ignite node cannot start on existing > >> >> persisted > >> >> > > data. Looking at the tickets, the fixes should be reasonably > easy, > >> so > >> >> it > >> >> > > should not shift 2.7.6 release timeline much. > >> >> > > > >> >> > > Thoughts? > >> >> > > > >> >> > > ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov < > nizhi...@apache.org > >> >: > >> >> > > > >> >> > > > Separate repos for different Spark version is a good idea for > me. > >> >> > > > Anyway, can you help with Spark version migration, for now? > >> >> > > > > >> >> > > > В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет: > >> >> > > > > Maybe the best solution today add for each new version of > Spark > >> >> the > >> >> > > > > sub-module (Spark-2.3, Spark-2.4) or the separate repository > >> with > >> >> > > modules > >> >> > > > > for each version or another way with separate repository and > >> >> different > >> >> > > > > branches like in > >> >> > > https://github.com/datastax/spark-cassandra-connector > >> >> > > > > > >> >> > > > > 3 ways to support different versions with the different costs > >> of > >> >> > > support > >> >> > > > > > >> >> > > > > In the case of separate repository I could help, for example > >> >> > > > > > >> >> > > > > ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov < > >> nizhi...@apache.org > >> >> >: > >> >> > > > > > >> >> > > > > > Hello, Alexey. > >> >> > > > > > > >> >> > > > > > > But the > >> >> > > > > > > compatibility with Spark 2.3 will be broken, isn't it? > >> >> > > > > > > >> >> > > > > > Yes. > >> >> > > > > > > >> >> > > > > > > Do you have any > >> >> > > > > > > plans to support the different version of Spark without > >> >> loosing > >> >> > > your > >> >> > > > > > > >> >> > > > > > unique > >> >> > > > > > > expertise in Spark-Ignite integration? > >> >> > > > > > > >> >> > > > > > What do you mean by "my unique expertise"? :) > >> >> > > > > > > >> >> > > > > > How do you see support of several Spark version? > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > В Ср, 28/08/2019 в 14:29 +0300, Alexey Zinoviev пишет: > >> >> > > > > > > Dear Nikolay Izhikov > >> >> > > > > > > Are you going to update the Ignite-Spark integration for > >> >> Spark 2.4. > >> >> > > > But > >> >> > > > > > > >> >> > > > > > the > >> >> > > > > > > compatibility with Spark 2.3 will be broken, isn't it? Do > >> you > >> >> have > >
[jira] [Created] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.
Sergey Antonov created IGNITE-12153: --- Summary: Control.sh add test for checking that help and cache help output are not broken. Key: IGNITE-12153 URL: https://issues.apache.org/jira/browse/IGNITE-12153 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 We should store "ideal" outputs in resorces and compare with current. -- This message was sent by Atlassian Jira (v8.3.2#803003)
help on IGNITE-11894
Hello, I need some help on the ticket https://issues.apache.org/jira/browse/IGNITE-11894 since this is my time working on ignite code base. I am not able to move the ticket in progress and would like to chat with a developer on what is expected for the ticket. Is there a slack channel or message client the team uses to communicate? Thanks, Amit
Re: help on IGNITE-11894
Hell, Amit. You can write you question here, on the dev-list or in the ticket. I think, Ignite community will help you with this and ongoing contribution. Welcome! В Пн, 09/09/2019 в 11:14 -0700, Amit Chavan пишет: > Hello, > > I need some help on the ticket > https://issues.apache.org/jira/browse/IGNITE-11894 since this is my time > working on ignite code base. I am not able to move the ticket in progress > and would like to chat with a developer on what is expected for the ticket. > Is there a slack channel or message client the team uses to communicate? > > Thanks, > Amit signature.asc Description: This is a digitally signed message part
[MTCGA]: new failures in builds [4582062] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Recently contributed test failed in master-nightly CheckpointFailBeforeWriteMarkTest.testCheckpointFailBeforeMarkEntityWrite https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7973963335094119083&branch=%3Cdefault%3E&tab=testDetails Changes may lead to failure were done by - alexey goncharuk https://ci.ignite.apache.org/viewModification.html?modId=890284 - anton kalashnikov https://ci.ignite.apache.org/viewModification.html?modId=890291 - 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 08:34:20 10-09-2019
