Custom Query (431 matches)
Results (55 - 57 of 431)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#55 | invalid | IZ304: sge_conf(5) binary_path not used for qrsh_starter | andreas | |
Description |
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=304] Issue #: 304 Platform: All Reporter: andreas (andreas) Component: gridengine OS: All Subcomponent: qmaster Version: 5.3beta1 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: --- Assigned to: ernst (ernst) QA Contact: ernst URL: * Summary: sge_conf(5) binary_path not used for qrsh_starter Status whiteboard: Attachments: Issue 304 blocks: Votes for issue 304: Opened: Fri Jun 28 08:21:00 -0700 2002 ------------------------ DESCRIPTION: The binary_path setting in local sge_conf(5) is not considered when qrsh_starter is started using rsh by qrsh. The man page says binary_path is used in such a case. sge_conf(5) binary_path is used for cluster tuning purposes, as it can be used to lower the load a NFS server is faced with. ------- Additional comments from andreas Mon Jan 20 04:24:43 -0700 2003 ------- sge_conf(5) binary path does not apply to util bin binaries ------- Additional comments from andreas Fri Sep 10 02:28:08 -0700 2004 ------- WORKAROUND: A symbolic link needs to be created to effectuate executable pathes other than $SGE_ROOT/utilbin/<arch>/qrsh_starter actually be used. ------- Additional comments from pollinger Fri Dec 9 08:32:28 -0700 2005 ------- Changed Subcomponent |
|||
#94 | invalid | IZ553: Admin guide: Moved object references from pe/ckpt into queue | ernst | |
Description |
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=553] Issue #: 553 Platform: All Reporter: ernst (ernst) Component: gridengine OS: All Subcomponent: doc Version: 6.0 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: FEATURE Target milestone: --- Assigned to: andreas (andreas) QA Contact: skonta URL: * Summary: Admin guide: Moved object references from pe/ckpt into queue Status whiteboard: Attachments: Issue 553 blocks: Votes for issue 553: Opened: Thu May 15 04:49:00 -0700 2003 ------------------------ The attribute set of the pe object, checkointing environment and queue has been changed. These changes will be available with the next major release (6.0) of SGE/EE. PE object --------- The attribute "queue_list" has been removed from pe object. The "queue_list" attribute made it possible to define a relation between one pe enviropnment and multiple queue objects. CKPT object ----------- Also here the attribute "queue_list" has been removed. The "queue_list" attribute made it possible to define a relation between one ckpt interface and multiple queue objects. QUEUE object ------------ Two attributes have been added to the queue specification: "pe_list" and "ckpt_list". These new lists may contain a list of pe/ckpt names or the keyword "NONE". Both lists make it possible to define relations between one queue object and multiple pe environments/ckpt interfaces. The definition of the qtype attibute has been changed. The formerly supported types parallel and checkpointing are deprecated. A queue is implicitely of type parallel/checkpointing if there is a parallel environment or a checkpointing interface specified for this queue instance in "pe_list"/"ckpt_list". Currently allowed values for qtype are BATCH and/or INTERACTIVE or the keyword NONE. Default value for new queues is BATCH and INTERACTIVE Some Examples ------------- a) Old configuration: QUEUE1: qtype PARALLEL PE1: queue_list QUEUEU1 New configuration: QUEUE1: qtype NONE pe_list PE1 PE1: b) Old configuration: QUEUE1: qtype BATCH CHECKPOINTING CKPT1: queue_list QUEUEU1 New configuration: QUEUE1: qtype BATCH ckpt_list CKPT1 CKPT1: ------- Additional comments from andreas Tue Jul 20 10:10:54 -0700 2004 ------- Changed summary. ------- Additional comments from andreas Thu Oct 21 08:37:22 -0700 2004 ------- Assign User/Admin/Install issues to Mark O'Brien. ------- Additional comments from surajp Mon Mar 23 01:53:25 -0700 2009 ------- Reassigning issue to Sandra. |
|||
#95 | invalid | IZ554: GE scheduler and ntpdate seems incompatible. | yoshiki | |
Description |
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=554] Issue #: 554 Platform: PC Reporter: yoshiki (yoshiki) Component: gridengine OS: Linux Subcomponent: qmaster Version: 5.3p2 CC: None defined Status: NEW Priority: P3 Resolution: Issue type: TASK Target milestone: --- Assigned to: andreas (andreas) QA Contact: ernst URL: * Summary: GE scheduler and ntpdate seems incompatible. Status whiteboard: Attachments: Issue 554 blocks: Votes for issue 554: Opened: Thu May 15 18:12:00 -0700 2003 ------------------------ My cluster has one ntp server node. The others has some clone script for time synchronization as following. 0 3 * * * /usr/sbin/ntpdate -s 192.168.1.1; /sbin/hwclock --systohc When I run some job at about ntpdate setting time (ex. 3 a.m.), the job is sometimes re-run. Some output of qmaster message is following. -------------------------------------------------- ------------------------ Wed May 14 02:59:51 2003|qmaster|node01|W|system time has been modified (-8 seconds) Wed May 14 02:59:51 2003|qmaster|node01|E|enrolled, but leave_commd() call failed with status: NOT ENROLLED Wed May 14 03:00:28 2003|qmaster|node01|W|job 3746.1 failed on host node07 rescheduling because: manual/auto rescheduling Wed May 14 03:00:28 2003|qmaster|node01|W|rescheduling job 3746.1 Wed May 14 03:00:28 2003|qmaster|node01|W|job 3828.1 failed on host node10 rescheduling because: manual/auto rescheduling Wed May 14 03:00:28 2003|qmaster|node01|W|rescheduling job 3828.1 -------------------------------------------------- ------------------------ I suppose it happens a long time delay to report qmaster from execd on time changed node. ------- Additional comments from sgrell Tue Dec 6 08:38:58 -0700 2005 ------- Changed subcomponent. Stephan ------- Additional comments from mnikhil Wed Jan 16 07:44:27 -0700 2008 ------- may I know anything latest on this please? ------- Additional comments from joga Wed May 28 03:40:25 -0700 2008 ------- The corresponding code is only in 5.3 source base, so are you seeing this in a 5.3 cluster? Then you should consider upgrading to the current version (6.1u4). A workaround might be to run ntpd instead of regular calls to ntpdate. |
Note: See TracQuery
for help on using queries.