Correction, Running Ignite as a Stand-Alone Process <https://apacheignite.readme.io/docs/getting-started#section-run-ignite-as-a-stand-alone-process> documentation section.
> On 13 Jun 2018, at 19:35, Petr Ivanov <[email protected]> wrote: > > Bhaskar, > > > To be honest, RPM packages are designed for at least RHEL / CentOS 7 and > higher. I’ve never had a chance to test them on 6.9 or earlier. > Thus, package design also requires systemd service manager (it should be > installed by dependency as well), and should be started as follows `systemctl > start [email protected]`. > Note: > systemctl — exactly this command should be used, not service; > @default-config.xml — after [at] sign you should specify only the name of > configuration file in /etc/apache-ignite, not full path to configuration file. > > Also, if problems with systemd will persist or in case of other corresponding > difficulties, see Running Ignite as a Service > <https://apacheignite.readme.io/docs/getting-started#section-run-ignite-as-a-service> > documentation section for alternative ways of running Apache Ignite > installed from packages. > > > Hope it helps! > > > >> On 13 Jun 2018, at 19:02, bhaskar <[email protected] >> <mailto:[email protected]>> wrote: >> >> Thanks, >> installed jdk rpm and apache-ignite installation went through, but when I >> start getting start: unrecognized service error, what is missing here?.I am >> m using Red Hat Enterprise Linux Server release 6.9 (Santiago) >> >> # service start apache-ignite@/etc/apache-ignite/default-config.xml >> start: unrecognized service >> # service start [email protected] >> <mailto:[email protected]> >> start: unrecognized service >> # >> >> My use case: >> want to build apache ignite and spark cluster for sql and spark ML. Spark >> streaming loads incremental data into Ignite Cluster. I am able to do this >> with zero deployment . But now trying to make Ignite Standalone Cluster run >> in service mode like spark standalone cluster. >> >> Thanks >> Bhaskar >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> <http://apache-ignite-users.70518.x6.nabble.com/> >
