[
https://issues.apache.org/jira/browse/TRAFODION-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619536#comment-14619536
]
Amanda Moran edited comment on TRAFODION-24 at 7/9/15 3:50 AM:
---------------------------------------------------------------
Yes, there are checks in multiple places. The checks within the installer were
never removed.
https://wiki.trafodion.org/wiki/index.php/Trafodion_Scanner (List of all the
scanner checks).
SameHBaseVersion
Removed from installer scripts, not needed in newest version of installer (will
be checked in soon).
SameHadoopVersion
Removed from installer scripts, not needed in newest version of installer.
HardwarePlatform
Installer does not check this... not sure it is needed at all
LinuxDistro
Installer does not check for this today, but will need to add something like
this within the installer scripts to determine if on Centos or SUSE
ntpdServiceRunning
We seem to get false positives with this one. It will fail and the whole
install will fail but Cloudera/Hortonworks will be running fine.
HBaseVersion
Already in installer scripts
HBaseJavaVersion
Already in installer scripts
The no_scanner option can be used as the default or a flag can be changed
around to disable running the scanner, then we would not need to remove the
code and could have it for future use.
was (Author: amoran):
Yes, there are checks in multiple places. The checks within the installer where
never removed.
https://wiki.trafodion.org/wiki/index.php/Trafodion_Scanner (List of all the
scanner checks).
SameHBaseVersion
Removed from installer scripts, not needed in newest version of installer (will
be checked in soon).
SameHadoopVersion
Removed from installer scripts, not needed in newest version of installer.
HardwarePlatform
Installer does not check this... not sure it is needed at all
LinuxDistro
Installer does not check for this today, but will need to add something like
this within the installer scripts to determine if on Centos or SUSE
ntpdServiceRunning
We seem to get false positives with this one. It will fail and the whole
install will fail but Cloudera/Hortonworks will be running fine.
HBaseVersion
Already in installer scripts
HBaseJavaVersion
Already in installer scripts
The no_scanner option can be used as the default or a flag can be changed
around to disable running the scanner, then we would not need to remove the
code and could have it for future use.
> Removing the Scanner from Trafodion Install
> -------------------------------------------
>
> Key: TRAFODION-24
> URL: https://issues.apache.org/jira/browse/TRAFODION-24
> Project: Apache Trafodion
> Issue Type: Brainstorming
> Reporter: Amanda Moran
> Priority: Minor
> Labels: installer
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Would like to get some feedback on possibly removing the scanner from
> Trafodion Install. We currently have a --no_scanner option that we have had
> to use on every POC/customer install. We get many false errors from the
> scanner and when we use the --no_scanner option we get a successful install
> and Trafodion works fine.
> All the important checks that are vital for trafodion installing properly are
> in the trafodion install scripts (all of the important checks that are in the
> scanner were taken from the Trafodion install scripts).
> I suggest we discontinue use of the scanner at this time. If we need
> additional checks we can add them to the installer scripts. We can also do
> some tweaking to the installer to "pick up where it left off" so that way
> when we do find errors we don't have to rerun the installer all over again,
> we will just start in the appropriate place.
> Looking forward to a discussion on this!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
