You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by vdogaru <gi...@git.apache.org> on 2016/04/07 22:58:35 UTC

[GitHub] incubator-quarks pull request: [WIP] QUARKS-13: Start over Quarks ...

GitHub user vdogaru opened a pull request:

    https://github.com/apache/incubator-quarks/pull/79

    [WIP] QUARKS-13: Start over Quarks when the JVM crashes (Linux)

    Simple mechanism to restart a Quarks application if the JVM running Quarks terminates unexpectedly:
     - Sample application which simulates a JVM crash after processing N tuples
     - Script which checks whether the Quarks JVM is still running, otherwise it restarts the Quarks sample app
     - Cron entry which runs the script every mnute
     - Readme providing setup instructions

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vdogaru/incubator-quarks QUARKS-13-vdogaru

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks/pull/79.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #79
    
----
commit 6615560b8b297f7bd07d4db7734e60a5774cef83
Author: Victor Dogaru <vd...@apache.org>
Date:   2016-04-07T20:08:24Z

    QUARKS-13-vdogaru Sample app which terminates the JVM after N tuples

commit bfd1273a22d9e868f01a5dc3587daf53d95f42db
Author: Victor Dogaru <vd...@apache.org>
Date:   2016-04-07T20:09:50Z

    QUARKS-13-vdogaru Script and crontab entry for Quarks jvm monitoring

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quarks pull request: QUARKS-13: Start over Quarks when t...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-quarks/pull/79


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quarks pull request: [WIP] QUARKS-13: Start over Quarks ...

Posted by ddebrunner <gi...@git.apache.org>.
Github user ddebrunner commented on a diff in the pull request:

    https://github.com/apache/incubator-quarks/pull/79#discussion_r59043626
  
    --- Diff: scripts/cron/startapp.cron ---
    @@ -0,0 +1,27 @@
    +#
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You under the Apache License, Version 2.0
    +# (the "License"); you may not use this file except in compliance with
    +# the License.  You may obtain a copy of the License at
    +#
    +#    http://www.apache.org/licenses/LICENSE-2.0
    +#
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +#
    +# Crontab file which contains settings for scheduling the execution of a 
    +# monitoring script every minute using cron.
    +#
    +# You must set the QUARKS environment variable to point to your Quarks 
    +# installation:
    +# QUARKS=/home/your_userid/quarks/java8
    +#
    +# Make sure that java is in the PATH environment used by cron:
    +# PATH=/opt/my_java/bin:$PATH
    --- End diff --
    
    Why not use the standard approach of JAVA_HOME?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quarks pull request: [WIP] QUARKS-13: Start over Quarks ...

Posted by ddebrunner <gi...@git.apache.org>.
Github user ddebrunner commented on a diff in the pull request:

    https://github.com/apache/incubator-quarks/pull/79#discussion_r59043494
  
    --- Diff: scripts/cron/startapp.cron ---
    @@ -0,0 +1,27 @@
    +#
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You under the Apache License, Version 2.0
    +# (the "License"); you may not use this file except in compliance with
    +# the License.  You may obtain a copy of the License at
    +#
    +#    http://www.apache.org/licenses/LICENSE-2.0
    +#
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +#
    +# Crontab file which contains settings for scheduling the execution of a 
    +# monitoring script every minute using cron.
    +#
    +# You must set the QUARKS environment variable to point to your Quarks 
    --- End diff --
    
    Wouldn't be easier to have the quarks location passed in as a command line argument rather than requiring an evironment variable set elsewhere?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quarks pull request: [WIP] QUARKS-13: Start over Quarks ...

Posted by ddebrunner <gi...@git.apache.org>.
Github user ddebrunner commented on a diff in the pull request:

    https://github.com/apache/incubator-quarks/pull/79#discussion_r59044276
  
    --- Diff: scripts/cron/startapp.sh ---
    @@ -0,0 +1,119 @@
    +#!/bin/bash
    +#
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You under the Apache License, Version 2.0
    +# (the "License"); you may not use this file except in compliance with
    +# the License.  You may obtain a copy of the License at
    +#
    +#    http://www.apache.org/licenses/LICENSE-2.0
    +#
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +#
    +
    +[ ! -n "${QUARKS:-}" ] && QUARKS=../..
    +
    +#
    +# Application name identifies the running process.  For the scope of this
    --- End diff --
    
    Seems like with minor changes this could change from a sample to a reusable script, e.g. passing in the classpath and main class name.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---