Re: Cluster name
Hi, The community has just voted to phase out Ignite Web Console: https://issues.apache.org/jira/browse/IGNITE-13038 GridGain's version of Web Console incorporates all the features of Ignite counterpart and should support the feature you are checking out. Feel free to switch to that tool or another monitoring solution. - Denis On Tue, May 19, 2020 at 12:29 PM lovellmathews wrote: > Hi - Just checking if this feature of naming a cluster from the web console > has been added now? If yes how do we do it? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
[RESULT][VOTE] Stop Maintenance of Ignite Web Console
Igniters, The vote is over [1] with a decision to phase out Ignite Web Console by moving to a separate repository and stopping its development/maintenance officially. The following PMC members cast +1 binding votes: - Saikat Maitra - Alexey Zinoviev - Nikolay Izhikov There are no -1 votes thus we can proceed with the tool discontinuation procedure [2]. [1] http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Stop-Maintenance-of-Ignite-WebConsole-td47451.html [2] https://issues.apache.org/jira/browse/IGNITE-13038 - Denis
[jira] [Created] (IGNITE-13038) Phase out Ignite Web Console
Denis A. Magda created IGNITE-13038: --- Summary: Phase out Ignite Web Console Key: IGNITE-13038 URL: https://issues.apache.org/jira/browse/IGNITE-13038 Project: Ignite Issue Type: Improvement Reporter: Denis A. Magda Fix For: 2.9 The community voted to stop the development and maintenance of Ignite Web Console: The following needs to be done: * Move the tool's source code from the Ignite core to its own repository (https://github.com/apache/ignite-web-console) * Update the repository description highlighting that the tool is no longer supported by the community. * Unlist Web Console documentation from the navigation and main menus. Do NOT remove as long as there are many pages referring to the docs. Just hide. * Put a callout on all the hidden documentation pages saying that the tool's source code is archived (provide a reference to the repo). -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Stop Maintenance of Ignite WebConsole
The vote is closed. Thanks to everyone who cast a vote. I'll share the results shortly. - Denis On Wed, May 13, 2020 at 2:22 AM Вячеслав Коптилин wrote: > +1 > > Thanks, > S. > > ср, 13 мая 2020 г. в 08:48, Nikolay Izhikov : > > > +1 > > > > ср, 13 мая 2020 г., 07:35 Alexey Zinoviev : > > > > > +1 > > > > > > ср, 13 мая 2020 г., 5:52 Saikat Maitra : > > > > > > > +1 > > > > > > > > Regards > > > > Saikat > > > > > > > > On Tue, 12 May 2020 at 7:03 PM, Denis Magda > wrote: > > > > > > > > > Igniters, > > > > > > > > > > As it was discussed earlier [1], it feels like we abandoned the > > > > development > > > > > and maintenance of Ignite WebConsole. The users keep creating > tickets > > > for > > > > > improvements and report issues, while the backlog only keeps > growing > > > with > > > > > no reaction on our end. > > > > > > > > > > With this vote, we hope to put WebConsole's development and > > maintenance > > > > on > > > > > hold *officially* by moving it to a separate Ignite repository and > > > > closing > > > > > all WebConsole-related tickets with a proper maintenance > > > discontinuation > > > > > notice. That's a gentle phase-out. If anybody joins the community > and > > > > > decides to resurrect the project they will have a chance to do > that. > > > > > Otherwise, WebConsole ends up on a graveyard eventually. > > > > > > > > > > Please cast your vote: > > > > > +1 - to discontinue Ignite WebConsole's development and maintenance > > by > > > > > moving to a separate Ignite repository. > > > > > -1 - against this course of action. > > > > > > > > > > I'll let this vote last for 7 days and close it on May 18th. > > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Ignite-WebConsole-Deprecation-td47259.html > > > > > > > > > > - > > > > > Denis > > > > > > > > > > > > > > >
Re: Cluster name
Hi - Just checking if this feature of naming a cluster from the web console has been added now? If yes how do we do it? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Ignite Task deployment questions
Hi Marble, Same with this question. Please forward it to the Ignite user list ( https://ignite.apache.org/community/resources.html). - Denis On Tue, May 19, 2020 at 1:38 AM Marble wrote: > Hi Guru, > > Even check the ignite deployment documentation, but still not much > understand the overall picture. > > Say I have ready 3 nodes cluster with zookeeper discovery. Now I have a > task > want to deploy to this cluster, in flink, there is a console to provide > upload, stop/run/delete and monitoring this tasks, how ignite achieve this > deployment? Is there a detail step by step case? thanks. > > If we achieve this by deploy a jar to each node ./libs folder, and when > instance startup it will lunch this task, but once we have new changes on > this task, does it mean each deployment need restart the instances? Seems > not a good solution. > > Another query is, with Ignite ignite = Ignition.Ignite(); ignite.start(); > in > this ignite instance, how can I connect to the remote cluster, where to set > the remote connection string, such as host:port:user:pwd, like JDBC? and > run > the example/debug with this cluster environment. > > new to the ignite, need help, thanks a lot. > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
Re: Compute Task deployment Queries
Hi Marble, Please forward these questions to the Ignite user list ( https://ignite.apache.org/community/resources.html). The dev list is used to discuss Ignite contribution and development topics. - Denis On Tue, May 19, 2020 at 1:38 AM Marble wrote: > Hi Guru, > > I have ready 3 nodes cluster with zookeeper, have questions/confuse on the > task deployment. > > Like flink, there is a web console to upload the jar file and control the > job run/stop/delete, how our ignite tasks deploy to my cluster? From the > doc, still not much understand the full pictures, need help, thanks. > > And another query is, in debug/dev environment, How I can connect to this > cluster instances? > Ignite ignite = Ignition.Ignite(); ignite.start(); where to set the > connection string of the cluster instance? How can I run the tasks on the > cluster instance, instead of with the provided example local instance > startup? > > Thanks a lot. > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
[ISSUE] Enum vs BinaryEnum
Hi, I am experiencing an issue related to enum data types in ignite cluster, the following message is displayed during object deserialization: Caused by: class org.apache.ignite.binary.BinaryObjectException: Unexpected field type [pos=33, expected=Enum, actual=Enum] At first I was confused by the message but looking at the code I can see that there are two types of enum FIELD_TYPE_NAMES[GridBinaryMarshaller.ENUM] = "Enum"; FIELD_TYPE_NAMES[GridBinaryMarshaller.BINARY_ENUM] = "Enum"; ( https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java ) I am updating that field in two different ways, one is directly using cache.put and the other is using an SQL update query. I wonder if that is the cause of the issue, but I don't understand why it would be, since both use the same classes and enum type. Any help in understanding what is going on so I can fix this would be appreciated. Thank you
Re: Request for contributors permissions
Hi Maksim, Welcome to Apache Ignite Community! I added your account to the contributors list. Now you can assign tickets to yourself. Do not hesitate to ask if you need any assistance. Please check this page out for commonly asked questions pertaining to the contribution process https://ignite.apache.org/community/contribute.html 2020-05-19 18:06 GMT+03:00, Max Timonin : > Hi all, my name is Maksim Timonin, I'm going to contribute to Ignite. > > Could you please grant contributors permissions to *timonin.maksim > *account? > > Regards, > Maksim > -- Best regards, Ivan Pavlukhin
Request for contributors permissions
Hi all, my name is Maksim Timonin, I'm going to contribute to Ignite. Could you please grant contributors permissions to *timonin.maksim *account? Regards, Maksim
Re: Proposal: set default transaction timeout to 5 minutes
> > Support this idea in general but why 5 minutes and not less? This value looks to me greater than any value that can possibly affect existing deployments (existing long transactions may suddenly start to rollback), but less than reaction time of users that are only starting to get along with Ignite and suddenly experience TX deadlock. -- Best Regards, Ivan Rakov On Tue, May 19, 2020 at 10:31 AM Anton Vinogradov wrote: > +1 > > On Mon, May 18, 2020 at 9:45 PM Sergey Antonov > wrote: > > > +1 > > > > пн, 18 мая 2020 г. в 21:26, Andrey Mashenkov >: > > > > > +1 > > > > > > On Mon, May 18, 2020 at 9:19 PM Ivan Rakov > > wrote: > > > > > > > Hi Igniters, > > > > > > > > I have a very simple proposal. Let's set default TX timeout to 5 > > minutes > > > > (right now it's 0 = no timeout). > > > > Pros: > > > > 1. Deadlock detection procedure is triggered on timeout. In case user > > > will > > > > get into key-level deadlock, he'll be able to discover root cause > from > > > the > > > > logs (even though load will hang for a while) and skip step with > > googling > > > > and debugging. > > > > 2. Almost every system with transactions has timeout enabled by > > default. > > > > > > > > WDYT? > > > > > > > > -- > > > > Best Regards, > > > > Ivan Rakov > > > > > > > > > > > > > -- > > > Best regards, > > > Andrey V. Mashenkov > > > > > > > > > -- > > BR, Sergey Antonov > > >
[jira] [Created] (IGNITE-13037) .NET: Thin Client Near Cache
Pavel Tupitsyn created IGNITE-13037: --- Summary: .NET: Thin Client Near Cache Key: IGNITE-13037 URL: https://issues.apache.org/jira/browse/IGNITE-13037 Project: Ignite Issue Type: New Feature Components: platforms, thin client Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Add near caching for thin clients: * Clients can subscribe to change notifications for specific keys * Clients use partition awareness to route subscriptions to primary nodes * Use existing Thick .NET Client near caching mechanism to handle updates on the server side * Eviction policy is to be handled by the client code (because multiple servers are involved) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13036) Add event triggered while page replacement start.
Stanilovsky Evgeny created IGNITE-13036: --- Summary: Add event triggered while page replacement start. Key: IGNITE-13036 URL: https://issues.apache.org/jira/browse/IGNITE-13036 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.8 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny Page replacement between in memory pages and disk stored pages will be triggered if no DataRegion free space available for the new payload. There is a need for checking such events. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13035) Calcite integration. Support fallback on indexes rebuild
Roman Kondakov created IGNITE-13035: --- Summary: Calcite integration. Support fallback on indexes rebuild Key: IGNITE-13035 URL: https://issues.apache.org/jira/browse/IGNITE-13035 Project: Ignite Issue Type: Improvement Components: sql Reporter: Roman Kondakov When indexes are being rebuilt we need to use CacheTree for index scans as it happens in legacy engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13034) Append additional yardstick test for page replacements test purpose.
Stanilovsky Evgeny created IGNITE-13034: --- Summary: Append additional yardstick test for page replacements test purpose. Key: IGNITE-13034 URL: https://issues.apache.org/jira/browse/IGNITE-13034 Project: Ignite Issue Type: Improvement Components: yardstick Affects Versions: 2.8 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny There is a need in additional yardstick benchmarks, which will measure throughput with page replacement already in action. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13033) Java thin client: Service invocation
Aleksey Plekhanov created IGNITE-13033: -- Summary: Java thin client: Service invocation Key: IGNITE-13033 URL: https://issues.apache.org/jira/browse/IGNITE-13033 Project: Ignite Issue Type: New Feature Components: thin client Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Provide an API to invoke Ignite Services from java thin client. Protocol changes and all implementation details described in IEP-46. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13032) Fix flacky OptimizedMarshallerPooledSelfTest.
Andrey Mashenkov created IGNITE-13032:
-
Summary: Fix flacky OptimizedMarshallerPooledSelfTest.
Key: IGNITE-13032
URL: https://issues.apache.org/jira/browse/IGNITE-13032
Project: Ignite
Issue Type: Task
Components: binary
Affects Versions: 2.7
Reporter: Andrey Mashenkov
Fix For: 2.9
There are two flaky tests in the test case:
{{OptimizedMarshallerPooledSelfTest#testEvents}} and
{{OptimizedMarshallerPooledSelfTest#testServices}}. The tests timeout, the
reason is the following assertion:
{noformat}
[00:39:14]W: [org.gridgain:ignite-core] java.lang.AssertionError
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectStreamRegistry.closeOut(OptimizedObjectStreamRegistry.java:120)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:209)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:56)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10658)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10722)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.partitionSizes(GridDhtPartitionsFullMessage.java:360)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.createPartitionsFullMessage(GridCachePartitionExchangeManager.java:1543)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.createPartitionsFullMessage(GridCachePartitionExchangeManager.java:1442)
[00:39:14]W: [org.gridgain:ignite-core] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.createPartitionsMessage(GridDhtPartitionsExchangeFuture.java:2116){noformat}
Looks like the assertion fails because we attempt to return a stream to the
pool which does not belong to it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13031) .NET: SqlFieldsQuery as ContinuousQuery.InitialQuery
Pavel Tupitsyn created IGNITE-13031: --- Summary: .NET: SqlFieldsQuery as ContinuousQuery.InitialQuery Key: IGNITE-13031 URL: https://issues.apache.org/jira/browse/IGNITE-13031 Project: Ignite Issue Type: New Feature Components: platforms Affects Versions: 2.8 Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.9 SqlQuery has been deprecated in favor of SqlFieldsQuery, but ContinuousQuery in Ignite.NET does not allow SqlFieldsQuery as InitialQuery. Java API allows that, so we have to derive SqlFieldsQuery from QueryBase and make it work. The problem will arise when SqlFieldsQuery does not return _key & _val - see how Java handles this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Ignite Zookeeper Cluster Exceptions
Ilya, works now, it is due to my zookeeper with authentication, thanks. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Ignite Task deployment questions
Hi Guru, Even check the ignite deployment documentation, but still not much understand the overall picture. Say I have ready 3 nodes cluster with zookeeper discovery. Now I have a task want to deploy to this cluster, in flink, there is a console to provide upload, stop/run/delete and monitoring this tasks, how ignite achieve this deployment? Is there a detail step by step case? thanks. If we achieve this by deploy a jar to each node ./libs folder, and when instance startup it will lunch this task, but once we have new changes on this task, does it mean each deployment need restart the instances? Seems not a good solution. Another query is, with Ignite ignite = Ignition.Ignite(); ignite.start(); in this ignite instance, how can I connect to the remote cluster, where to set the remote connection string, such as host:port:user:pwd, like JDBC? and run the example/debug with this cluster environment. new to the ignite, need help, thanks a lot. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Compute Task deployment Queries
Hi Guru, I have ready 3 nodes cluster with zookeeper, have questions/confuse on the task deployment. Like flink, there is a web console to upload the jar file and control the job run/stop/delete, how our ignite tasks deploy to my cluster? From the doc, still not much understand the full pictures, need help, thanks. And another query is, in debug/dev environment, How I can connect to this cluster instances? Ignite ignite = Ignition.Ignite(); ignite.start(); where to set the connection string of the cluster instance? How can I run the tasks on the cluster instance, instead of with the provided example local instance startup? Thanks a lot. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Proposal: set default transaction timeout to 5 minutes
+1 On Mon, May 18, 2020 at 9:45 PM Sergey Antonov wrote: > +1 > > пн, 18 мая 2020 г. в 21:26, Andrey Mashenkov : > > > +1 > > > > On Mon, May 18, 2020 at 9:19 PM Ivan Rakov > wrote: > > > > > Hi Igniters, > > > > > > I have a very simple proposal. Let's set default TX timeout to 5 > minutes > > > (right now it's 0 = no timeout). > > > Pros: > > > 1. Deadlock detection procedure is triggered on timeout. In case user > > will > > > get into key-level deadlock, he'll be able to discover root cause from > > the > > > logs (even though load will hang for a while) and skip step with > googling > > > and debugging. > > > 2. Almost every system with transactions has timeout enabled by > default. > > > > > > WDYT? > > > > > > -- > > > Best Regards, > > > Ivan Rakov > > > > > > > > > -- > > Best regards, > > Andrey V. Mashenkov > > > > > -- > BR, Sergey Antonov >
