[
https://issues.apache.org/jira/browse/IGNITE-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450203#comment-16450203
]
Max Shonichev commented on IGNITE-7108:
---------------------------------------
Confirm.
Also tested following scenarios:
- enabled apache-ign...@default-config.xml service for restart with physical
server restart
- checked firewall rules : two nodes successfully connect with/without
enabled firewalld
During those tests I found that there are no simple means for user to tweak
Apache Ignite service JVM settings other than manually hack
service.sh/ignite.sh, which I would consider bad practice, because files
installed with package will be overwritten upon package upgrade. We should add
something like /etc/defaults/apache-ignite in future.
Also, would be nice to have simple means to start Apache Ignite examples with
configs from /usr/share/doc/apache-ignite/examples/config.
Those findings do not block IGNITE-7108 ticket merge, because current state of
work is rather solid, packages for Redhat/Ubuntu are buildable, installable and
runnable.
IMO, we should adopt patch it to master, later on we can create appropriate
tickets after receiving some user feedback.
> Apache Ignite 2.5 RPM and DEB packages
> --------------------------------------
>
> Key: IGNITE-7108
> URL: https://issues.apache.org/jira/browse/IGNITE-7108
> Project: Ignite
> Issue Type: New Feature
> Components: binary
> Reporter: Peter Ivanov
> Assignee: Peter Ivanov
> Priority: Critical
> Labels: important
> Fix For: 2.5
>
>
> # (/) Update RPM build process to unify with DEB build.
> # (/) Prepare build of DEB package (using architecture and layout from RPM
> package).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
