Ignite web console on kubernetes with ingress

Hi, I was trying to use Ignite web console on Kubernetes using the docker image at https://hub.docker.com/r/apacheignite/web-console-standalone/ For external access, I am using ingress kubernetes resource. I am able to access Web console UI using the default href path (/). But with non default

Re: How to force ignite clear disk space

WAL is disabled, as you can see in config: dataStorageConfiguration.setWalMode(WALMode.NONE); My ignite version is 2.6 That is what I have in directory after completing the test: [cid:3ce7ec54-a3be-4eda-b319-c184a1ceabf9] От: aealexsandrov

Re: New added property with @QuerySqlField does not persist

Thank you very much! how to handle this case in production? it's too common to add new attribute to a new cache/pojo attribute.!!! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: New added property with @QuerySqlField does not persist

Actually you can't, because the schema stored in cache configuration is the old one before adding column. I've asked a similar question on dev list.

Re: New added property with @QuerySqlField does not persist

Thank you reply very much! May be I don't address the issue clearly. here is my steps: 1: keep the server running 2: alter the schema via sql 3: I can query the new add column 4: add the corresponding attribute in pojo and with tag it with @QuerySqlField. 5: call IgniteCache.put with new version

Re: New added property with @QuerySqlField does not persist

Hi, If you want to change sql schema after start, you have to use ALTER TABLE command: https://apacheignite-sql.readme.io/docs/alter-table Best Regards, Evgenii вт, 20 нояб. 2018 г. в 06:37, kcheng.mvp : > i noticed there is a comment from @slava.koptilin > > > I think the problem is to

Re: Read SQL table via cache api

Hi Andrei, I have figured this out after several hours of troubleshooting today. I had the Ignite server process, which hosted the table/cache, running on a Linux host (CentOS7). On the other hand, I was running the client code on a Macbook. It seems that the two platform was deserializing the

Invalid handshake message

We deployed Ignite on AWS.We have a single node cluster to begin with. Our Application is connecting as client. When I access one of the endpoints of our application, it is being intercepted by the GridWorker. GridWorker is throwing "Invalid handshake message" message. How to disable this

Re: Read SQL table via cache api

Hi, I think that information about it could be located in node log. Could you please provide the log of the node where you tries to read the data? BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Simple off heap implementation ?

Hi, To use persistence you need to get familiar with the concept of baseline topology: https://apacheignite.readme.io/docs/baseline-topology It basically means, that you need a fixed set of server nodes to store data. You can config which node will store partitions of a particular cache by using

Re: How to force ignite clear disk space

Hi, I think that you face the issue related to the next ticket: https://gridgain.freshdesk.com/helpdesk/tickets/9049 After destroying of the cache remains some files that contain the configuration of the cache. But it should be already fixed in the latest version of Ignite. However, the files

Re: Cache stats like number of cache hits, misses, reads, write, avg

Hi, DataStreamer depends on the allowOverwrite flag. https://apacheignite.readme.io/docs/data-streamers#section-allow-overwrite The default value is false to get the best performance. But it also means that metrics will not be updated. If you set allowOverwrite true then data streamer will

Re: Get Field Names In Select Query

If you don't do GetAll() and just do Query(new SqlFieldsQuery...), the FieldsQueryCursor returned will have the column count and name of your result set. Hope this help. On Tuesday, November 20, 2018, 8:43:22 PM EST, siva wrote: Hi, How to get the field names in select query? I am

Re: Ignite.Net - Defining SQL Schema without using QuerySqlField custom attribute

Yes.  I just found out the hard way yesterday by debugging through the Ignite.Net source code and reached the same understanding.  Thank you. On Wednesday, November 21, 2018, 6:12:16 AM EST, Pavel Tupitsyn wrote: There is a subtle issue with DateTime and SQL [1] If you always use UTC

Re: Ignite.Net - Defining SQL Schema without using QuerySqlField custom attribute

There is a subtle issue with DateTime and SQL [1] If you always use UTC in Ignite (which you should), the proper thing to do is: var igniteCfg = new IgniteConfiguration { BinaryConfiguration = new BinaryConfiguration { Serializer = new BinaryReflectiveSerializer {

Re: Long activate time with tens of millions data

Hi! Do you use persistence ? if so, do you have 150 different cahes ? if that is the case I would think trying to use cache groups would help a lot if that is possible for you Mikael Den 2018-11-21 kl. 09:03, skrev yangjiajun: I have a ignite node which is version 2.6.I use it as a

Long activate time with tens of millions data

I have a ignite node which is version 2.6.I use it as a database.It stores tens of millions data in about 150 tables.Every time I try to reactivate after restart,it takes very long time.But the cpu is very low.Is there any way to improve it? -- Sent from: