<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:26:11 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-551] Move fps database to larger partition</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-551</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;The postgres instance on db-ics is configured with database storage in the default location, which is on the root directory. On the VMs, that is ~8G and includes /var, /tmp, and /home/pfs. As it stands we have ~5G left, ~4G useable by the db.&lt;/p&gt;

&lt;p&gt;Once we get past the initial hardware configuration, we were planning to run centroiding on all mcs exposures. There are roughly 3600 holes; I think the rows have 48 bytes of data, plus 24 bytes of overhead plus one index. Call it 80 bytes per hole, ~300kB per exposure. We could conceivably (but will not) take ~600 frames/hour, 10 hours/night: ~1.7GB/night&lt;/p&gt;

&lt;p&gt;There is a db LUN on the storage server for just this purpose, but I do not know how it has been provisioned, and we have not used it. Given that we are demonstrably running successfully on the current VM storage I think it is safest to simply add more. &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=kyono&quot; class=&quot;user-hover&quot; rel=&quot;kyono&quot;&gt;kyono&lt;/a&gt; has created a new 48G partition now mounted on db-ics:/data-tmp/, so we can use that. &lt;/p&gt;

&lt;p&gt;I am not a postgres admin, but it looks trivial to &lt;em&gt;move&lt;/em&gt; a tablespace or to create a new one on a new location. The fancier stuff quickly gets intimidating.&lt;/p&gt;

&lt;p&gt;I propose taking a backup after tonight (saved to some other partition), and seeing how tight things really are. In any case I&apos;ll create a new tablespace on /data-tmp and be ready to shift things.&lt;/p&gt;</description>
                <environment></environment>
        <key id="13041">INSTRM-551</key>
            <summary>Move fps database to larger partition</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</priority>
                        <status id="10002" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/generic.png" description="The issue is resolved, reviewed, and merged">Done</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="kiaina">Kiaina Schubert</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>MCS</label>
                            <label>Subaru</label>
                            <label>subaru-personnel</label>
                    </labels>
                <created>Tue, 23 Oct 2018 23:35:45 +0000</created>
                <updated>Thu, 7 Nov 2019 01:49:48 +0000</updated>
                            <resolved>Thu, 7 Nov 2019 01:49:48 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="16005" author="cloomis" created="Thu, 29 Aug 2019 13:53:11 +0000"  >&lt;p&gt;Same thing happened this run. Fortunately the path is clearer now: the new disk server is online and is beefy enough to support running the postgres process. And we are not acquiring data for a while. &lt;/p&gt;

&lt;p&gt;So install postgres (newer version) on the NFS server, dump from and shutdown the current postgres, and load the new one. Renumber the db hostname(s).&lt;/p&gt;</comment>
                            <comment id="16296" author="cloomis" created="Thu, 7 Nov 2019 01:49:48 +0000"  >&lt;p&gt;This was done when the ZFS server was commissioned.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|s001j4:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>