SSL/TLS for Ignite web-console
Hi, Am trying add SSL/TLS security for the ignite web-console. Could you please let me know the steps to configure SSL/TLS security for the Ignite web-console -- *Regards* *Sheshananda Naidu*
SSL/TLS for Ignite web-console
Hi, Am trying add SSL/TLS security for the ignite web-console. Could you please let me know the steps to configure SSL/TLS security for the Ignite web-console -- Regards Sheshananda Naidu -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
SpringCache : issues while registering metrics
Spring Boot Cache + Apache ignite + Spring Boot Actuator - Application fail to start when running tests. I have a project where i use Spring Boot 2.0.0+ , Spring Boot Cache, Apache Ignite, Spring Boot Actuator and TestNG. Since i've upgraded from ignite 2.5 to ignite 2.6+ i've been facing issues while trying to run Application tests, cause everytime the application starts on the test Task, ignite fails to register it's cache metrics on the CacheMetricsRegistrarConfiguration. The application fails with the following exception: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.actuate.autoconfigure.metrics.cache.CacheMetricsRegistrarConfiguration': Invocation of init method failed; nested exception is java.lang.AssertionError I've create an application that showcases this issue, you can access it through this link: https://github.com/pmrochaubi/apache-ignite-spring-boot-actuator Can someone explain me what's happening and how can i solve this ? Currently i'm stuck on version 2.5... Cheers, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
starting ignite in docker
I'd like to pass a local configuration file to docker as below, but ignite
doesn't find it, any ideas? The file is in the PWD directory. Using windows
powershell.
docker run -it --rm --net=host -v ${PWD}:/apache-ignite/config -e
"CONFIG_URI=file:///apache-ignite/config/ignite-config.xml" --name ignite
apacheignite/ignite
/opt/ignite/apache-ignite/bin/ignite.sh, WARN: Failed to resolve JMX host (JMX
will be disabled): linuxkit-00155d0f670e
class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
application context [springUrl=file:/apache-ignite/config/ignite-config.xml,
err=IOException parsing XML document from URL
[file:/apache-ignite/config/ignite-config.xml]; nested exception is
java.io.FileNotFoundException: /apache-ignite/config/ignite-config.xml (No such
file or directory)]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1025)
at org.apache.ignite.Ignition.start(Ignition.java:351)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
instantiate Spring XML application context
[springUrl=file:/apache-ignite/config/ignite-config.xml, err=IOException
parsing XML document from URL [file:/apache-ignite/config/ignite-config.xml];
nested exception is java.io.FileNotFoundException:
/apache-ignite/config/ignite-config.xml (No such file or directory)]
This message is confidential and is for the sole use of the intended
recipient(s). It may also be privileged or otherwise protected by copyright or
other legal rules. If you have received it by mistake please let us know by
reply email and delete it from your system. It is prohibited to copy this
message or disclose its content to anyone. Any confidentiality or privilege is
not waived or lost by any mistaken delivery or unauthorized disclosure of the
message. All messages sent to and from Agoda may be monitored to ensure
compliance with company policies, to protect the company's interests and to
remove potential malware. Electronic messages may be intercepted, amended, lost
or deleted, or contain viruses.
Re: quick Q- date type in cache is converted to ticks. is this based on time since from 1970?
Yes, internally it is stored as number of milliseconds since 1970-01-01 00:00:00.000 пт, 29 мар. 2019 г. в 16:17, wt : > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Best regards, Ivan Pavlukhin
Re: Blog post "Introduction to the Apache(R) Ignite™ community structure"
Hi Ilya, Thank you for the idea. Yes, probably I will re-post older blog on habr/en, but, anyway, we've finished a new one: https://habr.com/ru/company/sberbank/blog/444264/ it is now in Russian, but I hope someday I will translate it to English and post it there. Sincerely, Dmitriy Pavlov ср, 27 мар. 2019 г. в 18:17, Ilya Kasnacheev : > Hello! > > There's an English version of Habr now, did you consider reposting there? > > Regards, > -- > Ilya Kasnacheev > > > чт, 21 мар. 2019 г. в 15:35, Dmitriy Pavlov : > >> Sorry for the late reply. Contributors are not ranked so weight is not >> measured. The community always prefer to build consensus. If consensus is >> not reached (this happens time-to-time), then feature or change should not >> appear in the product. >> >> By the way, Apache PMCs may veto changes with a technical justification >> explaining why change is bad. >> >> A final word in project development has PMC (it is a committee consisting >> of all its members). Practically Apache Ignite Community prefers wider >> consensus - from all contributors. >> >> In case something is going wrong, there is our last resort: >> https://www.apache.org/board/escalation But I don't remember any >> escalations. >> >> Priority of implementing features is solved in another way: if someone >> wants to implement something and the community does not reject it, so why >> not? There is no single priority for all contributors. >> >> ср, 17 окт. 2018 г. в 12:09, zaleslaw : >> >>> [For discussion] It's interesting to know more about possible conflicts: >>> when >>> a few persons are involved in contribution as a commiters, for example, >>> and >>> they have different opinions about next steps in roadmap implementation >>> or >>> about certain feature. How to measure correctly their weights? One of >>> them >>> doing small bug fixes, another does large features. They are not ranked, >>> except amount of commits or code lines in github. Who can say last word? >>> >>> Imagine, only they are both understand something in this feature and its >>> priority. Votes couldn't help, right? How they should solve their >>> conflict? >>> Does you have any cases in your experience? >>> >>> >>> >>> -- >>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>> >>
