[teiid-issues] [JBoss JIRA] Commented: (TEIID-616) Start time of the system could be incorrect in rare cases where processes are brought down and back up

[Larry O'Leary (JIRA)]

    [ https://jira.jboss.org/jira/browse/TEIID-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12469267#action_12469267 ] 

Larry O'Leary commented on TEIID-616:
-------------------------------------

Sorry about that.  I read that originally but I guess that's what happens when you come back later and think you are picking up from where you left off.

Anyway, I agree that we must decide what "System Start Time" really is and why do we need it.  I think in the most common scenario, the system start time is used to determine how long a system or service has been running.  By traditional sense, running equates to available.  This introduces some issue within the Teiid world.  

First off, just about everything is exposed as a service.  A system is made up of multiple services.  You can not say the system has been up if the membership service isn't running.  Furthermore, can you really say that the system is up if a connector that one user may need is unavailable?  

>From my perspective, legacy meaning of system start time in MMx would be the date and time the entire system was started.  It would not reflect availability.  It would only reflect the state of the system going from no server processes to at least one server process.  

Now, if you think about it the system start time does not have any real value in this sense.  If someone wants to know how long the process has been running then they could just examine the processes within the operating system or examine the process logs.  

On the other hand, I can see value in making service start time available via the Admin API and as some detailed info that is displayed in the Console.  In this case each service (query, connector, membership, etc) would have a property that identified when that specific service started and it would be expected that a connector in one process may have a different start time than the same connector in a different process.  

In any event, I think the notion of system start time the current way it is implemented serves no purpose and could lead to confusion.  It would be better, in my opinion, to remove it.

> Start time of the system could be incorrect in rare cases where processes are brought down and back up
> ------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-616
>                 URL: https://jira.jboss.org/jira/browse/TEIID-616
>             Project: Teiid
>          Issue Type: Bug
>          Components: AdminApi, Server
>            Reporter: Van Halbert
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 6.1.1
>
>
> The system start time is determined by the Eldest Process start time.   This is not a 100% guaranteed to be true in all cases.   In a rare cases where proceses are brought down and backup, the oldest process start time might not represent how long the system had actually been running.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira